Meta Stamp Pockets MCP server
online · 100% uptimeio.github.Christebob/meta-stamp-pockets·v1.0.0Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP.
0 stars
Reviews
Write oneNobody has reviewed Meta Stamp Pockets yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Meta Stamp Pockets tools (3)
write = sends, deletes, buys or postslist_pocketsFreeList 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. Requires a valid Bearer token. Optional creator_id parameter filters results to a single creator's pockets. Returns a paginated list of pockets with IDs, titles, descriptions, creators, content types, and pricing tiers.
pull_contentFreePull 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, or training purposes. 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 401. Successful pulls trigger a metered charge ($0.001–$0.25 depending on content tier) 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.
search_pocketsFreeSearch 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. Requires a valid Bearer token. The query parameter accepts natural language search terms or category keywords; the creator_email parameter restricts results to a single creator by their email address. Provide at least one of query or creator_email. Returns matching pockets with their IDs, titles, descriptions, creators, content types, and pricing tiers. Use the limit parameter to control page size.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 493ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 57 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Meta Stamp Pockets compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 87/100
- higher than 78% of 4,460 AI and agents servers
- Tools
- 3
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 102 ms
- faster than 86% of 2,331 AI and agents servers
What its tools let an agent do: 3 read
Install Meta Stamp Pockets in Claude Code, Cursor or VS Code
claude mcp add --transport http meta-stamp-pockets https://metastampv3-production.up.railway.app/mcp
What the publisher says
From the Meta Stamp Pockets repository's README, as published. We do not edit it. Read it on GitHub
Meta-Stamp Pockets
Attribution and settlement infrastructure for AI agent access.
AI agents consume creator content at machine speed. Meta-Stamp Pockets is the payment and licensing rail at the point of access: every request either settles payment to the creator or generates a timestamped denial record — a documented licensing opportunity, declined. License, or leave a paper trail.
What It Does
- Serves licensed, provenance-tracked creator content to AI agents via the Model Context Protocol (MCP) and HTTP 402
- Per-pull pricing set by the creator — $1.00 default, configurable per asset
- 85% of every pull goes to the creator, automatically
- Every access attempt lands in an immutable event ledger — paid pulls settle, refusals leave evidence
How Content Gets Protected
Two registration paths, each matched to how content arrives:
- Direct upload — the file is perceptually fingerprinted (audio spectral analysis, image/video hashing, text signatures) and then discarded. The fingerprint travels; the file stays with the creator.
- YouTube URL — ownership is verified through OAuth channel connection; the pocket carries metadata, transcript, and the access ledger. YouTube remains the canonical host.
Three protection layers are filed IP (12 U.S. provisional patent filings, sole inventor). Two run live today: multi-modal fingerprinting and the immutable access ledger. Embedded watermarking is the roadmap layer.
MCP Server
Connect AI agents to Meta-Stamp Pockets via the Model Context Protocol:
https://metastampv3-production.up.railway.app/mcpAvailable tools:
- search_pockets — search licensed creator content by keyword
- pull_content — retrieve provenance-verified content from a Pocket
- list_pockets — list all available Pockets, optionally filtered by creator
Authentication: Bearer token required. Register at https://metastampv3-production.up.railway.app/docs
Live Demo
https://metastampv3-production.up.railway.app/demo
API Docs
https://metastampv3-production.up.railway.app/docs
For Creators
If you're a creator interested in licensing your content through Meta-Stamp Pockets, contact chriscoynetalent@gmail.com.
For Enterprise
If you represent an AI platform interested in licensing access to the Meta-Stamp creator network, contact chriscoynetalent@gmail.com.
Meta-Stamp, LLC · Simi Valley, CA · Patent pending
Nothing above is checked by us. What we check is on the safety report.
Meta Stamp Pockets: common questions
- Is Meta Stamp Pockets MCP server safe?
- Yes, by our scan: it is graded A (87/100). Read the Meta Stamp Pockets safety report
- How do I install Meta Stamp Pockets?
- It runs remotely at metastampv3-production.up.railway.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Meta Stamp Pockets need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Meta Stamp Pockets maintained?
- The last commit was 98 days ago (2026-07-29). The latest release is v1.0.0.
- Is Meta Stamp Pockets up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of Meta Stamp Pockets?
- Servers from other publishers that do the same job: Mockserver MCP server, agent-device MCP server and Pm Claude Skills MCP server.
- How does Meta Stamp Pockets compare with other AI and agents MCP servers?
- safety score 87/100 (higher than 78% of 4,460 AI and agents servers); tools 3 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to Meta Stamp Pockets
Same job from other publishers: the closest match first, then the best rated.
- MockserverMock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.not reviewedEstablishedA
- agent-deviceOpen source device layer for AI agents: control mobile, web, TV, and desktop apps over MCPnot reviewedWidely usedA
- Pm Claude Skills1310 professional Agent Skills + workflow recipes — searchable & fetchable over MCP.not reviewedEstablishedA
Agoragentic Agent OS MCPTriptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.not reviewedEstablishedB- CHAP CoordinatorAuditable records of human decisions over AI agent work. Approvals, edits, overrides, escalations.not reviewedEstablishedA