Skip to main content
Glama

Related Servers

Alternatives to imd-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      CLI and local stdio MCP payment runtime for AI agents on macOS Apple Silicon. Supports x402 offer inspection and payment preparation, with signing and execution requiring foreground owner approval.
      21
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude Code to delegate tasks to persistent GitHub Copilot CLI sessions via MCP, inspect pending tool requests, and approve each operation once or deny it while continuing multi-turn context. It bridges ACP runtime sessions locally over stdio without a public service or background daemon.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Lets AI clients call paid x402ai endpoints — embeddings, summaries, and short answers — paying per call in USDC on Base via the x402 protocol, with per-payment and per-session spend caps plus a free inspector for decoding any x402 endpoint's payment challenge. Runs locally over stdio, needs no hosted account, and can operate in quote-only dry-run mode.
      5
      608 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients such as Claude Desktop and Cursor to use an encrypted local x402 wallet for AI agents, with tools to check balance and resources, call paid resources, discover and pay third-party x402 services, quote and execute token swaps, and view history under per-payment and daily caps.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to access hosted models and services via a local stdio bridge, with live model discovery, pricing, balance checks, and paid execution requiring cost estimates.
      MIT

    TDQS

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct endpoint or step in the request lifecycle (capabilities, check, import, quote, pay, order status, job, schedules), so an agent can easily tell them apart. No two tools appear to do the same thing, even though capabilities and check are both informational.

    Naming Consistency4/5

    All tools use lowercase snake_case with a consistent 'imd_' prefix, which makes the set predictable. The only minor deviation is mixing verb forms (e.g., imd_quote) with noun forms (e.g., imd_capabilities), but this is readable and not confusing.

    Tool Count5/5

    8 tools is well-scoped for an API client that handles discovery, evaluation, quoting, payment, and status/report retrieval. Each tool earns its place without redundancy.

    Completeness4/5

    The set covers the core paid-action workflow from capabilities through quote, pay, and status, plus repo import and job reports. Minor gaps exist, such as no schedule creation/deletion or job listing, but agents can work around these for primary use cases.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues