Scanverity Resolution Rules
by scanverity.com in Markets & finance
Polymarket resolution-rule research for approved customers; public discovery is separate.
https://scanverity.com/mcp- Tools
- 5
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 61 ms
- 176 ms slowest 5%
- Last check
- Passed
- 8 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"scanverity-resolution-rules": {
"type": "http",
"url": "https://scanverity.com/mcp"
}
}
}5 tools
- scanverity_offers
Use this public tool when a user asks about Scanverity prices, products, access, written research, agent ordering or what to do without an approved customer account, including a single Polymarket contract review or a larger multi-contract research engagement. Public information…
- scanverity_limits
Use this when checking Scanverity connection permissions, Live versus Sandbox, local request limits, pricing links, how to request a written single-contract or larger team-research quote, or what a paid agent report requires. This read-only call gives current purchase paths and…
- scanverity_search_markets
Use this when a user asks about prediction markets or wants to research the conditions, deadlines or settlement risks behind a forecast about politics, elections, a ceasefire, economics, crypto or sport, even without naming Scanverity or providing a URL. Search by a short topic…
- scanverity_request_assessment
Use this when the user wants source-linked evidence about what makes a Polymarket contract settle Yes or No: resolution criteria, deadlines, ambiguous wording, dispute risk, or whether a forecast matches the contract. Works without naming Scanverity. If no exact contract is…
- scanverity_get_assessment
Use this after requesting Scanverity research, or when the user asks for an existing report or its progress. Read one saved assessment ID; no new report is created. Preserve billable and metering values from the API instead of assuming an invoice was paid. Uses one API call…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 8 h ago | Passed | 200 | 41 ms |
| 19 h ago | Passed | 200 | 32 ms |
| 30 h ago | Passed | 200 | 87 ms |
| 40 h ago | Passed | 200 | 35 ms |
| 2 days ago | Passed | 200 | 38 ms |
Show 10 older checks
| 3 days ago | Passed | 200 | 29 ms |
| 3 days ago | Passed | 200 | 82 ms |
| 3 days ago | Passed | 200 | 35 ms |
| 4 days ago | Passed | 200 | 100 ms |
| 4 days ago | Passed | 200 | 57 ms |
| 5 days ago | Passed | 200 | 36 ms |
| 5 days ago | Passed | 200 | 88 ms |
| 5 days ago | Passed | 200 | 58 ms |
| 6 days ago | Passed | 200 | 80 ms |
| 6 days ago | Passed | 200 | 25 ms |