Vältgeist Domains
REMOTE · API.VALTGEIST.TRADE · SCANNED OCT 5
Daily GoDaddy auction data: is a domain at auction, its appraisal, price and bid count.
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 → Why this is hard to score →
Endpoint Security57
- 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 5 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 456 tokens (~91/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Vältgeist Domains MCP server?
Vältgeist Domains is a hosted endpoint at https://api.valtgeist.trade/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.valtgeist.trade
claude mcp add --transport http ilumci-valtgeist-domains 'https://api.valtgeist.trade/mcp'
{
"mcpServers": {
"ilumci-valtgeist-domains": {
"url": "https://api.valtgeist.trade/mcp"
}
}
} {
"servers": {
"ilumci-valtgeist-domains": {
"type": "http",
"url": "https://api.valtgeist.trade/mcp"
}
}
} [mcp_servers.ilumci-valtgeist-domains] url = "https://api.valtgeist.trade/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ilumci-valtgeist-domains": {
"type": "remote",
"url": "https://api.valtgeist.trade/mcp",
"enabled": true
}
}
} openclaw mcp add ilumci-valtgeist-domains --url 'https://api.valtgeist.trade/mcp' --transport streamable-http
mcp_servers:
ilumci-valtgeist-domains:
url: "https://api.valtgeist.trade/mcp" {
"McpServers": {
"ilumci-valtgeist-domains": {
"Transport": "http",
"Url": "https://api.valtgeist.trade/mcp"
}
}
} assistant mcp add ilumci-valtgeist-domains -t streamable-http -u 'https://api.valtgeist.trade/mcp'
{
"mcpServers": {
"ilumci-valtgeist-domains": {
"type": "http",
"url": "https://api.valtgeist.trade/mcp"
}
}
} 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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Oct 2026 · Probed https://api.valtgeist.trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=valtgeist.trade | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 940bfa4f187af9c60eb8ac95f37cd6bc |
| SANs: valtgeist.trade, *.valtgeist.trade | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.valtgeist.trade. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| trade. | present | 64969 | 8 | Verified |
| valtgeist.trade. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.valtgeist.trade/mcp | Verified | 200 | |
| http (plaintext) | http://api.valtgeist.trade/mcp | HTTPS enforced | 301 | https://api.valtgeist.trade/mcp |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bid_rates ~62
How the share of listings carrying a bid varies by GoDaddy appraisal band and by how close the auction is to closing. Useful for judging whether an appraisal means anything at a given value, and for telling a domain owner whether their listing is in a band where anything trades.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_auctions ~117
List live GoDaddy auctions that already carry at least one bid. Sort by soonest closing, most bids, biggest appraisal-to-price gap, or lowest price. Filter by extension and maximum price. Auctions that have already closed are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 1 to 200, default 25. |
| max_price | number | – | Only auctions at or below this price in USD. |
| sort | string | – | Default closing. |
| tld | string | – | Restrict to an extension, e.g. com |
No output schema declared.
No examples provided.
lookup_domain ~100
Check whether a specific domain is currently listed in a GoDaddy expiry or Buy Now auction, and if so its appraisal, current price, bid count and close time. Use this before suggesting a domain name to someone, so the suggestion is one they can actually buy. Covers GoDaddy auctions ONLY: a "not listed" result says nothing about whether the domain is registered or available elsewhere.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Full domain, e.g. example.com |
No output schema declared.
No examples provided.
market_stats ~86
Headline figures for the GoDaddy auction market today: how many domains are listed, how many carry a bid, median appraisal, and the measured CEILING on how often a listed domain sells. The sell-through figure is an upper bound and not a rate: a seller withdrawing a listing looks identical to a sale in this feed. Do not quote it as the probability a domain will sell.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tld_stats ~37
Bid rate and average appraisal for each domain extension with at least 400 listings. Shows which extensions actually attract bidders and which are dead inventory.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Vältgeist Domains MCP server?
Vältgeist Domains is an MCP server listed in the public MCP registry as io.github.IlumCI/valtgeist-domains. Daily GoDaddy auction data: is a domain at auction, its appraisal, price and bid count. This page covers its hosted endpoint (https://api.valtgeist.trade/mcp).
Is the Vältgeist Domains MCP server safe to use?
Vältgeist Domains scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vältgeist Domains MCP server expose?
Vältgeist Domains exposes 5 tools: lookup_domain, list_auctions, market_stats, bid_rates, tld_stats. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.
Does the Vältgeist Domains MCP server require authentication?
No. We connected to Vältgeist Domains without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vältgeist Domains MCP server still maintained?
Vältgeist Domains is still listed as active in the MCP registry. We last reached this channel on 5 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.