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/samuellawrence/openapi-mcp-bridge/openapi-bridgegit clone --depth 1 https://github.com/samuellawrence/openapi-mcp-bridgeGrade A, and why
openapi-bridge 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 2d 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
{
"openapi-bridge": {
"command": "python",
"args": [
"-m",
"src.server"
],
"cwd": "/Users/samuel/workspace/py-apps/openapi-mcp-bridge",
"env": {
"PETSTORE_KEY": "special-key"
}
}
}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.
- 2d ago First seen · 13 lines scan A a5e5a8a2099a
openapi-bridge is an MCP server published in the GitHub repository samuellawrence/openapi-mcp-bridge (0 stars, last pushed 1mo 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-31.
Other mcp servers, from other repositories
ninjaone-mcp
MCP server "ninjaone-mcp" as configured in WYRE-AI/ninjaone-mcp. Runs in Docker (ghcr.io/wyre-ai/ninjaone-mcp:v2.3.0). Needs 6 environment variables to run.
connectwise-manage-mcp
MCP server "connectwise-manage-mcp" as configured in WYRE-AI/connectwise-manage-mcp. Runs in Docker (ghcr.io/wyre-ai/connectwise-manage-mcp:v1.8.8). Needs 8 environment variables to run.
apibase
327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint. Runs locally from the apibase-mcp-client npm package.
umami
MCP server for Umami Analytics API v2 — websites, stats, events, reports, and realtime. Runs locally from the @mikusnuz/umami-mcp npm package. Needs 4 environment variables to run.
mcp-server
MCP server for Zooza — class scheduling, attendance, and booking for activity businesses. Remote server at mcp.zooza.app.
local-delegate
Delegate mechanical text tasks to a local OpenAI-compatible LLM endpoint to conserve Claude subscription quota. Runs locally from the local-delegate-mcp Python package. Needs 2 environment variables to run.