A local MCP server for requesting decentralized AI services, including weather information, deepfake detection, and language-model tasks. MCP is a standard way for an AI agent to call external tools.

Use it when an agent needs weather or climate data, deepfake checks, language-model output, image generation, or embeddings through the Telegraph network.

It lets an agent access these services from a local process, but it needs eight environment settings, including network details and private keys.

telegraph — MCP server by telegraphprotocol/telegraph-mcp

Install

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.

Clone the repo

git clone --depth 1 https://github.com/telegraphprotocol/telegraph-mcp

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/mcp/telegraphprotocol/telegraph-mcp/telegraph/github.svg)](https://agentmods.dev/mcp/telegraphprotocol/telegraph-mcp/telegraph)

Your own site

<a href="https://agentmods.dev/mcp/telegraphprotocol/telegraph-mcp/telegraph"><img src="https://agentmods.dev/badge/mcp/telegraphprotocol/telegraph-mcp/telegraph/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.

Your own site · 80×15

<a href="https://agentmods.dev/mcp/telegraphprotocol/telegraph-mcp/telegraph"><img src="https://agentmods.dev/badge/mcp/telegraphprotocol/telegraph-mcp/telegraph.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Security

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 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.

server.json · 19 lines

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": ""
    }
  }
}

Changes

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 · 19 lines scan A a3121b319d5b

Subscribe to this mod's changes

telegraph is an MCP server published in the GitHub repository telegraphprotocol/telegraph-mcp (0 stars, last pushed 3mo 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.

Data and AI Web3 and blockchain

ibm-x402-mcp

x402 pay-per-use MCP server for IBM Granite AI — chat, code, embeddings, analysis, and time-series forecasting. Pay USDC on Solana per call. No IBM Cloud account required. Runs locally from the @three-ws/ibm-x402-mcp npm package. Needs 9 environment variables to run.

nirholas/three.ws · not measured

payperbyte

MCP server for PayPerByte — cryptographically attested, provenance-verifiable data feeds for AI agents (proves which publisher signed the exact bytes, not data correctness). Pay-per-call via x402 settled in USDC on Base mainnet, or subscribe to first-part. Runs locally from the byte-mcp-server npm package.

0rkz/byte-mcp-server · not measured

telegraph

Getting it into your agent

Wrote this? Show the measurements

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

ibm-x402-mcp

payperbyte

agentpay

nodeflare

mcp

bridgenode-mcp