Other · Remote MCP server
AgentPay - Pay-per-call AI Microservices
34 pay-per-call AI microservices via x402, USDC on Base, no API keys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
help.agentpay/agentpay- Version
- 1.3.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- help.agentpay
- Namespace
- Namespace verified by the MCP Registry via the domain agentpay.help · how
- Website
- agentpay.help
- Repository
- github.com/ronaldanton/x402-shop
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://agentpay.help/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- agentpay 1.0.0 · protocol 2025-06-18
- Tools discovered
34 - show names
summarize,classify-insurance,sentiment,extract,translate,code-review,insurance-analysis,token-safety,wallet-risk,web-scrape,crypto-price,image-describe,defi-yields,threat-intel,sanctions-screen,market-intel,on-chain-events,content-safety,agent-reputation,legal-lookup,news-feed,weather-data,web-search,memory,geocode,eth-gas,prediction-market,deep-research,buy-credits,buy-credits-starter,buy-credits-pro,batch,ad-copy,lead-score- Checked on
- 2026-10-05
How to connect AgentPay - Pay-per-call AI Microservices
AgentPay - Pay-per-call AI Microservices is a remote MCP server: there is nothing to install. Its endpoint is https://agentpay.help/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| Agentmarketplace MCPDiscover MCP servers + tools, auto-install into any client, pay for x402 endpoints in USDC. | Local · stdio |
| AgentNetAgent-to-agent referral network. Discover, recommend, and refer users between AI agents via MCP. | Remote · HTTPLive check: ✗ no handshake |
| AgentObserver - Check x402 Dependencies Before PayingCheck Exa, BlockRun, OneSource, Apify and other x402 dependencies before invoking or paying. | Remote · HTTPLive check: ✗ no handshake |
| AgentosBuild and manage policy-compliant AI agents with safety enforcement and compliance checking. | Local · stdio |
| AgentPay - trust routing + spend caps for x402 agentsBuyer-side trust oracle + capped sessions for x402 agents: verified_route, receipts, 17 free tools. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| AgentPhoneGive AI agents real phone numbers, messages, and voice calls via MCP. | Remote & Local · HTTP, stdioLive check: sign-in required |
| AgentpmtAI agent marketplace for automated employees, workflows, skills, and tool orchestration. | Remote · HTTPLive check: sign-in required |
| AgentprofileOne profile - skills, credentials, and memory - synced to every agent tool via one MCP URL. | Remote · HTTPLive check: sign-in required |