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/telegraphprotocol/telegraph-mcp/telegraphgit clone --depth 1 https://github.com/telegraphprotocol/telegraph-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/telegraphprotocol/telegraph-mcp/telegraph)<a href="https://agentmods.dev/mcp/telegraphprotocol/telegraph-mcp/telegraph"><img src="https://agentmods.dev/badge/mcp/telegraphprotocol/telegraph-mcp/telegraph.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
telegraph 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 3d 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
{
"telegraph": {
"command": "npx",
"args": [
"-y",
"telegraph-protocol-mcp"
],
"env": {
"TELEGRAPH_NODE_URL": "",
"TELEGRAPH_ENGINE_URL": "",
"TELEGRAPH_DAEMON_URL": "",
"TELEGRAPH_EVM_PRIVATE_KEY": "",
"TELEGRAPH_SOLANA_PRIVATE_KEY": "",
"EVM_NETWORK": "",
"SVM_NETWORK": "",
"REFRESH_INTERVAL_MS": ""
}
}
}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.
- 3d ago First seen · 19 lines scan A a3121b319d5b
telegraph is an MCP server published in the GitHub repository telegraphprotocol/telegraph-mcp (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
sap-mcp
Solana-native MCP gateway for SAP, DeFi tools, SNS identity, and x402 payments. Runs locally from the @oobe-protocol-labs/sap-mcp-server npm package. Needs 2 environment variables to run.
mcp
MCP server that lets AI agents create, fetch, verify, and publish Molpha oracle data. Runs locally from the @molpha/mcp npm package. Needs 20 environment variables to run.
nightgate-mcp
MCP server exposing NIGHTGATE (Midnight blockchain attestation layer) to AI agents. Runs locally from the @odatano/nightgate-mcp npm package.
oddsrail
MCP server giving AI trading agents access to prediction markets (Polymarket, Kalshi) with on-chain builder-code attribution and trading signals. Runs locally from the oddsrail Python package. Needs 4 environment variables to run.
fibx
Swap, transfer, track a portfolio and use Aave V3 on Base, HyperEVM and Monad. Runs locally from the fibx npm package. Needs 2 environment variables to run.
crypto
Crypto MCP — cryptocurrency prices and currency conversion. Remote server at gateway.pipeworx.io.