mcpbeat

Event Resolver API MCP Server

io.github.Br0ski777/event-resolver
answering

Event Resolver API is answering right now. Last checked 11 min ago. It exposes 3 tools. Last commit 19 Jul 2026.

Resolve prediction market events. Price checks, claim verification, outcome confidence.

Uptime history 43 hours of history
43 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
33 ms
Response time
average over 24h
0
Stars
last commit 19 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add event-resolver --transport http https://event-resolver.api.klymax402.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "event-resolver": {
      "url": "https://event-resolver.api.klymax402.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.event-resolver]
url = "https://event-resolver.api.klymax402.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "event-resolver": {
      "url": "https://event-resolver.api.klymax402.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "event-resolver": {
      "url": "https://event-resolver.api.klymax402.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

event
event_check_price_threshold
Use this when you need to check if a cryptocurrency or stock price has crossed a specific threshold -- the most common resolution type in prediction markets. Returns current price, whether threshold was crossed, and direction. 1. asset: the asset being checked (e.g. "bitcoin", "ethereum", "solana") 2. currentPrice: the current price in USD from CoinGecko 3. threshold: the target price threshold 4. direction: "above" or "below" -- which direction constitutes crossing 5. crossed: boolean indicating whether the price has crossed the threshold in the specified direction Example output: { "asset": "bitcoin", "currentPrice": 102450.23, "threshold": 100000, "direction": "above", "crossed": true } Use this for settling price-based prediction market contracts, monitoring price milestones, or triggering alerts when assets cross key levels. Uses CoinGecko free API for crypto prices (no auth required). Do NOT use for crypto prices only -- use token_get_price instead. Do NOT use for prediction market odds -- use prediction_list_markets instead. Do NOT use for stock prices -- use stock_get_quote instead. Do NOT use for trust/security scoring -- use trust_score_evaluate instead.
event_resolve_outcome
Use this when you need to determine the outcome of a real-world event for prediction market settlement. Takes a natural language question (e.g. "Did BTC reach $100K?", "Did France win the 2026 World Cup?") and returns a structured resolution with confidence score. 1. question: the original question being resolved 2. resolved: whether the event can be conclusively determined (true/false) 3. outcome: the determined result -- "Yes"/"No" for binary, a number for numeric, or a category string 4. confidence: 0-100 score indicating certainty of the resolution 5. sources: array of data sources consulted, each with name, url, and whether it agrees with the outcome 6. timestamp: ISO timestamp of when the resolution was performed Example output: { "question": "Did BTC reach $100K?", "resolved": true, "outcome": "Yes", "confidence": 95, "sources": [{ "name": "CoinGecko", "url": "https://coingecko.com", "agrees": true }], "timestamp": "2026-04-13T12:00:00Z" } Use this when settling prediction market contracts, verifying event outcomes for on-chain resolution, or building automated settlement oracles. Handles price-based questions via CoinGecko and general questions via web search aggregation. Do NOT use for prediction market odds -- use prediction_list_markets instead. Do NOT use for crypto prices only -- use token_get_price instead. Do NOT use for full fact checking with sources -- use research_check_fact instead. Do NOT use for trust/security scoring -- use trust_score_evaluate instead.
event_verify_claim
Use this when you need to quickly verify whether a factual claim is true or false. Simpler and cheaper than full event resolution -- designed for fast claim checking without structured market settlement. 1. claim: the original claim being verified 2. verdict: "true", "false", or "unverifiable" if insufficient data 3. confidence: 0-100 score indicating certainty of the verdict 4. evidence: array of strings summarizing supporting or contradicting evidence found Example output: { "claim": "Tesla stock is above $300", "verdict": "true", "confidence": 90, "evidence": ["CoinGecko/financial APIs confirm current price above threshold", "Multiple news sources corroborate"] } Use this for quick fact-checking before making decisions, verifying claims in conversation, or pre-screening questions before full resolution. Faster and cheaper than event_resolve_outcome for simple true/false checks. Do NOT use for prediction market odds -- use prediction_list_markets instead. Do NOT use for full fact checking with sources -- use research_check_fact instead. Do NOT use for stock prices -- use stock_get_quote instead. Do NOT use for crypto prices only -- use token_get_price instead.

Endpoints

URLTransportStateLatencyChecked
https://event-resolver.api.klymax402.com/mcp sse answering 39 ms 11 min ago

Event Resolver API — questions

Answers built from our own checks of this server.

What can Event Resolver API do?
It exposes 3 tools, read directly from the server on our last check. Among them: event_check_price_threshold, event_resolve_outcome, event_verify_claim. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Event Resolver API working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 33 ms. The bar chart above shows every period we have measured.
How do I connect Event Resolver API?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Event Resolver API need an API key?
No. Event Resolver API completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Event Resolver API?
It answers our handshake in 33 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Event Resolver API open source?
Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.