MCP.Market

Molpha MCP server

by molpha·io.github.molpha/mcp·v0.1.2·2 stars

MCP server that lets AI agents create, fetch, verify, and publish Molpha oracle data.

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

2 stars26 downloads/wk

Reviews

Write one

Nobody has reviewed Molpha MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Molpha MCP tools (8, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • molpha_agent_status

    Read the caller's x402 agent escrow (advisory: USDC ATA balance, amount committed to unsettled rounds, unsettled round count) and the next round's quoted price for a given quorum. Escrow is derived server-side per (payer, gateway). A non-existent escrow is normal pre-first-round — it's created lazily. Call before payment: "x402" fetches to see whether the escrow is already funded, or to pre-fund i

  • molpha_derive_feed

    Locally derive the feedId for a declarative spec (apiConfig + quorum) — no transaction, no subscription required. feedId = keccak256(owner || apiConfigHash || signaturesRequired); the feed itself is created lazily on-chain at first settle (subscription or x402 round). Call this to preview a feedId before molpha_fetch_verified, or to check what feedId a given spec resolves to for the current signer

  • molpha_describe_feed

    Read a feed's on-chain state (last committed value, registryVersion, signaturesRequired) and the caller's subscription status. Pass feedId directly, or apiConfig + signaturesRequired to derive it first (see molpha_derive_feed). A missing feed account is normal pre-first-settle — feeds are created lazily. `feed.valueKind` is the attested encoding of the stored bytes ("value" = raw payload, "hash" =

  • molpha_executewrite action

    Submit a signed DataUpdate to the Solana feed via submit_data_update. Pass the output of molpha_fetch_verified through unmodified — both the artifact shape ({ dataUpdate, signature }) and the flat shape ({ s, commitmentAddr, timestamp }) are accepted, and short hex fields are zero-padded server-side. Permissionless on-chain; the owner key pays SOL fees. EVM/Starknet execution is deliberately out o

  • molpha_fetch_verified
  • molpha_get_capabilities

    Returns the current Molpha verification surface: active registryVersion, registered node set, gateway endpoints, supported chains, signing scheme, and x402 spend caps. Call first to learn where a signed result can be verified.

  • molpha_get_latest

    Read the latest on-chain feed account for a Molpha feedId. `valueKind` is the attested encoding of the stored bytes ("value" = raw payload, "hash" = keccak digest) — it is not a scale hint. Molpha does not attest decimals on-chain; see molpha_describe_feed's valueEncoding for the (unsigned) apiConfig provenance.

  • molpha_verify

    Build the verifier address and call args for a signed DataUpdate on EVM or Starknet. This tool stops at calldata by design, not by omission: the Molpha verifier is stateless, so the agent (or its contract) executes verify() itself and the server never submits an EVM/Starknet transaction or vouches for a result it did not verify on-chain. There is no EVM/Starknet execution path anywhere in this MCP

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan39 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 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Molpha MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
Tools
8
the typical server has 7
Tools that change things
13%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers
Downloads a week
26
more than 13% of 12,191 servers with a package

What its tools let an agent do: 7 read · 1 change

Install Molpha MCP in Claude Code, Cursor or VS Code

Runs npx -y @molpha/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp -- npx -y @molpha/mcp
Add to Cursor

What the publisher says

From the Molpha MCP repository's README, as published. We do not edit it. Read it on GitHub

Molpha MCP

A Model Context Protocol (MCP) server that lets AI agents create, fetch, verify, and publish Molpha oracle data.

Molpha turns HTTP API responses into threshold-signed payloads that can be verified on Solana, EVM, and Starknet. This server exposes that workflow as a small set of MCP tools and keeps signing behind a local, Privy, or Turnkey-backed 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 may consume subscription quota unless dry-run mode is enabled.

What you can do

  • Discover the active registry, oracle nodes, gateways, and verifier deployments.
  • Derive a feedId locally from a declarative API spec — no transaction, no subscription required. Feeds are created lazily on first settle.
  • Request a threshold-signed result and build verifier arguments for multiple chains, paid for either by an active USDC subscription or a self-funded x402 round.
  • Build EVM/Starknet verifier call args, or submit a verified update to a Solana feed.
  • Use a local keypair, Privy server wallet, or Turnkey wallet without changing the MCP tool surface.
  • Put daily caps and a global dry-run default around agent-initiated writes and x402 spend.

MCP tools

molphaverify stops at calldata by design: the Molpha verifier is stateless, so the agent executes verify() itself and the server never submits an EVM/Starknet transaction or vouches for a result it did not verify on-chain. Solana is the one leg this server settles — via molphaexecute or molphafetchverified's autoSubmit — and there is no standalone Solana verify-simulation path; submit, then read the result back with molphagetlatest.

molphaexecute and molphaverify take the molphafetchverified response as-is: no field remapping between calls, and short hex fields (the gateway emits a one-signer signersBitmap as "4") are zero-padded to their canonical widths server-side.

Quick start

Requirements

  • Node.js 20 or later
  • A Solana wallet funded with Devnet SOL
  • Devnet USDC if you plan to use an active subscription or the x402 pay-per-request path
  • An MCP client such as Cursor, Claude Desktop, or Codex

1. Install and build

git clone https://github.com/molpha/mcp.git
cd mcp
npm ci
cp .env.example .env
npm run build

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Molpha MCP: common questions

Is Molpha MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Molpha MCP safety report
How do I install Molpha MCP?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Molpha MCP need an API key?
Yes. The registry entry asks for PRIVY_APP_ID, PRIVY_APP_SECRET, PRIVY_WALLET_ID, TURNKEY_API_PUBLIC_KEY and 2 more.
Is Molpha MCP maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.1.2.
How does Molpha MCP compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); tools 8 (the typical server has 7); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.