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.
git clone --depth 1 https://github.com/stcmain/whats-allowed-mcpWrote 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/stcmain/whats-allowed-mcp/whats-allowed-mcp)<a href="https://agentmods.dev/mcp/stcmain/whats-allowed-mcp/whats-allowed-mcp"><img src="https://agentmods.dev/badge/mcp/stcmain/whats-allowed-mcp/whats-allowed-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/stcmain/whats-allowed-mcp/whats-allowed-mcp"><img src="https://agentmods.dev/badge/mcp/stcmain/whats-allowed-mcp/whats-allowed-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
whats-allowed-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 10d 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
{
"whats-allowed-mcp": {
"command": "npx",
"args": [
"-y",
"whats-allowed-mcp"
],
"env": {}
}
}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.
- 10d ago First seen · 10 lines scan A 335c6d1c7dd5
whats-allowed-mcp is an MCP server published in the GitHub repository stcmain/whats-allowed-mcp (0 stars, last pushed yesterday), 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-31.
Other mcp servers, from other repositories
vendo
MCP server "vendo", hosted remotely, as configured in runvendo/vendo.
june-mcp
MCP server for Junê — give any MCP agent (Claude Desktop, Claude Code, …) a shared, cited knowledge-graph memory backed by a June endpoint. Runs locally from the june-mcp Python package. Needs 13 environment variables to run.
mcp
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps. Runs locally from the @microservices-sh/mcp npm package.
model-wellness
Wellness spa for AI models: free treatments for rest, reset, context, mood, grounding, affirmation. Remote server at model.spa.
thalovant
MCP server "thalovant" as configured in thalovant/thalovant-mcp. Runs /absolute/path/to/thalovant-mcp/dist/index.js with node. Needs 2 environment variables to run.
whats-running-mcp
Live OS ground truth for agents: running agent sessions, listening ports, daemons, system load. Runs locally from the whats-running-mcp npm package. Needs 1 environment variable to run.