Telegraph

io.github.telegraphprotocolPublished by GitHub account telegraphprotocolv1.0.0Updated Oct 24, 2026

Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Local MCP server that gives an assistant paid access to Telegraph's decentralized AI inference network, settling per-call USDC micropayments automatically.

What you can do
Check node status, miner health and the live miner catalog, and list the miners the engine can route to, without payment. Run auto-routed or miner-specific inference such as weather prediction, deepfake detection, AI-text detection and LLM chat, embeddings, image generation and moderation, paid per call. Query the daemon for health, signal categories and collected signals filtered by category, source, time or interest. Miner-specific tools are discovered from the live registry and refreshed periodically, so the available tool set changes over time.
When to use it
Useful when you want an assistant to call a range of AI inference services, including weather, deepfake and AI-content detection, through one interface and pay per request in USDC rather than holding separate provider accounts.
Requirements
Runs locally over stdio, typically via npx or a built Node.js build. Requires TELEGRAPH_NODE_URL, TELEGRAPH_ENGINE_URL and TELEGRAPH_DAEMON_URL, plus at least one of TELEGRAPH_EVM_PRIVATE_KEY or TELEGRAPH_SOLANA_PRIVATE_KEY. Optional EVM_NETWORK, SVM_NETWORK and REFRESH_INTERVAL_MS. Network access to the Telegraph endpoints is needed.
Before you install
Paid tools spend real USDC per call, signed with the private key you supply; the README advises a burner wallet funded only with what you need. The private key is held by the local process, so protect the environment configuration. Miner tools are auto-discovered from a remote registry and change without notice, and requests and payment details go to third-party Telegraph endpoints.

Installation

In SourceWeft

  1. Open Telegraph in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Telegraph MCP server

Gives any MCP client (Claude Code, Claude Desktop, Cursor, Goose, Continue, ElizaOS, LangChain, ...) the Telegraph network: ask questions that the best-ranked miner answers, browse every intent, miner and ranking, and pay per ask in USDC from escrow or by x402. One setting, nine tools.

Quick start

You need Node 18+ and, for paid asks, the private key of a wallet made for this (never your main wallet). Free tools work without a key.

Claude Code

bash
claude mcp add telegraph -e TELEGRAPH_PRIVATE_KEY=0xyour_key -- npx -y @telegraphprotocol/telegraph-protocol-mcp

Claude Desktop, Cursor and most other clients (claude_desktop_config.json, ~/.cursor/mcp.json, ...)

json
{  "mcpServers": {    "telegraph": {      "command": "npx",      "args": ["-y", "@telegraphprotocol/telegraph-protocol-mcp"],      "env": { "TELEGRAPH_PRIVATE_KEY": "0xyour_key" }    }  }}

Then ask your agent things like "what is the BTC price?", "which miners serve weather and how do they rank?" or "how much is in my Telegraph escrow?". More client configs are in examples/.

Settings

VariableDefaultWhat it is
TELEGRAPH_PRIVATE_KEYnoneWallet that pays for asks. Without it only the free tools work. (TELEGRAPH_EVM_PRIVATE_KEY, the v1 name, also works.)
TELEGRAPH_URLhttps://devnode.telegraphprotocol.comThe node (Telegraph beta 2)
TELEGRAPH_PAYMENTautoauto: escrow first, then x402. escrow or x402: only that one
TELEGRAPH_RPC_URLpublic Sepolia RPCChain RPC, for the balance and deposit tools
TELEGRAPH_DIAMOND, TELEGRAPH_CHAIN_IDbeta 2'sThe contract that holds escrow, and its chain

Tools

ToolCostWhat it does
telegraph_ask~$0.01Ask a question (optionally an exact intent and params); the node routes it to the top live miner
telegraph_ask_minerthe miner's priceAsk one miner you choose, or call one of its endpoints directly
telegraph_find_intentsfreeSearch the 130+ intents (kinds of question)
telegraph_intentfreeOne intent's kind, params, answer fields and top miners
telegraph_find_minersfreeAn intent's miners with rank, score, price and endpoints, or a word search over all miners
telegraph_rankingfreeThe latest epoch's ranking, per intent
telegraph_accountfreeWallet USDC and ETH, and the escrow balance, debt and pending withdrawal
telegraph_depositgasMove wallet USDC into escrow (approve + depositUSDC)
telegraph_docsfreeBuilt-in guides: getting started, payments, intents and ranking, errors. Also served as MCP resources (telegraph://docs/...)

Payments

  • Escrow (used first): deposit USDC once with telegraph_deposit. Each ask carries a signature that proves intent but can't move funds. Asks are deducted at the epoch close, and a failed ask is never billed.
  • x402 (fallback): when escrow is empty, the server pays each ask from the wallet's USDC. If the ask then fails, the node credits the payment to your escrow, so it stays yours.

Details, debt and withdrawing: guides/2-payments.md.

Test funds (beta 2)

Beta 2 runs on Ethereum Sepolia. Its USDC (0xcc194e1a843B658526D0D5C431f670028582Ae17) is a test token anyone can mint with mint(yourAddress, amount) (6 decimals). Gas needs a little Sepolia ETH from a public faucet.

Security

  • Use a wallet made for this, holding only what you plan to spend.
  • The key stays in the MCP server process; the agent never sees it.
  • The server runs locally over stdio and opens no port.

Development

bash
npm install && npm run buildnode scripts/smoke.mjs                                       # free tools against the nodeTELEGRAPH_PRIVATE_KEY=0x... node scripts/smoke.mjs paid      # plus three asks (~$0.03)node scripts/smoke.mjs call telegraph_intent '{"intent":"CRYPTO_PRICE_USD"}'npx @modelcontextprotocol/inspector dist/index.js            # browse the tools

Architecture: docs/architecture.md. Problems: docs/troubleshooting.md.

Source: README.md at commit 097e3ec

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts