Telegraph MCP server
io.github.telegraphprotocol/telegraph·v1.0.0Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.
0 stars23 downloads/wk
Reviews
Write oneNobody has reviewed Telegraph yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Telegraph tools (9)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
tg_daemon_categoriesList all signal categories tracked by the Telegraph Daemon. Shows category name, question count, and average interest score. Categories include POLITICS, ECONOMICS, GEOPOLITICS, TECHNOLOGY, CLIMATE, HEALTH, FINANCE, CRYPTO, SPORTS, SCIENCE, SOCIAL, OTHER. No payment required.
tg_daemon_healthCheck the health status of the Telegraph Daemon. Returns status and server time. No payment required.
tg_daemon_questionsQuery Telegraph Daemon-collected signals and questions. Supports filtering by category, source, sort order, time range, minimum interest score. Returns questions with their metadata, results, and interest scores. No payment required.
tg_engine_askAuto-routed AI inference through the Telegraph Engine. The engine uses an LLM router to select the best subnet for your query and returns the result. Requires x402 payment. Use this for general questions like 'what is the weather in Lahore', 'what is Bitcoin', or 'is this image a deepfake'.
tg_engine_ask_subnetDirect AI inference through a specific Telegraph subnet. Provide the subnet ID (e.g., 18 for Zeus Weather, 34 for BitMind deepfake detection, 102 for OpenAI) along with the method, endpoint, and payload. Requires x402 payment. Use tg_engine_list_subnets to see available subnets and their capabilities.
tg_engine_list_subnetsList all available Telegraph Engine subnets (AI inference providers). No payment required. Returns subnet ID, slug, name, description, base URL, capabilities, and cost per call.
tg_node_list_subnetsList all available Telegraph subnet integrations with full metadata. Returns subnet ID, slug, protocol, name, description, available endpoints, input/output schemas, and signal mappings. No payment required.
tg_node_statusGet the status of the Telegraph Node. Returns public key, node identity, and chain connection info. No payment required.
tg_node_subnets_healthCheck the health of all subnet integrations on the Telegraph Node. Returns available subnets, status, and timestamp. No payment required.
Public scan report
scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it
- Code scan25 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 65 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Telegraph compares
Against every graded Maps and travel MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 78/100
- higher than 67% of 681 Maps and travel servers
- Tools
- 9
- the typical Maps and travel server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Downloads a week
- 23
- more than 9% of 150 Maps and travel servers with a package
What its tools let an agent do: 9 read
Install Telegraph in Claude Code, Cursor or VS Code
Runs npx -y telegraph-protocol-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add telegraph -- npx -y telegraph-protocol-mcp
What the publisher says
From the Telegraph repository's README, as published. We do not edit it. Read it on GitHub
@telegraph/mcp-server
MCP server exposing Telegraph Protocol AI inference APIs as tools with automatic x402 micropayments.
Connects any MCP-compatible agent (Claude Desktop, Cursor, ElizaOS, LangChain, OpenClaw, Goose, etc.) to Telegraph's network of AI miners — weather forecasting, deepfake detection, LLM inference, AI-text detection, signal monitoring — with zero crypto code in the agent. The MCP server handles private key custody, payment signing, and transaction settlement internally.
Miners can be Bittensor subnets, hosted models, or any private API integrated via YAML. Some tool and field names still say subnet for legacy reasons — read it as "miner".
Documentation
Quick Start
Option A — npx (no clone, recommended once published)
TELEGRAPH_NODE_URL=http://13.237.89.59:7044 \
TELEGRAPH_ENGINE_URL=http://13.237.89.59:8080 \
TELEGRAPH_DAEMON_URL=http://13.237.89.59:8081 \
TELEGRAPH_EVM_PRIVATE_KEY=0xyour_key_here \
npx -y telegraph-protocol-mcpOption B — from source
# 1. Clone and enter
git clone https://github.com/telegraphprotocol/telegraph-mcp
cd telegraph-mcp
# 2. Copy and edit .env
cp .env.example .env
# Edit: set TELEGRAPH_EVM_PRIVATE_KEY=0xyour_key_here
# 3. Install and build
npm install && npm run build
# 4. Run
npm startPublished to npm as telegraph-protocol-mcp and listed on the MCP Registry as io.github.telegraphprotocol/telegraph. Maintainers: see PUBLISHING.md.
Architecture
Agent (Claude / Cursor / Eliza / etc.)
│
│ MCP protocol (JSON-RPC over stdio)
│
┌──────▼─────────────────────────────────────────┐
│ Telegraph MCP Server (runs locally) │
│ │
│ ┌─────────┐ ┌──────────┐ ┌───────────────┐ │
│ │ Node │ │ Engine │ │ Daemon │ │
│ │ :7044 │ │ :8080 │ │ :8081 │ │
│ ├─────────┤ ├──────────┤ ├───────────────┤ │
│ │ Status │ │ Subnets │ │ Health │ │
│ │ Health │ │ Ask │ │ Categories │ │
│ │ Subnets │ │ Direct │ │ Questions │ │
│ │ Dynamic │ │ │ │ │ │
│ └─────────┘ └──────────┘ └───────────────┘ │
│ │
│ X402 payment handled transparently: │
│ request → 402 → sign EIP-3009 → retry │
└─────────────────────────────────────────────────┘Configuration
All via environment variables (.env file or inline):
*At least one private key required.
Available Tools
Node Tools (no payment)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Telegraph: common questions
- Is Telegraph MCP server safe?
- Mostly: it is graded B (78/100). Read the Telegraph safety report
- How do I install Telegraph?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Telegraph need an API key?
- Yes. The registry entry asks for
TELEGRAPH_EVM_PRIVATE_KEY,TELEGRAPH_SOLANA_PRIVATE_KEY. - Is Telegraph maintained?
- The last commit was 104 days ago (2026-07-23). The latest release is v1.0.0.
- What can I use instead of Telegraph?
- Servers from other publishers that do the same job: Weather Data MCP Server, Weather MCP Server and Repo Graph MCP server.
- How does Telegraph compare with other Maps and travel MCP servers?
- safety score 78/100 (higher than 67% of 681 Maps and travel servers); tools 9 (the typical Maps and travel server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Telegraph
Same job from other publishers: the closest match first, then the best rated.
- Weather Data MCP Server17 weather tools, no API keys: forecasts, alerts, air quality, marine, radar, lightning, wildfiresnot reviewedEstablishedA
- Weather MCP Serverproviding weather information, air quality data, and timezone utilities using the Open-Meteo API.not reviewedEstablishedA
- Repo GraphStructural graph map of any codebase so LLMs navigate by structure, not guesswork.not reviewedGrowingA
- VariflightVariFlight's official MCP server provides tools to query flight, weather, comfort, and fare data.not reviewedGrowingA
- Open MeteoGlobal weather via Open-Meteo: forecast, historical, marine, air quality, geocoding, elevation.not reviewedGrowingB