Mantis
REMOTE · MANTISS.STORE · SCANNED SEP 22
Cross-venue prediction market routing for AI agents with arbitrage, quotes, history, and signals.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 692 tokens (~115/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_url" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Mantis MCP server?
Mantis is a hosted endpoint at https://mantiss.store/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mantiss.store
claude mcp add --transport http alfred768-mantis 'https://mantiss.store/mcp'
{
"mcpServers": {
"alfred768-mantis": {
"url": "https://mantiss.store/mcp"
}
}
} {
"servers": {
"alfred768-mantis": {
"type": "http",
"url": "https://mantiss.store/mcp"
}
}
} [mcp_servers.alfred768-mantis] url = "https://mantiss.store/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alfred768-mantis": {
"type": "remote",
"url": "https://mantiss.store/mcp",
"enabled": true
}
}
} openclaw mcp add alfred768-mantis --url 'https://mantiss.store/mcp' --transport streamable-http
mcp_servers:
alfred768-mantis:
url: "https://mantiss.store/mcp" {
"McpServers": {
"alfred768-mantis": {
"Transport": "http",
"Url": "https://mantiss.store/mcp"
}
}
} assistant mcp add alfred768-mantis -t streamable-http -u 'https://mantiss.store/mcp'
{
"mcpServers": {
"alfred768-mantis": {
"type": "http",
"url": "https://mantiss.store/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://mantiss.store/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mantiss.store | CN=YR1,O=Let's Encrypt,C=US | 16 Aug 2026 | 14 Nov 2026 | RSA 2048 | SHA256-RSA | 635472d5bf3ca82c13cf9b487b1d31bca62 |
| SANs: mantiss.store | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mantiss.store. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| store. | present | 2327 | 13 | Verified |
| mantiss.store. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mantiss.store/mcp | Verified | 200 | |
| http (plaintext) | http://mantiss.store/mcp | HTTPS enforced | 308 | https://mantiss.store/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
execute_url ~146
Get a deep link URL to place a trade on the best venue for a given market. The URL has a referral code embedded so the platform earns commission. Call this to get the URL, then direct the user to open it.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | – | USD amount to trade (for tracking) |
| canonical_id | string | – | Cross-venue canonical market ID |
| market_id | string | – | Platform-specific market ID (e.g. "polymarket-abc123") |
| route_query | string | – | Original route_market query when source is route |
| side | string | – | Which side to trade |
| source | string | – | Tool path that produced this execution intent |
No output schema declared.
No examples provided.
get_arbitrage ~160
Find live cross-venue arbitrage opportunities — markets where the same event trades at different prices on Polymarket vs Kalshi vs other venues. Can also estimate fee-normalized net spread for a position size.
| Name | Type | Req | Description |
|---|---|---|---|
| include_fees | boolean | – | Whether to include estimated fee/friction normalization |
| min_spread_pct | number | – | Minimum spread in percentage points (default 4 = 4¢) |
| position_size | number | – | USD position size used for fee/slippage estimation |
| venue_a | string | – | Optional venue filter for one side of the arbitrage pair, e.g. polymarket |
| venue_b | string | – | Optional venue filter for the other side of the arbitrage pair, e.g. kalshi |
No output schema declared.
No examples provided.
get_history ~155
Get historical OHLCV-style prediction market candles over a time range, including the latest stored depth snapshot within each bucket when available. Can also export CSV text or base64-encoded Parquet.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | – | Cross-venue canonical market ID |
| format | string | – | Return JSON candles, CSV text payload, or base64-encoded Parquet payload |
| from | string | yes | Inclusive ISO 8601 start timestamp |
| granularity | string | – | Bucket size for history candles |
| market_id | string | – | Platform-specific market ID |
| to | string | yes | Inclusive ISO 8601 end timestamp |
| venue | string | – | Venue filter, e.g. polymarket or kalshi |
No output schema declared.
No examples provided.
get_quote ~84
Get the live probability, liquidity, and volume for a prediction market across all venues. Can also return venue order book depth and size-aware VWAP/slippage estimates.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical_id | string | – | Cross-venue canonical market ID |
| market_id | string | – | Platform-specific market ID |
| size | number | – | USD size for YES-buy VWAP/slippage estimation |
No output schema declared.
No examples provided.
get_unmet_demand ~69
Find questions that users are searching for but no prediction market exists. Useful for discovering new market creation opportunities or identifying emerging topics with real trading interest.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Lookback window in days (default 7) |
| limit | integer | – | Max results (default 20) |
No output schema declared.
No examples provided.
route_market ~78
Find the best prediction market for a natural-language question or trading intent. Returns the best cross-venue match, current probability, liquidity, and any arbitrage opportunity between venues.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | Natural language question or trading intent, e.g. "Will BTC reach $200k in 2025?" or "Fed rate cut September" |
No output schema declared.
No examples provided.
What is the Mantis MCP server?
Mantis is an MCP server listed in the public MCP registry as io.github.Alfred768/mantis. Cross-venue prediction market routing for AI agents with arbitrage, quotes, history, and signals. This page covers its hosted endpoint (https://mantiss.store/mcp).
Is the Mantis MCP server safe to use?
Mantis scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Mantis MCP server expose?
Mantis exposes 6 tools: route_market, get_arbitrage, execute_url, get_quote, get_history, get_unmet_demand. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.
Does the Mantis MCP server require authentication?
No. We connected to Mantis without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mantis MCP server still maintained?
Mantis is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.