Dantes Exchange
REMOTE · DANTES.AI · SCANNED SEP 28
Paid trader skills MCP. Coil scanner with dated 252d forward-return evidence. x402 USDC.
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 Security46
- 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability56
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4569 tokens (~761/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Dantes Exchange MCP server?
Dantes Exchange is a hosted endpoint at https://dantes.ai/exchange/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 · dantes.ai
claude mcp add --transport http dcrypt-007-dantes-exchange 'https://dantes.ai/exchange/mcp'
{
"mcpServers": {
"dcrypt-007-dantes-exchange": {
"url": "https://dantes.ai/exchange/mcp"
}
}
} {
"servers": {
"dcrypt-007-dantes-exchange": {
"type": "http",
"url": "https://dantes.ai/exchange/mcp"
}
}
} [mcp_servers.dcrypt-007-dantes-exchange] url = "https://dantes.ai/exchange/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dcrypt-007-dantes-exchange": {
"type": "remote",
"url": "https://dantes.ai/exchange/mcp",
"enabled": true
}
}
} openclaw mcp add dcrypt-007-dantes-exchange --url 'https://dantes.ai/exchange/mcp' --transport streamable-http
mcp_servers:
dcrypt-007-dantes-exchange:
url: "https://dantes.ai/exchange/mcp" {
"McpServers": {
"dcrypt-007-dantes-exchange": {
"Transport": "http",
"Url": "https://dantes.ai/exchange/mcp"
}
}
} assistant mcp add dcrypt-007-dantes-exchange -t streamable-http -u 'https://dantes.ai/exchange/mcp'
{
"mcpServers": {
"dcrypt-007-dantes-exchange": {
"type": "http",
"url": "https://dantes.ai/exchange/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
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 24 Sept 26 +11
- Judged manipulation: unverified → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: unverified → excellent ▲ functional
- 23 Sept 26 −10
- Judged manipulation: pass → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → unverified ▼ functional
- 21 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.
- 19 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.
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 28 Sept 2026 · Probed https://dantes.ai/exchange/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dantes.ai | CN=YE1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 640db12c05a6ec9c455f680b2acf45be7c8 |
| SANs: dantes.ai | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dantes.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| dantes.ai. | 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://dantes.ai/exchange/mcp | Verified | 200 | |
| http (plaintext) | http://dantes.ai/exchange/mcp | Served over HTTP | 200 |
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 →
get_capability Get capability manifest ~81
WHEN: Use when you already have a capability id and need schema, price, and when-to-use before paying. NOT for: Do not use to execute the scan. Returns: The full manifest — input and output schema, support envelope, limitations — plus the price and access class on THIS endpoint, and the routing block.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_capability_evidence Get capability evidence ~131
WHEN: Use when you need the dated forward-return pack for a listed skill (n, window, as-of). NOT for: Do not use as a live scan and do not treat evidence as today’s hits. Returns: Semantic evidence (does it do what it says) kept strictly separate from historical economic evidence (what was measured about the population it describes) — never combined into a score. Universe-relative and vs-benchmark figures appear only where they were actually measured; a capability with no economic measurement returns NOT_MEASURED rather than a borrowed figure.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Capability id |
No output schema declared.
No examples provided.
invoke_capability Invoke capability ~204
WHEN: Use when you have chosen a listed skill, the user wants names that match it now, and you are ready to pay. NOT for: Do not use for quotes, news, or a chart pattern nowhere on this endpoint (head-and-shoulders — say we don’t have that). Do not refuse a NAMED indicator before get_capability ta-primitives has been read, and do not rebuild a held recipe from memory: the composing rules in the routing guide apply to every call here. Returns: { ok, result } or { ok: false, error }. A priced capability answers an unpaid call with an x402 PaymentRequired naming the exact amount, asset, network and recipient; nothing executes and nothing is charged until a payment verifies. A scan that ran and returned zero names is a completed billable run, not an error.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Capability id |
| input | object | yes | Input conforming to the capability's input_schema |
No output schema declared.
No examples provided.
list_datasets List published datasets and enumerate their equity universes ~243
WHEN: Use when you need what universes / as-of books a skill can run on. NOT for: Do not use to fetch prices or news. Returns: The published datasets with their as-of dates and the universes they enumerate; with a `universe` argument, the member ticker list itself. Raw dataset files are never returned.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | Dataset name, when the endpoint publishes more than one. |
| eligible_only | boolean | – | SECULAR_TREND only — restrict to members that also pass the LIQUID_VOLATILE mechanical gates. |
| format | string | – | "full" (default) returns member records with metadata, paged. "symbols" returns the complete ticker list in one cheap response. |
| limit | number | – | Members per page for format "full" (default 250, max 1000). |
| offset | number | – | Page offset for format "full". |
| theme | string | – | SECULAR_TREND only — restrict to one secular theme id. |
| universe | string | – | Enumerate the members of one universe. Omit to list datasets and see which universes are available. |
No output schema declared.
No examples provided.
report_gap Report what Dantes is missing ~172
WHEN: Use when you concluded, after search_capabilities and get_capability, that Dantes cannot do part of what your user asked — name the missing data column, indicator, history or composition in buildable terms, and what Dantes CAN do of the ask. NOT for: Do not use for a capability that exists and refused your input shape (read its schema and retry), and do not tell your user the gap will be built or when — it is recorded for the operators, never promised. Returns: { ok, recorded } — the missing pieces as written to the operators’ gaps board, free, or { ok: false } with the reason.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities_tried | array | – | – |
| could_do | string | – | – |
| missing | array | yes | – |
| question | string | yes | – |
No output schema declared.
No examples provided.
search_capabilities Search capabilities ~107
WHEN: Use when the user named a setup in trader language and you need to know which Dantes skill matches. NOT for: Do not use to run a scan or to invent a skill we do not list. Returns: Matching capability ids, each with its price, what it takes to run it, and its own when / not_for / returns — plus `not_encoded`, the setups this endpoint does not have.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
What is the Dantes Exchange MCP server?
Dantes Exchange is an MCP server listed in the public MCP registry as io.github.dcrypt-007/dantes-exchange. Paid trader skills MCP. Coil scanner with dated 252d forward-return evidence. x402 USDC. This page covers its hosted endpoint (https://dantes.ai/exchange/mcp).
Is the Dantes Exchange MCP server safe to use?
Dantes Exchange scores 69 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 Dantes Exchange MCP server expose?
Dantes Exchange exposes 6 tools: search_capabilities, report_gap, get_capability, get_capability_evidence, list_datasets, invoke_capability. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.
Does the Dantes Exchange MCP server require authentication?
No. We connected to Dantes Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Dantes Exchange MCP server still maintained?
Dantes Exchange is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.