Data Collection
opreturn.xyz
An MCP server for The Permanent Record that searches and retrieves monitored Bitcoin OP_RETURN messages, lists curated Bitcoin address collections, fetches message details, and navigates pages.
ENDPOINT 1
https://opreturn.xyz
MCP server metadata
- Name
- WebMCP
Known tools 4
search-transmissionsSearch and retrieve live monitored Bitcoin OP_RETURN messages. Returns messages with txid, content, sender, address, and category.
Inferred read-onlylist-collectionsList all curated collections of monitored Bitcoin addresses (e.g. Liquid Network whitehat, Coldcard exploit, Genesis memorials).
Inferred read-onlyget-message-detailFetch a specific immutable Bitcoin OP_RETURN message by its 64-character transaction ID (txid).
Potential side effectsnavigate-pageNavigate to a specific page on The Permanent Record ('feed', 'collections', 'guide', 'landing').
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.webmcp]
url = "https://opreturn.xyz"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://opreturn.xyz"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://opreturn.xyz
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": {
"webmcp": {
"url": "https://opreturn.xyz"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://opreturn.xyz"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://opreturn.xyz"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.