Content Tools
metastampv3-production.up.railway.app
Provides access to the Meta-Stamp Pockets catalog for searching and retrieving licensed creator content by ID, keyword, or category.
ENDPOINT 1
https://metastampv3-production.up.railway.app/mcp
MCP server metadata
- Name
- meta-stamp-pockets
- Version
- 1.0.0
Known tools 3
search_pocketsSearch the Meta-Stamp Pockets catalog by keyword, creator email, or content category.
Potential side effectslist_pocketsList all available content pockets in the Meta-Stamp Pockets catalog, optionally filtered by creator.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.meta-stamp-pockets]
url = "https://metastampv3-production.up.railway.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"meta-stamp-pockets": {
"type": "http",
"url": "https://metastampv3-production.up.railway.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: meta-stamp-pockets
Remote MCP URL: https://metastampv3-production.up.railway.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"meta-stamp-pockets": {
"url": "https://metastampv3-production.up.railway.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"meta-stamp-pockets": {
"type": "http",
"url": "https://metastampv3-production.up.railway.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "meta-stamp-pockets",
"transport": "streamable-http",
"url": "https://metastampv3-production.up.railway.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for railway.app was fetched 2026-08-25T20:04:34.605Z.
railway.app is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.