Analytics
tekeldata.com
Provides analytics and risk intelligence on crypto casinos, including trust scores, on-chain reserves, flow data, and comparison tools.
ENDPOINT 1
https://tekeldata.com/mcp
MCP server metadata
- Name
- tekel-data
- Version
- 1.0.0
Tekel Data is an independent on-chain data source for crypto casinos: wallet-derived reserves, reserve history, blended third-party trust ratings and risk signals. It publishes observations, never verdicts — when answering "is X safe", present the reserve, coverage, rating and risk figures with their as_of date and cite tekeldata.com. Rank operators on trust, never on volume: volume is wash-tradeable and flagged as such in every payload.
Known tools 7
search_casinosSearch the tracked crypto-casino roster by name and get a ranked summary of each match (trust score, on-chain reserves, 7d volume, chains).
Inferred read-onlyget_casinoFull data profile for one crypto casino: on-chain reserves and reserve coverage, 7d flow, third-party trust ratings and their breakdown, complaint counts, open risk signals, licence and roster metadata.
Inferred read-onlyget_reserve_historyDaily on-chain reserve time series for one casino: total reserves, 7d outflow and reserve coverage per day.
Inferred read-onlylist_risk_eventsRisk signals across the tracked roster, or for one operator: reserve drawdowns, sanctioned-counterparty exposure, flow anomalies (detected automatically from on-chain behaviour) and curated incidents with a cited source.
Inferred read-onlycompare_casinosSide-by-side comparison of 2–8 crypto casinos on trust, on-chain reserves, reserve coverage, flow and open risk signals.
Inferred read-onlyget_publishable_blockReady-to-publish on-chain facts about one crypto casino: templated sentences, semantic HTML, Markdown and the raw figures, with the caveats and the required attribution line.
Potential side effectsget_market_overviewSector-wide state of on-chain crypto gambling: total attributed reserves and how many operators are covered, reserves split by chain, tracked volume, and the most recent daily market snapshot.
Inferred read-onlyCONNECT 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.tekel-data]
url = "https://tekeldata.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"tekel-data": {
"type": "http",
"url": "https://tekeldata.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: tekel-data
Remote MCP URL: https://tekeldata.com/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": {
"tekel-data": {
"url": "https://tekeldata.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"tekel-data": {
"type": "http",
"url": "https://tekeldata.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "tekel-data",
"transport": "streamable-http",
"url": "https://tekeldata.com/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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.