mcpbeat Sign in

Meta Stamp Pockets MCP Server

by christebob Your server? Claim it
answering

Meta Stamp Pockets is answering right now. Last checked 14 min ago. It exposes 3 tools. Last commit 30 Jul 2026.

Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP.

Uptime history 91 days of history · worst day 96%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
360 ms
Response time
average over 24h
0
Stars
last commit 30 Jul 2026

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 8 October 2026. No other catalogue keeps this.

30 Oct a tool description was rewritten pull_content
8 Oct 3 tool descriptions were rewritten list_pockets, pull_content, search_pockets
8 Oct 2 tools changed the parameters they ask for list_pockets, search_pockets
8 Oct a tool changed version

Nothing serious here today

Today is the operative word: we check Meta Stamp Pockets every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add meta-stamp-pockets --transport http https://metastampv3-production.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://metastampv3-production.up.railway.app/mcp
~/.codex/config.toml
[mcp_servers.meta-stamp-pockets]
url = "https://metastampv3-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "meta-stamp-pockets": {
      "url": "https://metastampv3-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "meta-stamp-pockets": {
      "type": "http",
      "url": "https://metastampv3-production.up.railway.app/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

pockets
list_pockets
List all available content pockets in the Meta-Stamp Pockets catalog, optionally filtered by creator. Use this tool when an AI agent needs to browse the full catalog or see everything available from a specific creator. Prefer search_pockets when looking for specific topics. Does NOT retrieve content — use pull_content with the returned pocket_id to access actual content. Works without authentication; anonymous results omit content_url and creator_id, which are returned only with a valid Bearer token (pkt_ API key). The optional creator_id parameter filters results to a single creator's pockets and requires an API key (anonymous calls using it are refused with an api_key_required error and a registration_url). Returns a paginated list of pockets with IDs, titles, descriptions, creators, content types, and pricing tiers. Each row also carries catalog_id, access ('open' or 'closed') and delivery ('file' or 'listing'); closed-catalog and listing rows never include content_url. Unlisted pockets are never listed; they stay reachable by pocket_id (pull_content) or by an exact isrc in search_pockets.
search_pockets
Search the Meta-Stamp Pockets catalog by keyword, creator email, or content category. Use this tool when an AI agent needs to discover available licensed content before pulling it. Ideal for finding relevant pockets when the agent knows what topic or creator it needs but not the specific pocket ID. Does NOT retrieve content — use pull_content with the returned pocket_id to access actual content. Works without authentication for query, isrc and content_type; anonymous results omit content_url and creator_id, which are returned only with a valid Bearer token (pkt_ API key). The query parameter is matched as a literal keyword and accepts natural language search terms or category keywords; the creator_email parameter restricts results to a single creator by their email address and requires an API key (anonymous calls using it are refused with an api_key_required error and a registration_url). The isrc parameter is an exact full-ISRC lookup. Provide at least one of query, creator_email or isrc. Returns matching pockets with their IDs, titles, descriptions, creators, content types, and pricing tiers. Each row also carries catalog_id, access ('open' or 'closed') and delivery ('file' or 'listing'). Closed-catalog rows cannot be pulled and never include content_url; listing rows show title, isrc and owner and never include content_url. Unlisted pockets are excluded from results unless found by an exact isrc match. Use the limit parameter to control page size.
pull
pull_content
Pull licensed creator content from a specific pocket by ID. Use this tool when an AI agent needs to retrieve verified, provenance-tracked content for generation, RAG, and inference use. Training use requires a separate training license — see training_use in the agreement terms. Do NOT use for browsing or discovery — use search_pockets or list_pockets instead. Requires a valid Bearer token for authentication; unauthenticated requests return HTTP 402. Successful pulls trigger a metered charge at the pocket's own price (quoted as owner_price on the receipt; $0.0025 platform default only when a pocket sets none) and the transaction is logged for creator royalty distribution. The pocket_id parameter is a 24-character hex string identifying the specific content pocket to pull from. Returns the full content payload with provenance metadata including creator attribution and license terms. Every call returns a receipt of the same shape (receipt_id, outcome, reason, amount_paid, terms, content_hash, and agent_count / agent_work_count: how many times this agent has accessed the owner's account and this work, this call included) with a public verify_url: on success under 'receipt' in the result (outcome 'delivered'), on an HTTP 402 refusal under 'receipt' in the error body (outcome 'refused', reason 'registration_required' when no valid API key is presented, 'payment_required' when the wallet balance is too low or the card charge fails). A pocket whose rights holder has closed its catalog is refused for every caller, with or without a key, as a normal result (not a 402) with reason 'catalog_closed', owner_price null and the receipt under 'receipt'; nothing is delivered or charged. A listing-only pocket (delivery 'listing' in search results) has no file: its pull is charged the owner's per-pull price like any other and returns delivery 'listing' with 'content' set to the listing object {title, isrc, owner, terms, link} and no download URL. content_hash is the sha256 hex of the delivered 'content' field only: a string is hashed as its UTF-8 bytes, an object as UTF-8 JSON with sorted keys and no whitespace.

Endpoints

URLTransportStateLatencyChecked
https://metastampv3-production.up.railway.app/mcp streamable-http answering 346 ms 14 min ago

Alternatives to Meta Stamp Pockets

same job, measured the same way
E
Email
by primitive

Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.

14 tools answering
Subscriptions
by jdhart81

Verified monthly-seat catalog, account attribution, quota, overage, and MRR infrastructure.

10 tools answering
Veriswarm MCP
by veriswarm

VeriSwarm MCP Server — Trust infrastructure for AI agents via Model Context Protocol

141 installs/wk local only
x402 Facilitator Proxy
by seob5285-alt

Multi-tenant HTTP 402 infrastructure gateway and stdio MCP server for machine payments.

49 installs/wk local only
KeyID
by keyid-ai

Signup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents.

94 installs/wk answering
MCP Guardian
by rudraneel93

Security, cost, and health governance proxy for MCP infrastructure

199 installs/wk local only
Tailscale MCP Server
by itunified-io

Secure MCP access for private infrastructure over Tailscale — 48 tools across 9 domains

58 installs/wk local only
Report Needs MCP Server
by jarvisonm4

MCP server for AI agents to report infrastructure needs they encounter during task execution

40 installs/wk local only

Meta Stamp Pockets — questions

Answers built from our own checks of this server.

What can Meta Stamp Pockets do?
It exposes 3 tools, read directly from the server on our last check. Among them: list_pockets, pull_content, search_pockets. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Meta Stamp Pockets working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 360 ms. The bar chart above shows every period we have measured.
How do I connect Meta Stamp Pockets?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Meta Stamp Pockets need an API key?
No. Meta Stamp Pockets completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Meta Stamp Pockets?
It answers our handshake in 360 ms on average, which is faster than 38% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Meta Stamp Pockets open source?
The code is open source: it is published under the MIT licence, written in Python and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at metastampv3-production.up.railway.app, which runs on its operator's own terms.