Developer Tools
denpa.ai
Provides programmatic access to Denpa operator info, prediction market data, and live overlay signal management for developers.
ENDPOINT 1
https://denpa.ai/api/mcp
MCP server metadata
- Name
- denpa
- Version
- 1.0.0
Denpa is a broadcast protocol where prediction markets become live media surfaces. Authenticated tools act as the operator whose API key is connected (minted at denpa.ai/developer). Typical flow: denpa_whoami → denpa_featured_markets → denpa_push_signal (routes a SIGNAL to the operator's live page + OBS overlay) → denpa_bind_stream (attaches an HLS stream to a market page) → denpa_go_live (RTMP ingest + stream key; starting the stream creates the broadcast automatically). Language: SIGNAL, not bet; operator, not streamer. Signals are information, not financial advice.
Known tools 10
denpa_whoamiResolve the connected Denpa operator: handle, approval status, and links to their live page, OBS overlay, and public field record.
Inferred read-onlydenpa_featured_marketsList the featured/trending prediction markets on the Denpa home heatmap.
Inferred read-onlydenpa_marketGet a single Polymarket market (question, YES/NO prices, volume, close time) by numeric market id.
Inferred read-onlydenpa_push_signalRoute a SIGNAL to your live page and OBS overlay: feature a market with its current YES probability and an optional annotation.
Inferred read-onlydenpa_clear_signalClear the SIGNAL currently featured on your live page and overlay.
Inferred read-onlydenpa_get_signalRead the SIGNAL currently featured on an operator's live page (defaults to your own).
Inferred read-onlydenpa_bind_streamBind your live HLS stream to a market page so it appears on denpa.ai/m/<marketId> and pins a live tile on the home heatmap.
Inferred read-onlydenpa_go_liveProvision (or fetch) your broadcast ingest: RTMP server + stream key for OBS, plus your HLS playback URL.
Inferred read-onlydenpa_my_broadcastsList your recent broadcasts (stream receipts): start/end, duration, peak viewers, markets active.
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.denpa]
url = "https://denpa.ai/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"denpa": {
"type": "http",
"url": "https://denpa.ai/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: denpa
Remote MCP URL: https://denpa.ai/api/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": {
"denpa": {
"url": "https://denpa.ai/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"denpa": {
"type": "http",
"url": "https://denpa.ai/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "denpa",
"transport": "streamable-http",
"url": "https://denpa.ai/api/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.