meta-stamp-pockets MCP server
io.github.Christebob/meta-stamp-pocketsChristebobstreamable-httpv1.0.0Scanned
Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP.
3 tools: 1 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the meta-stamp-pockets MCP server can do
The meta-stamp-pockets MCP server is published by the GitHub account Christebob. It has 3 tools. It can create or change data (1 tool: pull_content), but cannot delete data. 2 tools only read.
1 tool reads private data (search_pockets); 1 tool brings in text other people can write (search_pockets).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 15, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
pull_contentPull licensed creator content from a specific pocket by ID.1 finding
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Findings
- Info
The description is 2,129 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...d as its UTF-8 bytes, an object as UTF-8 JSON with sorted keys and no whitespace."
Description, as the server wrote it 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.
Only reads 2Show 2 read-only tools
list_pocketsList all available content pockets in the Meta-Stamp Pockets catalog, optionally filtered by creator.No findings
Why it is in this group
- The name "list_pockets" says "list": a word for reading.
Description, as the server wrote it 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_pocketsSearch the Meta-Stamp Pockets catalog by keyword, creator email, or content category.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_pockets" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "search" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "search" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2024-11-05
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://metastampv3-production.up.railway.app/mcp: tools/list returned 3 tools to an anonymous client, including pull_content (write)
Findings
Matches of fixed checks, with the text they matched.
- Infopull_content
The description is 2,129 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...d as its UTF-8 bytes, an object as UTF-8 JSON with sorted keys and no whitespace."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:pull_contentChanges thingsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http meta-stamp-pockets https://metastampv3-production.up.railway.app/mcpclaude mcp add --transport http meta-stamp-pockets https://metastampv3-production.up.railway.app/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__meta-stamp-pockets__search_pockets",
"mcp__meta-stamp-pockets__list_pockets"
],
"ask": [
"mcp__meta-stamp-pockets__pull_content"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as meta-stamp-pockets. Review it before you use it.
Capability tags behind 1 rule
- mcp__meta-stamp-pockets__search_pockets private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Christebob/meta-stamp-pockets/verify?hash=e2b948283c1e968da10fc8c88ccaecf3a6286954595f8bbe9e9b04cb10fc8069" | jq -e '.changed == false'Pinned hash e2b948283c1e, from Nov 15, 2026, 18:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Christebob/meta-stamp-pockets/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Christebob/meta-stamp-pockets)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.
meta-stamp-pockets MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the meta-stamp-pockets MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the meta-stamp-pockets MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the meta-stamp-pockets MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the meta-stamp-pockets MCP server have?
- 3 tools: 1 write, 2 read. pull_content, search_pockets and list_pockets.
Does the meta-stamp-pockets MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the meta-stamp-pockets MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the meta-stamp-pockets MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 2, 2026. Every change is on this page and in its Atom feed.