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/rejifald/StitchAPIWrote 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/rejifald/stitchapi/stitchapi-docs)<a href="https://agentmods.dev/mcp/rejifald/stitchapi/stitchapi-docs"><img src="https://agentmods.dev/badge/mcp/rejifald/stitchapi/stitchapi-docs/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/rejifald/stitchapi/stitchapi-docs"><img src="https://agentmods.dev/badge/mcp/rejifald/stitchapi/stitchapi-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stitchapi-docs 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- docs — 91% identical, 5 lines differ
What it actually says
{
"stitchapi-docs": {
"command": "npx",
"args": [
"-y",
"@stitchapi/docs-mcp"
]
}
}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.
- 1mo ago First seen · 9 lines scan A d403881712f3
stitchapi-docs is an MCP server published in the GitHub repository rejifald/StitchAPI (20 stars, last pushed 2d ago), licensed Apache-2.0. 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
openclaw-mcp
MCP server bridging Claude.ai/Desktop with self-hosted OpenClaw via OAuth 2.1. Runs locally from the openclaw-mcp npm package. Needs 4 environment variables to run.
openclaw
Model Context Protocol (MCP) server for OpenClaw AI assistant integration. Runs locally from the openclaw-mcp npm package.
adyen-mcp-server
MCP server "adyen-mcp-server" as configured in Adyen/adyen-mcp. Runs /workspaces/adyen-mcp/typescript/dist/index.js with node. Needs 1 environment variable to run.
homespun
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions. Runs locally from the @homespunapps/mcp npm package. Needs 4 environment variables to run.
x-mcp-ai
Safety-first X (Twitter) API v2 MCP server: 41 typed tools across 12 packages, policy-gated. Runs locally from the x-mcp-ai npm package. Needs 18 environment variables to run.
swagger-mcp
MCP server "swagger-mcp" as configured in dkanster/samotpravil-api-mcp. Launched with .cursor/swagger-mcp.sh.