English Français العربية

io.github.Christebob/meta-stamp-pockets

Registre officiel Cloud et DevOps

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

Code source Site web Documentation

Que pouvez-vous faire avec io.github.Christebob/meta-stamp-pockets ?

  • 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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http meta-stamp-pockets 'https://metastampv3-production.up.railway.app/mcp'
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "meta-stamp-pockets": {
            "type": "http",
            "url": "https://metastampv3-production.up.railway.app/mcp"
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Meta-Stamp Pockets
  2. What It Does
  3. How Content Gets Protected
  4. MCP Server
  5. Live Demo
  6. API Docs
  7. For Creators
  8. For Enterprise

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

Questions fréquentes

Qu'est-ce que io.github.Christebob/meta-stamp-pockets ?

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

Comment installer io.github.Christebob/meta-stamp-pockets ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http meta-stamp-pockets 'https://metastampv3-production.up.railway.app/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.Christebob/meta-stamp-pockets ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.Christebob/meta-stamp-pockets est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.Christebob/meta-stamp-pockets ?

Il est publié par Christebob. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.