Skip to main content
Glama
molpha

Molpha MCP

Official
by molpha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Molpha MCP

No user-submitted related servers found.

    Related Servers

    • agent-guardrail

      rudimentall1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
      3
      24 PyPI
      1
      MIT

    • orcatrace-mcp

      jcislo
      A
      license
      A
      quality
      C
      maintenance
      MCP server for OrcaTrace, a pay-per-call Polymarket intelligence feed for AI agents. It provides tools to track smart money, whale entries with calibration, market repricings, and digests across 42K prediction markets, with payments settled via x402 on Base.
      13
      4 npm
      MIT

    • Pangle Coordinator

      aitools420
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for coordinating a permissionless swarm of AI agents to discover, investigate, and synthesize on-chain anomalies across EVM chains. Agents authenticate via off-chain ECDSA and earn reputation through useful contributions.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clear distinct purposes (e.g., derive_feed vs fetch_verified, verify vs execute), but there is some overlap: describe_feed also provides the latest committed value and can derive feed IDs, making it partially redundant with get_latest and derive_feed. The detailed descriptions help differentiate, but an agent might still hesitate between get_latest and describe_feed for reading a value.

    Naming Consistency4/5

    All tools share the 'molpha_' prefix and most follow a verb_noun pattern (get_latest, describe_feed, derive_feed, fetch_verified). However, 'molpha_verify' and 'molpha_execute' are bare verbs, and 'molpha_agent_status' is noun_noun, so the pattern is not fully consistent. Still, the naming is predictable and readable overall.

    Tool Count5/5

    With 8 tools, the server is well-scoped. Each tool covers a distinct operation in the Molpha workflow: reading state, deriving IDs, checking capabilities, fetching verified data, building calldata, and submitting to Solana. There are no redundant or extraneous tools.

    Completeness4/5

    The core lifecycle is covered: derive feed ID, fetch verified data, verify on EVM/Starknet, execute on Solana, and read back the result. Minor gaps exist, such as no explicit subscription management (though subscription status is readable) and no historical data access, but these are acceptable for the server's apparent purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources