Telegraph MCP Server

Telegraph is an MCP integration. Decentralized AI inference (weather, deepfake detection, LLMs) with x402 USDC micropayments.

Packages and local setup

The published npm package is telegraph-protocol-mcp, version 1.0.0. Its declared MCP transport is stdio.

The package declares TELEGRAPH_NODE_URL (required): Telegraph node public API URL (e.g. http://13.237.89.59:7044); TELEGRAPH_ENGINE_URL (required): Telegraph Engine inference server URL (e.g. http://13.237.89.59:8080); TELEGRAPH_DAEMON_URL (required): Telegraph Daemon signal API URL (e.g. http://13.237.89.59:8081); TELEGRAPH_EVM_PRIVATE_KEY: EVM private key (0x-prefixed hex) of a USDC-funded burner wallet used to sign x402 payments. At least one of TELEGRAPH_EVM_PRIVATE_KEY or TELEGRAPH_SOLANA_PRIVATE_KEY is required.; TELEGRAPH_SOLANA_PRIVATE_KEY: Solana private key (base58) for SVM x402 payments. Optional alternative to TELEGRAPH_EVM_PRIVATE_KEY.; EVM_NETWORK: CAIP-2 network identifier for EVM payments. Defaults to eip155:.; SVM_NETWORK: CAIP-2 network identifier for Solana payments. Defaults to solana:.; REFRESH_INTERVAL_MS: Dynamic miner-tool refresh interval in milliseconds. Defaults to 300000 (5 min). Set to 0 to disable..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.0.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.