live.marketmaster/mcp
REMOTE · API.MARKETMASTER.LIVE · 2 COMPONENTS
Live Kalshi and Polymarket data: EV edges, cross-venue arbitrage, markets, and whale trades.
Available components
Last scanned (12 hours ago)
Scores higher than 95% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Finance and Payments
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 397 tokens (~66/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 Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 22% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 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
- 14 Oct 26 0
- Tool “mm_arbitrage” rewrote its description, which is the text the model reads security
- 12 Oct 26 0
- Tool “mm_markets” changed its title: List market snapshots cosmetic
- Tool “mm_status” changed its title: API key status cosmetic
- Tool “mm_whales” changed its title: Recent whale trades cosmetic
- Tool “mm_market” changed its title: Get one market cosmetic
- Tool “mm_arbitrage” changed its title: Cross-venue price spreads cosmetic
- Tool “mm_edges” changed its title: Find mispriced edges cosmetic
6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 28 Sept 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 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 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
- 3 Sept 26 0
- Authorization: unverified → pass ▲ security
- First check of Authorization: partial security
- 28 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
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 6 Nov 2026 · Probed https://api.marketmaster.live/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=marketmaster.live | CN=YE1,O=Let's Encrypt,C=US | 16 Sept 2026 | 15 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5e78ea3f9bce117830a6ac232fb13e7377a |
| SANs: *.marketmaster.live, marketmaster.live | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.marketmaster.live. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| live. | DS published | 4724 | 8 | Verified |
| marketmaster.live. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="marketmaster", resource_metadata="https://api.marketmaster.live/.well-known/oauth-protected-resource"
Bearer realm="marketmaster", resource_metadata="https://api.marketmaster.live/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Protected resource metadata
| Document | https://api.marketmaster.live/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.marketmaster.live/mcp |
| Authorisation server | https://api.marketmaster.live |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.marketmaster.live/mcp | Verified | 200 | |
| http (plaintext) | http://api.marketmaster.live/mcp | HTTPS enforced | 301 | https://api.marketmaster.live/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 →
mm_arbitrage Cross-venue price spreads ~92
Two-leg cross-venue locks on Yes/No markets listed on both Kalshi and Polymarket: buy YES on one venue and NO on the other at the ask. Returns the spread before fees and net of taker fees; depth and slippage not included.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min_spread | number | – | minimum spread in percentage points |
| offset | integer | – | – |
No output schema declared.
No examples provided.
mm_edges Find mispriced edges ~76
Mispriced prediction-market edges (model fair value vs live price), ranked by edge size, across Kalshi and Polymarket.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| min_edge | number | – | minimum absolute edge in percentage points |
| offset | integer | – | – |
| platform | string | – | – |
No output schema declared.
No examples provided.
mm_market Get one market ~45
A single market's latest snapshot plus any live edges for it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | the venue's native market id (source_market_id) |
| source | string | yes | – |
No output schema declared.
No examples provided.
mm_markets List market snapshots ~59
Latest normalized market snapshots across venues (title, YES/NO price, 24h volume, close time).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
mm_status API key status ~21
Your API key's tier, rate limits, and current usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mm_whales Recent whale trades ~58
Recent large real-money trades (whale fills) across venues, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| min | integer | – | minimum trade size in USD |
| offset | integer | – | – |
| source | string | – | – |
No output schema declared.
No examples provided.
How do I install the live.marketmaster/mcp server?
live.marketmaster/mcp is a hosted endpoint at https://api.marketmaster.live/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 · api.marketmaster.live
claude mcp add --transport http live-marketmaster-mcp 'https://api.marketmaster.live/mcp'
What is the live.marketmaster/mcp server?
live.marketmaster/mcp is listed in the public MCP registry as live.marketmaster/mcp. Live Kalshi and Polymarket data: EV edges, cross-venue arbitrage, markets, and whale trades. This page covers its hosted endpoint (https://api.marketmaster.live/mcp).
Is the live.marketmaster/mcp server safe to use?
live.marketmaster/mcp scores 88 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 live.marketmaster/mcp server expose?
live.marketmaster/mcp exposes 6 tools: mm_edges, mm_markets, mm_market, mm_arbitrage, mm_whales, mm_status. Their descriptions and schemas cost roughly 351 tokens of context every time the server is loaded.
Does the live.marketmaster/mcp server require authentication?
Yes. live.marketmaster/mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the live.marketmaster/mcp server still maintained?
live.marketmaster/mcp is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the live.marketmaster/mcp server?
VerifyMCP ran 13 checks on live.marketmaster/mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.