Ordiscan MCP Server

Created By
ordiscana year ago
An MCP server for getting information about Ordinals and Runes on Bitcoin
Overview

What is Ordiscan MCP Server?

Ordiscan MCP Server is a model context protocol server designed to retrieve information about Ordinals and Runes on the Bitcoin blockchain.

How to use Ordiscan MCP Server?

To use the Ordiscan MCP Server, you need to configure it with your API key and set it up in the Claude Desktop application. Follow the installation instructions provided in the documentation.

Key features of Ordiscan MCP Server?

  • Retrieves real-time information about Bitcoin Ordinals and Runes.
  • Easy integration with Claude Desktop.
  • Requires an API key for access.

Use cases of Ordiscan MCP Server?

  1. Accessing detailed information about Bitcoin Ordinals.
  2. Analyzing Runes on the Bitcoin blockchain.
  3. Integrating with other applications for enhanced Bitcoin data retrieval.

FAQ from Ordiscan MCP Server?

  • How do I obtain an API key?

You can obtain a free API key from the Ordiscan website.

  • Is there a cost associated with using the Ordiscan MCP Server?

No, the API key is free to use.

  • What programming language is the server built with?

The Ordiscan MCP Server is built using TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ordiscan
Star
1
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago