home / mcp / ordiscanmcp v1 mcp server
ordiscan mcp
Configuration
View docs{
"mcpServers": {
"calel33-ordiscan-mcp-v1": {
"url": "http://localhost:1337/mcp",
"headers": {
"ORDISCAN_API_KEY": "YOUR_API_KEY"
}
}
}
}You run the OrdiscanMCP v1 server to access Ordiscan tools via an MCP-style interface. It provides an HTTP stream transport on port 1337 with real-time stream responses, direct API access to Ordiscan, and Bearer token authentication. This setup lets your MCP client query a comprehensive set of tools for inscriptions, runes, UTXOs, collections, and more, all with robust parameter handling and clear response formatting.
Start the MCP server and configure your client to connect over HTTP or via a local stdio integration. You can connect directly to the MCP endpoint at the provided HTTP URL for real-time streaming responses, or you can launch a local stdio-based MCP subprocess as described in the setup. Use your API key with every request to authenticate using the Bearer token scheme.
Prerequisites: make sure you have Node.js installed on your system. You will also need npm to manage dependencies.
Install dependencies and build the project.
npm install
```
```
npm run buildConfigure your MCP client with the following example. This enables the client to connect to the Ordiscan MCP v1 server via the remote endpoint.
{
"mcpServers": {
"ordiscanmcpv1": {
"command": "npx",
"args": [
"mcp-remote",
"https://your-deployed-server.com/mcp"
]
}
}
}Start the server to begin serving MCP requests.
npm startFor development with hot-reload you can run the development command.
npm run devAuthentication uses a Bearer token. You can provide the API key either as a parameter in each tool call (apiKey) or through the environment variable ORD ISC AN_API_KEY. All requests must include the header Authorization: Bearer <your-api-key>. Ensure your API key is kept secure and rotated periodically.
Environment variables that are used by the server can be supplied as part of your MCP config for the stdio setup. The key variable to store your API key is ORDISCAN_API_KEY.
Treat your API keys as secrets. Do not hardcode them in your codebase. Use environment variables and rotate keys regularly. Implement proper error handling to avoid leaking sensitive information in error messages.
The MCP server exposes an HTTP stream transport on port 1337. You can also connect via a local stdio-based subprocess if you prefer running the solver locally with a command like npx mcp-remote ....
General-purpose tool for rune information and status
Get all UTXOs owned by a Bitcoin address
Get inscription information for an address (basic)
Get detailed inscription information for an address (detailed)
Get rune balances for an address
Get BRC-20 token balances for an address
Get rare sats owned by an address
Track inscription transfers for an address
Track rune transfers for an address
Track BRC-20 token transfers for an address
Get detailed information about a transaction
Get inscriptions in a transaction
Track inscription transfers in a transaction
Track rune transfers in a transaction
Get detailed information about an inscription (specific)
Get traits for an inscription
Get a paginated list of all inscriptions
Track transfers of an inscription
Get a paginated list of collections
Get detailed information about a collection
Get inscriptions in a collection
Get a list of all runes
Get market information for a rune
Check rune name availability
Get a list of all BRC-20 tokens
Get detailed information about a BRC-20 token
Get information about a specific sat
Get rare sats in a UTXO
Get sat ranges in a UTXO