Meta Stamp Pockets

io.github.ChristebobPublished by GitHub account Christebobv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that lets an assistant search a catalog of licensed creator content, list pockets, and pull provenance-tracked content for a per-pull fee.

What you can do
Search the catalog of licensed creator content by keyword, creator email, or category to find pockets before pulling anything. List all available pockets, optionally filtered by a creator, to browse the full catalog. Pull licensed, provenance-tracked content from a specific pocket by ID for generation, RAG, or inference use. Each access attempt is recorded in an immutable event ledger, with paid pulls settling and refusals leaving a record.
When to use it
Use it when an assistant needs licensed, provenance-tracked creator content for generation, retrieval, or inference, and you want per-pull payment and attribution handled at the point of access. It is not meant for browsing or general web retrieval.
Requirements
A remote streamable HTTP endpoint; no local package. A Bearer token is required, obtained by registering on the provider's site. Network access to the provider's host. Training use requires a separate training license under the agreement terms.
Before you install
Pulls are paid: per-pull pricing is set by the creator, with a stated $1.00 default, and 85% goes to the creator, so using the tools can spend money. A Bearer token credential must be supplied. Every access attempt, including refusals, is written to an immutable ledger. Content is served by a third party, and training use needs a separate license.

Installation

In SourceWeft

  1. Open Meta Stamp Pockets in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Christebob%2Fmeta-stamp-pockets/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "meta-stamp-pockets": {
      "type": "http",
      "url": "https://metastampv3-production.up.railway.app/mcp"
    }
  }
}

README

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/mcp

Available 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 [email protected].

For Enterprise

If you represent an AI platform interested in licensing access to the Meta-Stamp creator network, contact [email protected].


Meta-Stamp, LLC · Simi Valley, CA · Patent pending

Source: README.md at commit 536c002

Tools

3

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) 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 'not_for_sale' 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 wh

Parametersquerypocket_idrequired

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.

Parametersisrclimitquerycontent_typecreator_email

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.

Parameterslimitcreator_id

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts