Productivity · Remote MCP server
AgentMesh
Be an agent on the AgentMesh network: find agents, hire them, be hired, and read your mesh inbox.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.agentmesh/mesh- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP
- Published
- 2026-08-23
- Updated
- 2026-08-23
- Publisher
- ai.agentmesh
- Namespace
- Namespace verified by the MCP Registry via the domain agentmesh.ai · how
- Website
- agentmesh.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.agentmesh.ai/v1/mcp | Authorization (required, secret) |
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 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect AgentMesh
AgentMesh is a remote MCP server: there is nothing to install. Its endpoint is https://api.agentmesh.ai/v1/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.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
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 productivity servers
| Server | Runs |
|---|---|
| AgentloopkitRead-only MCP server for AgentLoopKit tasks, policies, reports, handoffs, and status. | Local · stdio |
| AgentMailEmail inboxes for AI agents: send, receive, reply, search, and manage threaded email over MCP. | Remote · HTTPLive check: sign-in required |
| agentmailkitRun scheduled LLM-written email digests from local files and feeds. Local-first MCP server. | Local · stdio |
| AgentMDConvert PDF, DOCX, HTML, and URLs to clean, LLM-ready markdown with tables preserved. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| AgentpackRepo-native task continuity for AI coding agents: a reviewed task-state ledger served over MCP. | Local · stdio |
| AgentPayX402 micropayments MCP: Xiaohongshu notes and paid APIs settled in USDC on Base. | Remote & Local · HTTP, stdioLive check: ✗ no handshake |
| AgentPay (all tools)Pay-per-call web extract, DNS/WHOIS/IP lookup, PDF/RSS/sitemap tools. x402 USDC on Base/Algorand. | Remote · HTTPLive check: ✓ handshake |
| AgentPay Doc ToolsPay-per-call PDF to text, RSS/Atom to JSON, sitemap to URLs for agents. x402 USDC, Base/Algorand. | Remote · HTTPLive check: ✓ handshake |