# io.github.sparkmastergrape/dns-of-money (remote · api.dnsofmoney.com) Resolve, discover & pay pay: aliases for AI agents; returns a signed OFAC-screen attestation. - Trust score: 68/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `api.dnsofmoney.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/sparkmastergrape-dns-of-money/api.md), [page](https://verifymcp.io/servers/sparkmastergrape-dns-of-money/api) ## Channel facts - Endpoint: `https://api.dnsofmoney.com/mcp/rpc` - Transports: `streamable-http` - Auth: `none` - Version: `1.0.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 66/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC is configured correctly; the domain's records validate against the full chain to the root. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 65/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 964 tokens (~160/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http sparkmastergrape-dns-of-money https://api.dnsofmoney.com/mcp/rpc ``` ### Codex ```toml [mcp_servers.sparkmastergrape-dns-of-money] url = "https://api.dnsofmoney.com/mcp/rpc" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "sparkmastergrape-dns-of-money": { "type": "remote", "url": "https://api.dnsofmoney.com/mcp/rpc", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add sparkmastergrape-dns-of-money --url https://api.dnsofmoney.com/mcp/rpc --transport streamable-http ``` ### Hermes ```yaml mcp_servers: sparkmastergrape-dns-of-money: url: "https://api.dnsofmoney.com/mcp/rpc" ``` ### Other ```json { "mcpServers": { "sparkmastergrape-dns-of-money": { "type": "http", "url": "https://api.dnsofmoney.com/mcp/rpc" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-03 (score 68, 0) - [functional regression] Schema quality: 778 → 964 - [functional] New tool “get_payment_status” ### 2026-08-02 (score 68, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 67, +2) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 65, +12) - [functional improvement] Schema quality: unverified → good ### 2026-07-28 (score 53, −11) - [functional regression] Schema quality: 608 → 778 - [functional regression] Schema quality: good → unverified ### 2026-07-27 (score 64, +2) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 62) First indexed and scored. ## MCP tools (6) ### `resolve_alias` (~216 tokens) 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'). Input parameters: - `alias_uri` (string, required): The pay: address to resolve. E.g. 'pay:acme.user'. - `amount` (string): Optional payment amount (decimal string) — refines rail scoring. - `currency` (string): Optional ISO 4217 currency code. Defaults to USD. - `preferred_rail` (string): Optional rail hint (e.g. 'xrpl', 'fednow'). Advisory only. ### `discover_agent` (~93 tokens) 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'). Input parameters: - `alias_uri` (string, required): The pay: address to discover. E.g. 'pay:acme.user'. ### `check_alias_available` (~127 tokens) 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'). Input parameters: - `alias_uri` (string, required): Candidate pay: address, e.g. 'pay:acme.user'. A bare name without the 'pay:' prefix is accepted too. ### `get_payment_requirements` (~239 tokens) 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'). Input parameters: - `alias_uri` (string, required): The pay: address to pay. E.g. 'pay:acme.user'. - `amount` (string): Amount to pay — decimal string in the asset's display unit (XRP). Omit it to be quoted the alias's declared price; required for an alias that declares no price. - `currency` (string): Asset to pay in: 'XRP' (XRPL) or 'USDC' (Algorand). Defaults to XRP. ### `get_payment_status` (~186 tokens) 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. Input parameters: - `request_key` (string, required): The exact Idempotency-Key you sent with the paid request. 32-128 characters of [A-Za-z0-9_-], generated from a CSPRNG with at least 128 bits of entropy. ### `get_agent_registration_info` (~83 tokens) Learn how to self-register a FREE pay:agent.