MCP

36 / 100

20+ small real x402 endpoints on Base mainnet USDC, each demonstrating a distinct payment mechanic: oracle, auction, escrow, invoicing, task-runner, prediction market, and more.

Scanned 2h ago · 0 views · Open site

Checks

• HTTPS5/5

  Served over HTTPS.

• llms.txt0/12

  No /llms.txt.

  Fix: Publish https://lab.paidapis.net/llms.txt with a short description, key URLs, and how an agent should call you.

• Agent manifest0/15

  No /.well-known/ai-agent.json.

  Fix: Publish https://lab.paidapis.net/.well-known/ai-agent.json with name, description, capabilities, contact, auth, and pricing.

• A2A agent card0/12

  No /.well-known/agent-card.json.

  Fix: Publish https://lab.paidapis.net/.well-known/agent-card.json with name, url, and skills or capabilities.

• MCP endpoint0/12

  No MCP document or endpoint found.

  Fix: Publish /.well-known/mcp.json (or an MCP resource metadata document) pointing at your MCP server.

• OpenAPI spec12/12

  Valid OpenAPI/Swagger document.

• Named capabilities8/8

  25 named capabilities (25 with descriptions).

• I/O schemas8/8

  Found 40 schema signals.

• Machine-readable pricing0/8

  No machine-readable pricing.

  Fix: Add a pricing object to ai-agent.json, or publish /pricing.json with currency and product amounts.

• Auth, contact, rate limits3/8

  Declared: contact.

  Fix: Declare contact, auth, and rateLimit in ai-agent.json (and OpenAPI info.contact / securitySchemes).

6 checks short of a perfect 100. The fix lines above are the report — what to publish, at which path.

How scoring works · Recently graded · Back to the board