SatsDNS
v0.2.10DNS hosting, secondary DNS and dynamic DNS paid per call in sats; optional Nostr account tools.
Endpoint health
online- Last checked
- 11/20/2026, 7:16:40 AM
- Latency
- 303 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:com.satsdns%2Fsatsdns
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"com.satsdns/satsdns": {
"url": "https://api.satsdns.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
21 shown · authentication unknown
Your SatsDNS account: objects, invoices, state (free, API key or signature)
account_objects
Free, read-only: the account's state and limits, or the zones, hostnames or invoices it owns. With api_key, only the objects the key's scope covers and only their invoices (the account view of limits and counts is the same for every key). Called without nip98 it returns signature_required: the exact URL, method and body to sign, the body's sha256 and an unsigned kind 27235 event template (with proof of work for accounts without a paid order). Sign that, then call again with the same arguments plus nip98. Each signed event works once, within 60 s. Secrets that are ours to receive: object tokens, account API keys (jdk_), signed NIP-98 events; never a private key (nsec or 64 hex characters), wallet connection string or seed words. A raw hex key or seed words inside a sentence cannot be caught here.
Schema valid · SHA-256 c0fd075154d5…
View input schema
{ "type": "object", "properties": { "type": { "type": "string", "enum": [ "account", "zones", "hostnames", "invoices" ], "description": "account: state, tier, limits and whether proof of work is needed; zones, hostnames: what the account owns; invoices: the 50 newest." }, "api_key": { "type": "string", "description": "A scoped account API key (jdk_...) made in the dashboard. It passes through your model context and transcript: treat it like a password. Key model: a key reads (or, with write access, changes) only the objects in its scope, and sees only their invoices; every key reads the account view (limits and counts); a key never orders new objects and never receives a new object's shown-once token." }, "nip98": { "type": "string", "description": "The signed NIP-98 event (base64 of its JSON) for exactly the request the signature_required answer of the same call named. Sign it with your own Nostr signer (local key, NIP-46 bunker or a signer tool); never send the private key itself, in any form (nsec, hex or seed words)." } }, "required": [ "type" ], "additionalProperties": false }
Connections
streamable-http
https://api.satsdns.com/mcp