A Model Context Protocol (MCP) server that lets AI agents fetch signed Molpha oracle data, publish it on Solana, and build verifier calldata for EVM and Starknet.
概览
A Model Context Protocol (MCP) server that lets AI agents fetch signed Molpha oracle data, publish it on Solana, and build verifier calldata for EVM and Starknet. Molpha turns HTTP API responses into threshold-signed payloads that can be verified on Solana, EVM, and Starknet. This server exposes that workflow as MCP tools, with signing behind a local, Privy, or Turnkey wallet, or, on mcp.molpha.io, behind your own wallet. This release targets Solana Devnet and Sepolia verifier networks. Treat it as testnet software, not a production security boundary. Write tools spend SOL, and round tools may consume subscription quota or pay USDC for x402 rounds, unless dry-run mode is enabled. Nothing to install, and no keys to hand over. Add the URL to your client. The read tools work straight away. The server has no wallet of its own, so name the one you mean: submitter for describe_feed and get_latest_value, payer for get_x402_status.
README
以下为原文 README 节选，完整内容请查看原文。
Molpha MCP
A Model Context Protocol (MCP) server that lets AI agents fetch signed Molpha oracle data, publish it on Solana, and build verifier calldata for EVM and Starknet.
Molpha turns HTTP API responses into threshold-signed payloads that can be verified on Solana, EVM, and Starknet. This server exposes that workflow as MCP tools, with signing behind a local, Privy, or Turnkey wallet, or, on mcp.molpha.io, behind your own wallet.
[!WARNING] This release targets Solana Devnet and Sepolia verifier networks. Treat it as testnet software, not a production security boundary. Write tools spend SOL, and round tools may consume subscription quota or pay USDC for x402 rounds, unless dry-run mode is enabled.
Quick start
Two recommended ways to connect:
| mcp.molpha.io | Local (stdio) | |
|---|---|---|
| Install | Nothing: add the URL to your client | npx, Node.js 24 or later |
| Signer | Your own wallet. The server holds no key. | Local keypair, Privy or Turnkey, held by the server |
| Subscription rounds | Sign in with SIWX, then execute_subscription_round |
execute_subscription_round |
| Spending limits | Your wallet’s own policy | Dry-run lock and daily caps in the server |
| Best for | Getting started, agents that bring their own wallet | Unattended agents, private API sources |
mcp.molpha.io
Nothing to install, and no keys to hand over. Add the URL to your client.
Claude Code:
claude mcp add --transport http molpha https://mcp.molpha.io/mcp
Cursor (.cursor/mcp.json):
{ "mcpServers": { "molpha": { "url": "https://mcp.molpha.io/mcp" } } }
The read tools work straight away. The server has no wallet of its own, so name the one you mean: submitter for describe_feed and get_latest_value, payer for get_x402_status.
Anything that needs a signature is returned for your own wallet to sign, so each such operation is two or three tool calls around one signature:
| Operation | Tools, in order | The wallet signs |
|---|---|---|
| Subscription round | begin_session → complete_session → execute_subscription_round |
A text message, once per session |
| x402 round | prepare_x402_round → execute_x402_round |
A USDC transfer, not broadcast |
| Solana submit | prepare_submit_attestation → send_signed_transaction |
The submit transaction |
autoSubmit, dryRun and encryptSecrets are not offered here. Set spending limits in the wallet’s own policy, and use the local server for private API work.
安装
npx -y @molpha/[email protected] doctor配置
{ "mcpServers": { "molpha": { "url": "https://mcp.molpha.io/mcp" } } }