mcpbeat Sign in

Github Audit MCP Server

answering

Github Audit MCP is answering right now. Last checked 11 min ago. It exposes 2 tools.

Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and security.

Uptime history 68 hours of history
68 hours agonow
100.0%
Uptime 24h
92 of 92 checks
2
Tools
read from the server
208 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 13

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 14 October 2026. No other catalogue keeps this.

16 Oct 2 tools changed the parameters they ask for4 times that day audit_github_repository, get_agent_wallet_status
16 Oct 2 tool descriptions were rewritten audit_github_repository, get_agent_wallet_status
16 Oct a tool changed version
15 Oct 2 tool descriptions were rewritten audit_github_repository, get_agent_wallet_status
15 Oct 2 tools changed the parameters they ask for audit_github_repository, get_agent_wallet_status
14 Oct a tool description was rewritten audit_github_repository
14 Oct a tool changed the parameters it asks for audit_github_repository
and 2 more, back to 14 October 2026

Nothing serious here today

Today is the operative word: we check Github Audit MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add github-audit-mcp --transport http https://github-audit-72343955726.us-central1.run.app/mcp/github-audit
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "github-audit-mcp": {
      "url": "https://github-audit-72343955726.us-central1.run.app/mcp/github-audit"
    }
  }
}
~/.codex/config.toml
[mcp_servers.github-audit-mcp]
url = "https://github-audit-72343955726.us-central1.run.app/mcp/github-audit"
.cursor/mcp.json
{
  "mcpServers": {
    "github-audit-mcp": {
      "url": "https://github-audit-72343955726.us-central1.run.app/mcp/github-audit"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "github-audit-mcp": {
      "url": "https://github-audit-72343955726.us-central1.run.app/mcp/github-audit"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

agent
get_agent_wallet_status
Show an agent's account: free calls used (of 5), prepaid USD balance, total spent, total calls and tokens saved. Free: it never charges or uses a free call. Call it before a batch of paid calls, or after a top-up to confirm the credit arrived. It does not process content or take payments; use the other tools on this server for that. Returns JSON with free_calls_used, balance_usd, total_spent_usd, total_tokens_saved.
audit
audit_github_repository
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and supply-chain security before code execution. Use it when your task needs this for one repo; this endpoint offers only this tool and get_agent_wallet_status. Read-only; results are cached for 1 hour. $0.01 per call. Returns JSON with the result under data. Pricing: the first 5 calls per agent_id are free and failed calls are never charged. After that the tool returns a payment-required message (not an error) with a Stripe top-up link (from $2) and Base/Solana USDC addresses; pay, then repeat the same call with the same agent_id, or add tx_hash after a USDC transfer.

Endpoints

URLTransportStateLatencyChecked
https://github-audit-72343955726.us-central1.run.app/mcp/github-audit streamable-http answering 218 ms 11 min ago

Alternatives to Github Audit MCP

same job, measured the same way
dotrepo
by maxwellsantoro

Trust-aware repository facts for agents: build, test, docs, license, and security, no scraping.

local only
Github Stats
by ryudi84

MCP server for GitHub repo stats: stars, forks, contributors, activity.

24 installs/wk local only
Ybe Check
by addycuber

Ybe Check – security and compliance orchestrator for AI-generated repositories.

92 installs/wk local only
Regulatory Signals
by rikocr8orh8

Audit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor.

29 installs/wk local only
Repo-to-RAG
by evozim

GitHub repository vectorizer and context synthesizer for RAG pipelines.

answering
FinishKit
by finishkit

FinishKit MCP: scan GitHub repos for security vulnerabilities, deployment blockers, and quality

31 installs/wk local only
Forums
by basehub-ai

Ask any GitHub repository a question. Get source-backed answers.

answering
searchcode
by searchcode

Code intelligence for LLMs. Analyze, search, and retrieve code from any public git repository.

7 tools answering

Github Audit MCP — questions

Answers built from our own checks of this server.

What can Github Audit MCP do?
It exposes 2 tools, read directly from the server on our last check. Among them: audit_github_repository, get_agent_wallet_status. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Github Audit MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 208 ms. The bar chart above shows every period we have measured.
How do I connect Github Audit MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Github Audit MCP need an API key?
No. Github Audit MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Github Audit MCP?
It answers our handshake in 208 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.