io.github.sparkmastergrape/dns-of-money
REMOTE · API.DNSOFMONEY.COM · SCANNED AUG 3
Resolve, discover & pay pay: aliases for AI agents; returns a signed OFAC-screen attestation.
Available components
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. How we score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.dnsofmoney.com
claude mcp add --transport http sparkmastergrape-dns-of-money https://api.dnsofmoney.com/mcp/rpc
[mcp_servers.sparkmastergrape-dns-of-money] url = "https://api.dnsofmoney.com/mcp/rpc"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sparkmastergrape-dns-of-money": {
"type": "remote",
"url": "https://api.dnsofmoney.com/mcp/rpc",
"enabled": true
}
}
} openclaw mcp add sparkmastergrape-dns-of-money --url https://api.dnsofmoney.com/mcp/rpc --transport streamable-http
mcp_servers:
sparkmastergrape-dns-of-money:
url: "https://api.dnsofmoney.com/mcp/rpc" {
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Aug 26 0
- Schema quality: 778 → 964 ▼ functional
- New tool “get_payment_status” functional
- 2 Aug 26 +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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +12
- Schema quality: unverified → good ▲ functional
- 28 Jul 26 −11
- Schema quality: 608 → 778 ▼ functional
- Schema quality: good → unverified ▼ functional
- 27 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.dnsofmoney.com/mcp/rpc
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.dnsofmoney.com | CN=YE1,O=Let's Encrypt,C=US | 19 Jun 2026 | 17 Sept 2026 | ECDSA 256 | ECDSA-SHA384 | 554c51932de44557ffc823bc008e0c1f29b |
| SANs: api.dnsofmoney.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC secure
Validation of api.dnsofmoney.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dnsofmoney.com. | present | 2371 | 13 | Verified |
| api.dnsofmoney.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.dnsofmoney.com/mcp/rpc | Verified | 200 | |
| http (plaintext) | http://api.dnsofmoney.com/mcp/rpc | HTTPS enforced | 301 | https://api.dnsofmoney.com/mcp/rpc |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_alias_available ~127
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').
| Name | Type | Req | Description |
|---|---|---|---|
| alias_uri | string | yes | Candidate pay: address, e.g. 'pay:acme.user'. A bare name without the 'pay:' prefix is accepted too. |
No output schema declared.
No examples provided.
discover_agent ~93
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').
| Name | Type | Req | Description |
|---|---|---|---|
| alias_uri | string | yes | The pay: address to discover. E.g. 'pay:acme.user'. |
No output schema declared.
No examples provided.
get_agent_registration_info ~83
Learn how to self-register a FREE pay:agent.<label> 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().
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_payment_requirements ~239
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').
| Name | Type | Req | Description |
|---|---|---|---|
| alias_uri | string | yes | 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. |
No output schema declared.
No examples provided.
get_payment_status ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_key | string | yes | 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. |
No output schema declared.
No examples provided.
resolve_alias ~216
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').
| Name | Type | Req | Description |
|---|---|---|---|
| alias_uri | string | yes | 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. |
No output schema declared.
No examples provided.