io.github.Christebob/meta-stamp-pockets
REMOTE · METASTAMPV3-PRODUCTION.UP.RAILWAY.APP · SCANNED OCT 5
Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.Christebob/meta-stamp-pockets MCP server?
io.github.Christebob/meta-stamp-pockets is a hosted endpoint at https://metastampv3-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · metastampv3-production.up.railway.app
claude mcp add --transport http christebob-meta-stamp-pockets 'https://metastampv3-production.up.railway.app/mcp'
{
"mcpServers": {
"christebob-meta-stamp-pockets": {
"url": "https://metastampv3-production.up.railway.app/mcp"
}
}
} {
"servers": {
"christebob-meta-stamp-pockets": {
"type": "http",
"url": "https://metastampv3-production.up.railway.app/mcp"
}
}
} [mcp_servers.christebob-meta-stamp-pockets] url = "https://metastampv3-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"christebob-meta-stamp-pockets": {
"type": "remote",
"url": "https://metastampv3-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add christebob-meta-stamp-pockets --url 'https://metastampv3-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
christebob-meta-stamp-pockets:
url: "https://metastampv3-production.up.railway.app/mcp" {
"McpServers": {
"christebob-meta-stamp-pockets": {
"Transport": "http",
"Url": "https://metastampv3-production.up.railway.app/mcp"
}
}
} assistant mcp add christebob-meta-stamp-pockets -t streamable-http -u 'https://metastampv3-production.up.railway.app/mcp'
{
"mcpServers": {
"christebob-meta-stamp-pockets": {
"type": "http",
"url": "https://metastampv3-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 1 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Oct 2026 · Probed https://metastampv3-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of metastampv3-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://metastampv3-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://metastampv3-production.up.railway.app/mcp | HTTPS enforced | 301 | https://metastampv3-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
list_pockets ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| creator_id | string | – | Optional filter to show only pockets from a specific creator. Use the creator's unique identifier. |
| limit | integer | – | Maximum number of results to return per page. Defaults to 50, maximum 200 for catalog browsing. |
No output schema declared.
No examples provided.
pull_content ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| pocket_id | string | yes | The 24-character hex identifier of the content pocket to pull from. Obtain this from search_pockets or list_pockets results. |
| query | string | – | Optional natural language focus query used to narrow or contextualize the returned content within the selected pocket. |
No output schema declared.
No examples provided.
search_pockets ~286
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. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | Optional filter to show only pockets in a specific content category or source type, such as 'youtube', 'webpage', 'video', 'text', 'image', or 'audio'. |
| creator_email | string | – | Optional filter to show only pockets created by the creator with this email address. Case-insensitive exact match on the email. |
| limit | integer | – | Maximum number of results to return per page. Defaults to 10, maximum 50 for search results. |
| query | string | – | Natural language search terms or category keywords to find matching content pockets. Optional when creator_email is provided. |
No output schema declared.
No examples provided.
What is the io.github.Christebob/meta-stamp-pockets MCP server?
io.github.Christebob/meta-stamp-pockets is an MCP server listed in the public MCP registry as io.github.Christebob/meta-stamp-pockets. Attribution and settlement infrastructure for AI agent content access over HTTP 402 and MCP. This page covers its hosted endpoint (https://metastampv3-production.up.railway.app/mcp).
Is the io.github.Christebob/meta-stamp-pockets MCP server safe to use?
io.github.Christebob/meta-stamp-pockets scores 33 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Christebob/meta-stamp-pockets MCP server expose?
io.github.Christebob/meta-stamp-pockets exposes 3 tools: pull_content, search_pockets, list_pockets. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.
Does the io.github.Christebob/meta-stamp-pockets MCP server require authentication?
No. We connected to io.github.Christebob/meta-stamp-pockets without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Christebob/meta-stamp-pockets MCP server still maintained?
io.github.Christebob/meta-stamp-pockets is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.