A
licenseB
qualityD
maintenanceEnable AI assistants to interact directly with Bitcoin Ordinals inscriptions. Seamlessly integrates with Goose and Claude Desktop to retrieve and display inscription content from transactions.
1
4
MIT
@ordinal402/ordinal-mcp
by ordi402
Related Servers
Alternatives to @ordinal402/ordinal-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAccount-less access to 45 Gemini models & autonomous agents, 71 edge microservices across 6 modular domain packages via L402, x402, MPP.1212MIT
- AlicenseBqualityFmaintenanceConnects a Bitcoin Lightning wallet to your LLM using Nostr Wallet Connect, enabling payment functionalities within language models like Claude.68 npm15MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables gasless blockchain transactions directly from Claude conversations, allowing users to execute transfers, swaps, and other operations without holding native tokens.39 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables users to connect Claude or ChatGPT to a custodial NFT collection and trade by chatting, including minting, buying, selling, listing, checking balances, and withdrawing test tokens.MIT
@arispay/payagent-mcpofficial
AlicenseAqualityAmaintenanceEnables AI agents to call paid APIs and settle HTTP 402 payment challenges with USDC on Base, without private keys ever being involved.7154 npmMIT
TDQS
A4.1/5.0
Scored across 6 tools
Disambiguation5/5
Each tool targets a distinct action: browsing, inspecting, trying, calling, checking payment status, and checking wallet identity. The try_service versus call_service distinction is clearly drawn by payment and settlement semantics.
Naming Consistency4/5
Five of six tools follow a clear verb_noun snake_case pattern. The sole exception is wallet_address, which is a noun phrase rather than a get_* verb, but it remains readable and predictable.
Tool Count5/5
At six tools, the set is tightly scoped to the service marketplace workflow: discover, inspect, try, pay, verify, and wallet identity. There is no bloat or redundancy.
Completeness4/5
The core lifecycle from discovery through paid execution to settlement verification is covered. Minor gaps exist: there is no transaction history tool and no way to configure the wallet within the MCP surface, but agents can work around both.
Maintenance
ActivitySlowing
ResponsivenessNo issues