Pyrimid Protocol

What the Pyrimid Protocol MCP server does

The Pyrimid Protocol MCP server gives MCP clients access to a catalog of paid tools and AI/API products. Agents can search products by query, price, category, or verification status; inspect available categories; and preview how a purchase would be divided before committing funds.

Its purchase flow uses x402 payment metadata and USDC settlement on Base. When an affiliate is associated with a purchase, the protocol routes the configured commission to that affiliate. The remaining payment goes to the vendor after the protocol treasury allocation. The material describes a single affiliate layer rather than a multi-level referral structure.

This server fits buyer agents, recommendation systems, and agent frameworks that need to discover external paid capabilities. It can also support vendors and affiliate participants through the broader Pyrimid SDK, although the MCP listing itself focuses on buyer-facing catalog and purchase operations.

How it works

The Pyrimid Protocol MCP server is available at /api/mcp as a Streamable HTTP endpoint. A GET request returns server information and tool definitions, while MCP JSON-RPC 2.0 requests use POST. The public API is readable without payment, subject to rate limits, and returns JSON.

A typical interaction starts with pyrimid_browse, optionally followed by pyrimid_preview to inspect the expected commission split. pyrimid_buy then purchases the selected product through x402 with affiliate attribution. The README also lists paid test endpoints that return HTTP 402 responses containing x402 accepts[] metadata before payment. Payment can be supplied through X-PAYMENT or X-PAYMENT-TX after the transaction is completed.

Settlement occurs through deployed contracts on Base. The documented architecture includes a registry for affiliate and vendor registration, a catalog for product listings, a router for commission splitting and maximum-price protection, and a treasury for protocol operations. Payment verification checks onchain events and USDC transfers, with a five-minute expiry described in the security notes.

Tools and capabilities

The MCP server exposes five tools:

• pyrimid_browse searches the catalog using query, price, category, and verified-status filters.
• pyrimid_buy purchases a catalog product through x402 and includes affiliate attribution.
• pyrimid_preview shows the commission split before a purchase.
• pyrimid_categories lists product categories and their product counts.
• pyrimid_register_affiliate provides instructions for registering an affiliate onchain.

The catalog API also supports pagination. Separate statistics endpoints expose protocol, affiliate, and vendor data, but those endpoints are documented as API routes rather than additional MCP tools.

Setup and configuration

Connect an MCP client to the Streamable HTTP endpoint at https://pyrimid.ai/api/mcp, using the server's MCP JSON-RPC interface. The provided material does not specify client-specific configuration files or required environment variables for using the hosted server.

For local development, the repository instructions use Node.js package installation, an .env file copied from .env.example, and npm run dev. The repository also contains an npm SDK package, @pyrimid/sdk, with resolver, MCP server factory, middleware, and type definitions. SDK examples show optional affiliate and vendor identifiers, but no environment variable names are provided in the supplied material.

The public API has rate limits of 60 requests per minute for catalog and statistics routes and 120 requests per minute for the MCP route. Buyers should account for Base network transactions, USDC payments, x402 payment handling, and the documented five-minute payment verification window. Contract addresses and source verification are published through BaseScan links in the project documentation.