Ext Ops Panel
Open dashboard
Comparison

github-secrets vs GitHub Actions Security Audit

github-secrets is a plugin bundle for AI coding tools published by gabrielkoerich. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GitHub Actions Security Audit is an MCP server published by tylerscomic-lab. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacegithub-secretsGitHub Actions Security Audit
Community marketplace gabrielkoerich/skills Not seen in the last pass
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

github-secrets vs GitHub Actions Security Audit
Factgithub-secretsGitHub Actions Security Audit
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (github-actions-audit-mcp.mcpize.run/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/gabrielkoerich/skillsgithub.com/tylerscomic-lab/github-actions-audit-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-192026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

github-secrets

In its own words, on Community GitHub marketplaces:

Manage GitHub repository secrets via the GitHub API. Supports listing, adding, updating, and deleting repository and organization secrets. Use when user needs to manage GitHub Actions secrets, environment variables, or repository-level secrets securely.

GitHub Actions Security Audit

In its own words, on Official MCP Registry:

Audit GitHub Actions workflows for script injection, unpinned actions and missing permissions.

How to run each

github-secrets As a Claude Code plugin

Claude Code
/plugin marketplace add gabrielkoerich/skills
/plugin install github-secrets@skills

GitHub Actions Security Audit As a remote MCP server

Claude Code
claude mcp add --transport http github-actions-audit-mcp https://github-actions-audit-mcp.mcpize.run/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only GitHub Actions Security Audit has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: github-secrets · What it can do: GitHub Actions Security Audit · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built