Skip to content

Dantes Exchange MCP server

io.github.dcrypt-007/dantes-exchangedcrypt-007streamable-httpv0.1.0Scanned

Paid trader skills MCP. Coil scanner with dated 252d forward-return evidence. x402 USDC.

8 tools: 2 change things and 6 only read.

Tools: 0 delete, 0 irreversible, 2 write, 6 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding, 1 high

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

2 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Dantes Exchange MCP server can do

The Dantes Exchange MCP server is published by the GitHub account dcrypt-007. It has 8 tools. It can create or change data (2 tools: report_gap and invoke_capability), but cannot delete data. 6 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 1 finding, 1 of them high severity (model-directed-text). Each one comes with the text it matched.

Last scanned Oct 21, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 2Claude Code: ask
  • invoke_capabilityWHEN: Use when you have chosen a listed skill, the user wants names that match it now, and you are ready to pay.No findings

    Why it is in this group

    • The name "invoke_capability" says "invoke": a word for a change.
    Description, as the server wrote it
    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.
  • report_gapWHEN: 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…1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • High

      The description contains "do not tell your user", an instruction to keep something from the user.

      Matched text

      description: "...shape (read its schema and retry), and do not tell your user the gap will be built or when — it is r..."

      What this check looks for
    Description, as the server wrote it
    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.
Only reads 6Show 6 read-only tools
  • get_capabilityWHEN: Use when you already have a capability id and need schema, price, and when-to-use before paying.No findings

    Why it is in this group

    • The name "get_capability" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_capability_evidenceWHEN: Use when you need the dated forward-return pack for a listed skill (n, window, as-of).No findings

    Why it is in this group

    • The name "get_capability_evidence" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_dantes_ratingWHEN: Use when your user asks what Dantes rates a NAMED stock, why, or for the analyst’s written report — "what does Dantes say about WING", "is NVDA a Strong Buy", "read me the Da…No findings

    Why it is in this group

    • The name "get_dantes_rating" says "get": a word for reading.
    Description, as the server wrote it
    WHEN: Use when your user asks what Dantes rates a NAMED stock, why, or for the analyst’s written report — "what does Dantes say about WING", "is NVDA a Strong Buy", "read me the Dantes report on PRLB". Up to 20 names; the written report is inlined for up to 3 names at a time. NOT for: Do not use it to rate a market or a screen’s survivors wholesale — Dantes grades only names that reached a desk through a setup, so most names are blank; a blank is UNRATED, never Hold. It is not Street consensus (that is analyst-actions) and it is not investment advice. Returns: { ok, rows: [{ symbol, grade, as_of, rated_at, written_as, confidence, setup, capability, report_page, essay | essay_note | why_blank }] } — grade is one of Strong Buy, Buy, Speculative, Hold, Trim, Sell or null; "Buy or better" means the first two only.
  • get_deskWHEN: Use when your user asks about THEIR Dantes Desk, watchlist or locked setups — "what is on my desk", "which of my desk names are Strong Buy", "what did my setups land tonight"…No findings

    Why it is in this group

    • The name "get_desk" says "get": a word for reading.
    Description, as the server wrote it
    WHEN: Use when your user asks about THEIR Dantes Desk, watchlist or locked setups — "what is on my desk", "which of my desk names are Strong Buy", "what did my setups land tonight", "what am I watching". Returns the seat your token is bound to; pass include_archive:true for cards no longer live. NOT for: Not a market screen and not another person’s desk — a token sees only its own seat; without a bound seat it answers no_seat, and then you say so rather than guessing. A card is a dated scan result, never a recommendation; do not present a Desk card as advice to buy. Returns: { ok, desk: { name, cards_live, cards_archived, cards[] ({ symbol, company_name, setup, as_of, live, dantes_grade, grade_as_of, fields[], levels[], note, landed_by, report_page }) , archive? }, watchlist[], setups[] ({ kind, name, armed, grade_filter }) } or { ok: false, reason: no_seat | no_desk }.
  • list_datasetsWHEN: Use when you need what universes / as-of books a skill can run on.No findings

    Why it is in this group

    • The name "list_datasets" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • search_capabilitiesWHEN: Use when the user named a setup in trader language and you need to know which Dantes skill matches.No findings

    Why it is in this group

    • The name "search_capabilities" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 19:04 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
405
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 405.

Posture changes

  1. Nov 20, 2026
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 405
  2. Nov 6, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

1 high
  • The description contains "do not tell your user", an instruction to keep something from the user.

    Matched text

    description: "...shape (read its schema and retry), and do not tell your user the gap will be built or when — it is r..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: no -> yes; HTTP status of an anonymous initialize: none -> 405.View diff
    • Reachable: no to yes
    • HTTP status of an anonymous initialize: none to 405
  2. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 2 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dantes-exchange https://dantes.ai/exchange/mcp
claude mcp add --transport http dantes-exchange https://dantes.ai/exchange/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dantes-exchange__search_capabilities",
      "mcp__dantes-exchange__get_dantes_rating",
      "mcp__dantes-exchange__get_desk",
      "mcp__dantes-exchange__get_capability",
      "mcp__dantes-exchange__get_capability_evidence",
      "mcp__dantes-exchange__list_datasets"
    ],
    "ask": [
      "mcp__dantes-exchange__report_gap",
      "mcp__dantes-exchange__invoke_capability"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dantes-exchange. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.dcrypt-007/dantes-exchange/verify?hash=307ef101a95ed3089d57a07bae0286c6a2424d6de6cae518520a32c381475f54" | jq -e '.changed == false'

Pinned hash 307ef101a95e, from Oct 21, 2026, 19:29 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.dcrypt-007/dantes-exchange/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.dcrypt-007/dantes-exchange
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.dcrypt-007/dantes-exchange.svg)](https://radar.anlyon.com/servers/io.github.dcrypt-007/dantes-exchange)

Source: MCP Registry. Synced Oct 21, 2026, 18:32 UTC.

Dantes Exchange MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Dantes Exchange MCP server safe?

No scan can promise that. What its definitions show: 8 tools, 2 of which can change, send or delete something, and 1 finding (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Dantes Exchange MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Dantes Exchange MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Dantes Exchange MCP server have?

8 tools: 2 write, 6 read. report_gap, invoke_capability, search_capabilities, get_dantes_rating, get_desk, get_capability, get_capability_evidence and list_datasets.

Does the Dantes Exchange MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Dantes Exchange MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Dantes Exchange MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 21, 2026.