Ordiscan MCP V1 MCP Server

MCP Framework HTTP Server

Local serverstdioTypeScript

What is the Ordiscan MCP V1 MCP server?

Ordiscan mcp v1 mcp server connects Ordiscan MCP V1 to AI assistants that speak the Model Context Protocol. MCP Framework HTTP Server.

What Ordiscan MCP V1 does

An MCP Framework HTTP server implementation with Ordiscan API integration.

Key capabilities

  • HTTP Stream transport on port 1337
  • Stream response mode for real-time communication
  • Comprehensive Ordiscan API integration (29 tools)
  • TypeScript implementation with Zod schema validation
  • Detailed error handling and response formatting
  • Direct API connection (no proxy required)
  • Bearer token authentication
  • Rate limiting handled by Ordiscan API

Tools it exposes

Once connected, the assistant can call these 2 tools directly:

  • BRC — 20 Balance Tool**: Get BRC-20 token balances for an address
  • Authentication — Every tool requires authentication using a Bearer token: - API key must be provided either: 1. As a parameter in each tool call (apiKey parameter) 2. Through

Installing the ordiscan mcp v1 mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply one environment variable: ORDISCAN_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Ordiscan MCP V1 sits in that group, and the shape of its toolset — BRC, Authentication — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

  • This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
  • It will not start until its required credentials are present, so set those before wondering why the tools never appear.
  • Maintained by Calel33, written in TypeScript.
  • MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the ordiscan mcp v1 mcp server actually does with your data.
  • Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.

Available tools

ToolWhat it does
BRC20 Balance Tool**: Get BRC-20 token balances for an address
AuthenticationEvery tool requires authentication using a Bearer token: - API key must be provided either: 1. As a parameter in each tool call (apiKey parameter) 2. Through the ORDISCAN_API_KEY environment variable - Authentication use

How to install the Ordiscan MCP V1 MCP server

{
  "mcpServers": {
    "ordiscanmcpv1": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://your-deployed-server.com/mcp"  
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ORDISCAN_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Ordiscan MCP V1 to BRC.
  • Use Ordiscan MCP V1 to Authentication.

Frequently asked questions

It connects Ordiscan MCP V1 to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (BRC, Authentication) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Ordiscan MCP V1 directly.