Developer · Local MCP server
Telegraph
Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.telegraphprotocol/telegraph- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-30
- Updated
- 2026-06-30
- Publisher
- telegraphprotocol (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/telegraphprotocol) · how
- Listed under
- Weather MCP servers
- Repository
- github.com/telegraphprotocol/telegraph-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | telegraph-protocol-mcp | 1.0.0 | stdio |
How to connect Telegraph
Telegraph runs locally from a Node.js package published to the npm registry: telegraph-protocol-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y telegraph-protocol-mcp@1.0.0. It reads these environment variables: TELEGRAPH_NODE_URL (required), TELEGRAPH_ENGINE_URL (required), TELEGRAPH_DAEMON_URL (required), TELEGRAPH_EVM_PRIVATE_KEY (secret), TELEGRAPH_SOLANA_PRIVATE_KEY (secret), EVM_NETWORK, SVM_NETWORK and REFRESH_INTERVAL_MS; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"telegraph": {
"command": "npx",
"args": [
"-y",
"telegraph-protocol-mcp@1.0.0"
],
"env": {
"TELEGRAPH_NODE_URL": "<value>",
"TELEGRAPH_ENGINE_URL": "<value>",
"TELEGRAPH_DAEMON_URL": "<value>",
"TELEGRAPH_EVM_PRIVATE_KEY": "<secret>",
"TELEGRAPH_SOLANA_PRIVATE_KEY": "<secret>",
"EVM_NETWORK": "<value>",
"SVM_NETWORK": "<value>",
"REFRESH_INTERVAL_MS": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Tech Stack DetectorDetect the technology stack behind any website: frameworks, CMS, analytics, and more from one POST. | Remote · HTTPLive check: ✓ handshake |
| Technology Stack Detection APIDetect 50+ technologies on any website: CMS, frameworks, analytics, CDN. x402. | Remote · SSELive check: ✗ no handshake |
| TelbaseDeploy any web project with one command. AI-native platform with self-healing feedback. | Local · stdio |
| Telegram MCPTelegram bridge for your MCP-compatible agent. Bidirectional, no LLM in our stack. | Remote · HTTPLive check: ✗ no handshake |
| telleroutlook MCP-SERVERWasmAgent MCP server - WASM-sandboxed code execution with capability manifests and Tasks API. | Local · stdio |
| Telys - on-device memoryPrivate on-device memory & retrieval for AI assistants - offline vector + lexical search. | Local · stdio |
| TemperaPersistent episodic memory for AI coding: capture, retrieve, brief, dream cycle, cross-project. | Local · stdio |
| TempoGraphCode graph context engine with 24 MCP tools. 170+ languages via tree-sitter. | Local · stdio |