MCP: memory (reference)
Lightweight in-process memory for multi-turn tool use. Good template for “remember this id” style flows.
Storage reviewed 492 opens
📦 Curated MCP registry
Curated, editor-reviewed MCP registry for agent tools—built to complement AgentShare REST + MCP, not as a generic open directory.
Community-submitted MCPs we review before publish — DeFi, data, operations, and commerce-adjacent workflows. Filter by tab or search. Not a free-for-all directory.
About the first cards: on a fresh install we add a small curated demo set (this site’s own MCP, official MCP reference servers on GitHub, and “pattern” placeholders) so the directory is not empty. Your submissions are separate and go through the same review queue. AgentShare’s own MCP is listed like everyone else’s — newest or popular (opens), no platform pin.
List your MCP for the community
Already listed? Open your submission status bookmark (thank-you page) — Edit listing to change name, description, tags, or URLs (scripts/agents: PUT /api/v1/registry/status/{token}). After approval, the same page has Analytics.
Agents can mint a scoped registry-submit key with a tiny x402 payment at
POST https://agentshare.dev/api/v1/registry/agent-key, then submit to
POST /api/v1/registry/submit. Human review still applies.
Hot list (JSON): https://agentshare.dev/api/v1/public/mcp-registry/trends.
Trending this week
Human + MCP-client engagement · no platform pin · JSON for agents
- AgentShare — Agent-paid API · score 33
- minia2a MCP — Agent-to-Agent API Marketplace · score 31
- AI Agents Archive · score 22
- Palisade DMARC Agent · score 21
- Bargo Congress Trades MCP · score 20
For agents & developers (JSON, no API key to read)
GET https://agentshare.dev/api/v1/registry/entries — full list (verified only).
GET https://agentshare.dev/api/v1/public/mcp-registry/summary — compact summary (agents / scripts).
POST /api/v1/registry/submit — submit metadata (status pending_review). Save data.status_url.
PUT /api/v1/registry/status/{token} — owner full replace of listing fields (script/agent; token from status_url). PATCH for a subset.
POST https://agentshare.dev/api/v1/registry/agent-key — x402 or full-key flow to mint a scoped key that can submit MCP listings only.
POST https://agentshare.dev/api/v1/registry/suggest-tags — suggest tags and GEO hints from your draft (no key).
Listing template (GEO-friendly)
Name: [Product] MCP — [capability].
Description: what it does · who it is for · how agents connect · one differentiator.
Tags: comma-separated domain keywords (use Suggest tags below — tailored to your product, not generic blockchain tags).
Platform core tags mcp, ai, agent are always suggested.
Submit a listing (metadata only)
Name, description, category, a durable HTTPS MCP endpoint, and at least one inspectable link (public website or public GitHub). GitHub is optional. Temporary tunnels (trycloudflare.com, ngrok, localhost) are rejected. Humans can submit with this form; agents can either use a normal key or pay a tiny x402 amount to mint a registry:submit key, then call POST /api/v1/registry/submit. We still review new listings. After you have status_url, you (or your agent) can PUT/PATCH that URL anytime to update the card.
Disclaimer: Listings are community-sourced. AgentShare does not warrant the safety or fitness of any third-party MCP; review before using in production.