io.github.Christebob/meta-stamp-pockets
REMOTE · METASTAMPV3-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 3
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 →
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 call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 664 tokens (~221/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · metastampv3-production.up.railway.app
claude mcp add --transport http christebob-meta-stamp-pockets 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": {
"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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
- 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 57
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 3 Aug 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=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 |
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 |
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.
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.