Resolve prediction market events. Price checks, claim verification, outcome confidence.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-br0ski777-event-resolver": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Resolve prediction market events. Price checks, claim verification, outcome confidence.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Persistent memory using a knowledge graph
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
Make HTTP requests and fetch web content
Read, write, and manage files on the local filesystem
MCP Security Weekly
Get CVE alerts and security updates for io.github.Br0ski777/event-resolver and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Resolve real-world events for prediction market settlement. Aggregates data from multiple sources to determine if an event occurred, with confidence scores and source attribution.
| Endpoint | Method | Price | Description |
|---|---|---|---|
/api/resolve | POST | $0.005 | Full event resolution with confidence score and sources |
/api/verify | POST | $0.003 | Quick-verify a factual claim (true/false/unverifiable) |
/api/price-check | POST | $0.002 | Check if crypto price crossed a threshold |
curl -X POST https://event-resolver-production.up.railway.app/api/resolve \
-H "Content-Type: application/json" \
-d '{"question": "Did BTC reach $100K?", "type": "binary"}'
Response:
{
"question": "Did BTC reach $100K?",
"resolved": true,
"outcome": "Yes",
"confidence": 95,
"sources": [
{
"name": "CoinGecko",
"url": "https://www.coingecko.com/en/coins/bitcoin",
"agrees": true
}
],
"timestamp": "2026-04-13T12:00:00.000Z",
"type": "binary"
}
curl -X POST https://event-resolver-production.up.railway.app/api/verify \
-H "Content-Type: application/json" \
-d '{"claim": "Bitcoin is above $90,000"}'
Response:
{
"claim": "Bitcoin is above $90,000",
"verdict": "true",
"confidence": 95,
"evidence": [
"bitcoin current price: $102,450 (via CoinGecko)",
"Threshold $90,000 above: crossed"
]
}
curl -X POST https://event-resolver-production.up.railway.app/api/price-check \
-H "Content-Type: application/json" \
-d '{"asset": "bitcoin", "threshold": 100000, "direction": "above"}'
Response:
{
"asset": "bitcoin",
"currentPrice": 102450.23,
"threshold": 100000,
"direction": "above",
"crossed": true,
"crossedAt": "2026-04-13T12:00:00.000Z",
"timestamp": "2026-04-13T12:00:00.000Z"
}
Add to your Claude Desktop or Cursor config:
{
"mcpServers": {
"event-resolver": {
"url": "https://event-resolver-production.up.railway.app/sse"
}
}
}
All endpoints use x402 protocol -- pay-per-call with USDC on Base L2. No API keys, no subscriptions. Your agent pays automatically.