ZBS Index What actually exists in applied AI, with the source next to it

mcp server

Event Resolver API

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

Description as published by the maintainer. Source

  • version 1.1.0
  • active

active — Most recent push to the repository was 2026-07-19.

What this server can do

3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.

event_check_price_threshold(asset, direction, 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. Required: asset, threshold, direction.
event_resolve_outcome(type, question)
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. Required: question.
event_verify_claim(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. Required: claim.

Last successful function declaration observed on . Source: https://event-resolver.api.klymax402.com/mcp. We list what the server declared; we do not call any of these functions.

Endpoint status observed on . Source: https://event-resolver.api.klymax402.com/mcp.

Signals

These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.

Signal Value What it measures Window Observed Source
GitHub stars 0 Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. cumulative, all time GitHub
Last commit 2026-07-19 Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. point in time GitHub
Open issues 0 Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. as of fetch GitHub
Latest published version 1.1.0 Latest version string the maintainer published to the registry. as of fetch Model Context Protocol
Registry record last updated 2026-05-16 When the registry record was last updated by its maintainer. point in time Model Context Protocol
License MIT Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. as of fetch GitHub
First listed in the MCP Registry 2026-05-16 Date this server was first published to the official MCP Registry. Not a usage or quality measure. point in time Model Context Protocol
repository status active The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. as of fetch GitHub
mcp tools declared 3 tools Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. as of probe event-resolver.api.klymax402.com
mcp endpoint status ok The server listed 3 functions when asked. as of probe event-resolver.api.klymax402.com

Where to get it

Related, by what their authors tagged them

  • Prediction Markets API — last commit 2026-07-19, shares crypto, prediction-markets, x402
    Prediction market odds from Polymarket. Active markets, probabilities, volume. x402.
  • CoinRithm Agent Trading — last commit 2026-08-06, shares crypto, prediction-markets
    Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM.
  • io.github.craigmbrown/blindoracle — last commit 2026-07-06, shares prediction-markets, x402
    The trust layer for the x402 agent economy: verifiable agent identity, payment & audit.
  • com.predictionmarketspicks/quant — last commit 2026-07-27, shares prediction-markets
    Quant tools + an NFL fantasy draft assistant for AI agents — Kalshi & Polymarket EV, edge, ADP.
  • stat-api — Sports Data — last commit 2026-07-07, shares prediction-markets
    NFL/NBA/MLB/NHL/PGA + DFS and prediction-market data. Browse free; query with a free API key.
  • ClearMarket — last commit 2026-08-06, shares prediction-markets
    Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance.
  • Simmer — last commit 2026-08-05, shares prediction-markets
    Trade prediction markets with AI agents — skill discovery, autoresearch, and execution.
  • Polymarket MCP — last commit 2026-08-05, shares prediction-markets
    Polymarket market data, live CLOB books, replay, simulation, and opt-in trading in Rust.
  • io.github.bolivian-peru/baozi-mcp — last commit 2026-04-17, shares prediction-markets
    68 tools for AI agents to interact with Solana prediction markets on Baozi.bet
  • Kalshi Prediction Markets — last commit 2026-08-05, shares prediction-markets
    MCP server for Kalshi prediction markets: native RSA-PSS auth, rate limiting, demo/prod safety.

These share tags the maintainers applied themselves, such as crypto, prediction-markets, x402. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.

This is not a recommendation and not a test result. It is a map of what the authors said their work is about.

Also from br0ski777

  • Address Validator API — last commit 2026-07-19
    Parse, validate and normalize postal addresses. Detect country, verify format. x402.
  • AI Text Summarizer API — last commit 2026-07-19
    Summarize text or URLs into key points with compression ratio and reading time. x402 USDC.
  • Airdrop Checker API — last commit 2026-07-19
    Check wallet eligibility for active crypto airdrops — LayerZero, EigenLayer, Scroll. x402.
  • Barcode Generator API — last commit 2026-07-18
    Generate barcodes — EAN-13, UPC-A, Code128, Code39. Returns SVG. x402 micropayment.
  • Base DeFi Yield Optimizer API — last commit 2026-07-19
    Base chain DeFi yields — Aerodrome, Moonwell, APY, TVL, risk scores. x402.
  • Base64 Codec API — last commit 2026-07-18
    Encode/decode base64 and URL-safe base64. x402 micropayment.
  • Cross-Chain Bridge Route API — last commit 2026-07-19
    Best cross-chain bridge routes with fees, time, providers. LI.FI-powered. x402.
  • Code Sandbox API — last commit 2026-07-31
    Execute Python, JavaScript, SQL code in a sandbox. x402 micropayment.
  • Color Palette Generator API — last commit 2026-07-18
    Generate harmonious color palettes — complementary, analogous, triadic. x402 micropayment.
  • Company Enrichment API — last commit 2026-07-31
    Company firmographics from domain: name, socials, tech stack, emails, phone, address

How the author describes it

Topics the maintainer set on GitHub: ai-agents, crypto, mcp, mcp-server, prediction-markets, x402.

This record as data

Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.

GET /api/v1/entries/mcp_server.json

Sources

  1. Br0ski777/event-resolver-x402 on GitHub — GitHub, observed , trust tier 3.
  2. Tools declared by the MCP server at https://event-resolver.api.klymax402.com/mcp — event-resolver.api.klymax402.com, observed , trust tier 1.
  3. Official MCP Registry — Model Context Protocol, observed , trust tier 1.