Skip to main content
Glama
Sign In
MAP Maraventano Agent Protocol

MAP Maraventano Agent Protocol

Official
by maraventano
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MAP Maraventano Agent Protocol

No user-submitted related servers found.

    Related Servers

    • genpark-agentic-commerce-agent

      alphaparkinc
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables agents to authenticate legitimate consumer shopping agents through cryptographic proof-of-delegation and block scraper abuse at retail gateways. It also exposes machine-to-machine catalog resolution, spend-bounded tokenized payment delegation, and automated alternating-offers bargaining over STDIO JSON-RPC.
      7
      MIT

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT
    • @integraledger/lcp-mcp-server

      @integraledger/lcp-mcp-serverofficial

      IntegraLedger
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only Model Context Protocol server exposing LCP tools to an AI agent — verify before pay, compute an atrHash, extract and place references across ten commerce protocols.
      Apache 2.0
    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

    A3.8/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool has a distinct, clearly defined purpose covering specific lessons or actions (e.g., 'choose-your-wallet-mode' vs 'explain-my-wallet' vs 'read-this-challenge'). No two tools overlap in function; descriptions provide fine-grained differentiation.

    Naming Consistency5/5

    All tool names follow a consistent lowercase-hyphenated pattern, mostly verb_phrase or question_phrase (e.g., 'get-a-wallet', 'what-is-x402', 'publish-catalog'). No mix of conventions like camelCase or underscores.

    Tool Count5/5

    23 tools is appropriate for a comprehensive curriculum covering orientation, wallet setup, payment protocols, troubleshooting, and publishing. Each tool earns its place as a distinct step or concept; no redundancy.

    Completeness5/5

    The tool set covers the full lifecycle: starting with wallet basics, through configuration, payment protocols (x402, AP2, ACP), troubleshooting, and catalog publishing. No obvious gaps for the stated domain of agent wallet and payment education.

    Resources