Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/apisec-inc/ai-surface/demo-app-github-mcpgit clone --depth 1 https://github.com/apisec-inc/AI-SurfaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/apisec-inc/ai-surface/demo-app-github-mcp)<a href="https://agentmods.dev/mcp/apisec-inc/ai-surface/demo-app-github-mcp"><img src="https://agentmods.dev/badge/mcp/apisec-inc/ai-surface/demo-app-github-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
github-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"github-mcp": {
"url": "https://mcp.github.com/sse",
"tools": [
"repo:read",
"issues:write",
"admin"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 10 lines scan A e3ee65b5035c
github-mcp is an MCP server published in the GitHub repository apisec-inc/AI-Surface (112 stars, last pushed 9d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
web-fetcher
MCP server "web-fetcher" as configured in akanthed/SecureAI-Scan. Runs locally from the some-mcp-fetch-server npm package. Needs 1 environment variable to run.
remote-tools
MCP server "remote-tools", hosted remotely at tools.example.com, as configured in akanthed/SecureAI-Scan.
local-dev
MCP server "local-dev", hosted remotely at localhost, as configured in akanthed/SecureAI-Scan.
assay
MCP server "assay" as configured in chawdamrunal/assay. Launched with assay mcp --transport stdio.
codeinspectus
Local-first MCP security scanner and CLI for AI-generated applications. Runs locally from the codeinspectus npm package.
ai-appsec
Evidence-backed AppSec for AI applications and agents. Powered by HAIEC. Runs locally from the ai-appsec npm package.