← Registry

Security & Testing

detracker.xyz

Fetches DeFi security incident data and stablecoin peg status from the DeTracker feed, including latest incidents, protocol-specific incidents, and depeg monitor checks.

1 endpoint13 known toolsFirst detected September 23, 2026Last detected September 23, 2026

ENDPOINT 1

https://mcp.detracker.xyz/mcp

No auth detected

MCP server metadata

Name
detracker-mcp
Version
0.1.0
Capabilities
tools

Known tools 13

get_latest_incidents

Latest DeFi security incidents from the DeTracker feed, newest first.

Inferred read-only
get_incident

Full incident record by id.

Inferred read-only
get_protocol_incidents

Incidents involving a given protocol: matches the protocols field or the derived hashtag (#NameWithoutSpaces).

Inferred read-only
check_peg

Check whether a USD stablecoin is currently within its peg, using the DeTracker depeg monitor state.

Inferred read-only
list_depegged

Stablecoins currently off their USD peg (DeTracker depeg monitor); stale observations are omitted and counted separately.

Inferred read-only
list_protocol_reports

Index of tracked DeFi protocols with deterministic report scores and bands, linked to report pages.

Inferred read-only
get_protocol_report

Full deterministic report for a tracked protocol: score with component breakdown and penalties, section facts with sources and verifiability, AI executive summary (summary_pending when not yet generated), limitations.

Inferred read-only
list_protocols

Registry of tracked DeFi protocols: slug, name, pool type with label, chains, site, count of current facts and whether a deterministic report exists.

Inferred read-only
list_fact_categories

Catalog of fact categories collected per protocol: key, group, title, cardinality (once or many), recommended check interval and whether the category is enabled.

Inferred read-only
get_protocol_facts

Current (non-superseded) facts of a protocol: category key and group, occurrence key for many-facts, body, verifiability, structured data, evidence sources, first/last timestamps, plus counts by verifiability.

Inferred read-only
get_score_history

Score history of a protocol from deterministic report rebuilds: computed_at, score and band (from the stored breakdown), newest first.

Inferred read-only
get_btc_forecast

Latest Bitcoin direction forecast: probability of a higher close tomorrow (1d) and in 30 days (30d) with the contributing signal breakdown, plus the public track record (hit rate and Brier score over 30/90/365 day windows).

Inferred read-only
get_btc_metrics

Latest values and daily series of the tracked Bitcoin metrics across eight groups (trend, overbought/oversold, on-chain, derivatives, sentiment, macro, geopolitics, cycle).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.detracker-mcp]
url = "https://mcp.detracker.xyz/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "detracker-mcp": {
      "type": "http",
      "url": "https://mcp.detracker.xyz/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: detracker-mcp
Remote MCP URL: https://mcp.detracker.xyz/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "detracker-mcp": {
      "url": "https://mcp.detracker.xyz/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "detracker-mcp": {
      "type": "http",
      "url": "https://mcp.detracker.xyz/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "detracker-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.detracker.xyz/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.