Skip to main content
Glama
Sign In
deenesjakoruzh
Meta-Stamp Pockets

Meta-Stamp Pockets

by Christebob
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

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

Related MCP server: x402 Stellar MCP Server

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

Available Tools

3 tools
list_pocketsAInspect

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. 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.

Inputs: limit, creator_id.

pull_contentAInspect

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, 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.

Inputs: pocket_id (required), query.

search_pocketsAInspect

Search the Meta-Stamp Pockets catalog by keyword, creator name, 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, creator names, or category keywords. Returns matching pockets with their IDs, titles, descriptions, creators, content types, and pricing tiers. Use the limit parameter to control page size.

Inputs: query (required), limit, content_type.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.8/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_pockets and list_pockets for discovery (metadata only), pull_content for actual content retrieval. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern: pull_content, search_pockets, list_pockets. Excellent naming convention.

    Tool Count5/5

    Three tools is ideal for a content pocket catalog: two for discovery (search and list) and one for retrieval. Not too few, not too many.

    Completeness4/5

    The tool set covers the essential operations for a read-only content catalog (discovery and retrieval). Missing create/update/delete, but these may be intentionally omitted for a consumption-focused service.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers