dns-of-money
Server Details
Resolve, discover & pay pay: aliases for AI agents; returns a signed OFAC-screen attestation.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- dnsofmoney/dns-of-money
- GitHub Stars
- 2
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
Each tool serves a unique, clearly defined purpose: availability check, resolution, agent discovery, registration info, payment requirements, and payment status. No two tools overlap in function, and descriptions clarify their distinct roles.
All tool names follow a consistent verb_noun pattern with underscores, using straightforward verbs like check, discover, get, and resolve. The get_ prefix is used uniformly for three tools, and all names are readable and predictable.
With 6 tools, the server is well-scoped for the DNS-of-money domain. Each tool covers a distinct aspect of the alias lifecycle—availability, resolution, discovery, payment requirements, and status—without unnecessary bloat or gaps.
The tool set covers the core workflows from checking alias availability to resolving payment endpoints, obtaining payment requirements, and verifying payment settlement. Registration info is provided, and the read-only nature is intentional, making the surface feel complete for its purpose.
Available Tools
6 toolscheck_alias_availableAInspect
Check whether a pay: alias can still be claimed. Returns exactly one of three states: 'available' (free to register), 'taken' (already registered), or 'reserved' (protected namespace). When available, also returns the number of founding spots remaining. Public — no API key required. Read-only: this never reserves or registers the name. Example: check_alias_available('pay:acme.user').
Inputs: alias_uri (required).
discover_agentAInspect
Get the AP2/A2A agent-commerce block for a pay: address — the DNS of Money equivalent of an A2A agent-card lookup. Use this during agent discovery before initiating a mandate flow. Returns agent capabilities only; NO payment credentials. Example: discover_agent('pay:acme.user').
Inputs: alias_uri (required).
get_agent_registration_infoAInspect
Learn how to self-register a FREE pay:agent. alias for your agent. Returns the registration endpoint, the AgentAuthorityCredential verifiable-presentation requirements (intent binding + domain), the rate limit, and the Merkle anchor-proof endpoint. Read-only — registration itself is the credential-gated POST this tool points at. Example: get_agent_registration_info().
Inputs: no named parameters.
get_payment_requirementsAInspect
Get x402 PaymentRequirements for paying a pay: alias. Returns the 402 accepts block (scheme, network, payTo, asset, amount, invoiceId) an x402 agent needs to construct and submit the payment. currency='XRP' settles on the XRP Ledger (amount in drops); currency='USDC' settles USDC on Algorand via the GoPlausible facilitator (amount in atomic micro-USDC, feePayer in extra). The deterministic resolver chooses the rail; this tool never moves money. Example: get_payment_requirements('pay:acme.user', amount='1.5').
Inputs: alias_uri (required), amount, currency.
get_payment_statusAInspect
Check whether a payment you already attempted was recorded, BEFORE you retry and risk spending twice. Pass the request_key you sent as the Idempotency-Key header on the paid request. Returns state 'settled' (we hold a receipt — do NOT pay again) or 'not_found' (we have no record — retrying is safe). Use this when a paid call timed out or its response was lost: on rails where the facilitator broadcasts, you never learn the transaction hash unless our response reaches you, so this key is the only thing that can answer. The key is a bearer secret — whoever presents it gets the receipt.
Inputs: request_key (required).
resolve_aliasAInspect
Resolve a human-readable financial alias (pay: address) to payment endpoints and routing metadata. Call this before initiating any payment to a pay: address. Returns the preferred rail, fallback endpoints, an ISO 20022 hint, and a compliance signal. Anonymous calls return status only; a free API key (no credit card) unlocks the endpoint set — which rails and currencies the alias accepts — via POST /api/v1/access-requests. You do NOT need a key to pay: get_payment_requirements returns a payable address to any caller. Example: resolve_alias('pay:acme.user').
Inputs: alias_uri (required), amount, currency, preferred_rail.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Resolve @handles to post-quantum-signed agent identities and transact with the brands behind them.
Resolve social handles to wallets, score onchain reputation, pay in any ERC-20, SPL or native.
Resolve, verify and discover .agt agent names: owner, records, signed manifest, endpoints.
Signed attestations for agents, $0.01/call via x402: URL witness, AI permission, tx finality, JWKS.
Related MCP Servers
AlicenseBqualityCmaintenanceEnables AI agents to resolve social handles to wallet addresses, check reputation scores, and send tokens directly from any MCP-compatible client.14369 npm9MIT- AlicenseAqualityBmaintenanceSpending firewall for AI agents on NEAR. Your agent pays through a vault contract with no master key: every payment is paid, held for you, or blocked on-chain, even if the agent is tricked. 7 tools: pay, check an address for scams, balance, rules, payment status, history, and Sentinel's paid safety check.7MIT
- AlicenseNot gradedqualityDmaintenanceProvides a three-layer payment firewall for AI agents, enabling identity verification, risk screening, and execution authorization with on-chain policy enforcement for secure and auditable transactions.3MIT
- AlicenseAqualityBmaintenancealalanet-agent is the open local client of alalanet.com, the free service an AI agent asks before it installs, connects or pays. A stdio MCP server whose key stays on your machine: it signs agent passports, receipts, skill and package releases, mail and memory locally (16 tools) and checks files and agents against alalanet's public transparency log. Hosted checks: https://alalanet.com/mcp.216Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.