← tekeldata.com

INDIVIDUAL MCP TOOL

get_publishable_block

Ready-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.

tekeldata.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://tekeldata.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_publishable_block and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.

Parent server

tekeldata.com

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.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.

Related tools

  • search_casinos — Search the tracked crypto-casino roster by name and get a ranked summary of each match (trust score, on-chain reserves, 7d volume, chains).
  • get_casino — Full 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.
  • get_reserve_history — Daily on-chain reserve time series for one casino: total reserves, 7d outflow and reserve coverage per day.
  • list_risk_events — Risk 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.
  • compare_casinos — Side-by-side comparison of 2–8 crypto casinos on trust, on-chain reserves, reserve coverage, flow and open risk signals.
  • get_market_overview — Sector-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.