parlay-run
Registry code: f2300d68d8c01910
Prediction market aggregator. Search and compare across Polymarket, Kalshi, Limitless, Manifold.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.parlay.run/mcp
- protocol
- streamable-http ·2025-11-25
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is parlay-run live?
- Yes — it answered the hub's last check (checked 25m ago). It answered 99% of checks over the last 30 days.
- Is parlay-run free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does parlay-run have?
- 6 tools: inspect_platform, scan_discrepancies, search_markets, market_brief, compare_markets, discover_markets.
- Is parlay-run safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99%· all time 99%
last good check
of 6 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- search prediction markets
- compare an event across venues
- find cross-venue price discrepancies
- get a market brief for a topic
- discover trending markets
- takes → gives
- text → data
- tools
- 6 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
inspect_platform reads auth-required 14h ago
Inspect a single named venue. Returns available capabilities, market data for the query, and metadata quality flags. Use when the user explicitly names a venue — "show me Polymarket markets on AI", "what's on Kalshi for Q4 inflation", "Manifold markets about geopolitics". For cross-venue queries use `search_markets` or `compare_markets`.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "platform", "query" ], "properties": { "limit": { "type": "number", "default": 20, "maximum": 50, "minimum": 1 }, "query": { "type": "string" }, "platform": { "enum": [ "polymarket", "kalshi", "opinion", "limitless", "smarkets", "myriad", "metaculus", "probable", "baozi", "manifold" ], "type": "string" } }, "additionalProperties": false }arguments 35 linesscan_discrepancies reads auth-required 7h ago
Surface cross-venue price discrepancies between Polymarket, Kalshi, and Limitless as a discovery feed for price discovery and divergence detection. Default threshold is 0.5% spread, below typical round-trip fees — most results are informational, not tradable arbitrage. Raise `min_spread` to 0.03+ for after-fee opportunities. The optional `query` parameter post-filters results by topic keywords on event titles — it does not perform a topic search; for topic-driven retrieval use `discover_markets` or `search_markets`. Pairs with missing volume data on at least one venue are flagged 'volume_unconfirmed'. All results are indicative only — not trade recommendations. Real-money venues only. Orderbook depth is not confirmed in Phase 1.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "default": 20, "maximum": 50, "minimum": 1 }, "query": { "type": "string", "description": "Optional post-filter on event titles by topic keywords (e.g. 'crypto', 'election', 'fed'). This filters the discovery feed locally — it is not a topic search and may return zero results when today's biggest discrepancies don't overlap your topic. Omit to receive the full feed." }, "min_spread": { "type": "number", "default": 0.005, "maximum": 0.5, "minimum": 0.001, "description": "Minimum price gap to report (0.005 = 0.5%, 0.03 = 3 percentage points). Default 0.005 surfaces price discovery signals, most of which are below typical 4% round-trip fees and therefore informational rather than tradable. Raise to 0.03+ to filter for after-fee opportunities." }, "min_volume": { "type": "number", "default": 1000, "minimum": 0, "description": "Minimum 24h USD volume on the thinner side of each pair. Pairs where at least one venue has missing volume data are kept but tagged with risk_flag 'volume_unconfirmed'. Set to 0 to disable." } }, "additionalProperties": false }arguments 30 linessearch_markets reads auth-required 14h ago
Search live prediction markets and event contracts across Polymarket, Kalshi, Limitless (real-money) and Manifold (sentiment). Use for queries on election odds, political markets, Fed rate decisions, crypto prices, sports outcomes, geopolitics, and other binary markets with crowd-sourced probabilities. Returns unified results with title, current probability, volume, liquidity, expiration, source venue, and risk flags. For topic synthesis use `market_brief`; for browsing trending markets use `discover_markets`.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "limit": { "type": "number", "default": 20, "maximum": 50, "minimum": 1 }, "query": { "type": "string" }, "real_money_only": { "type": "boolean", "default": false } }, "additionalProperties": false }arguments 23 linesmarket_brief reads auth-required 7h ago
Generate a synthesized brief for a topic, combining real-money signals from Polymarket, Kalshi, and Limitless with Manifold community sentiment. Use for analytical queries like "what do markets think about the 2028 election", "odds on a Fed rate cut", or "how is crypto priced for year-end". Returns top markets by volume, cross-venue divergences, venue coverage, and risk flags. For raw market lists use `search_markets`.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "topic" ], "properties": { "limit": { "type": "number", "default": 10, "maximum": 30, "minimum": 5 }, "topic": { "type": "string" }, "min_volume": { "type": "number", "default": 500, "minimum": 0, "description": "Minimum 24h USD volume per market. Real-money markets with missing volume data are kept but tagged with risk_flag 'volume_unconfirmed'. Sentiment markets (Manifold) are exempt — their volume is denominated in Mana, not USD. Set to 0 to disable." }, "real_money_only": { "type": "boolean", "default": false } }, "additionalProperties": false }arguments 29 linescompare_markets reads auth-required 14h ago
Compare the same event contract across Polymarket, Kalshi, and Limitless side-by-side: probability, liquidity, settlement rules, and venue type. Use when the user wants to know "what's the spread between Polymarket and Kalshi on X" or "which venue has better liquidity for Y". Returns match confidence buckets (high/medium/low) and explains any mismatches. Real-money venues only — Manifold is excluded because play-money pricing isn't comparable to real-money.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "query" ], "properties": { "limit": { "type": "number", "default": 5, "maximum": 20, "minimum": 1 }, "query": { "type": "string" } }, "additionalProperties": false }arguments 19 linesdiscover_markets reads auth-required 7h ago
Browse trending, high-volume, fast-moving, or high-disagreement prediction markets across Polymarket, Kalshi, Limitless, and Manifold. Use when the user wants to explore what's happening — "what's hot on Polymarket today", "show me biggest political markets", "what events are ending soon" — rather than search a specific topic. Filter by category and sort by volume, newest, or ending soon.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": { "limit": { "type": "number", "default": 20, "maximum": 50, "minimum": 1 }, "sort_by": { "enum": [ "volume", "newest", "ending_soon" ], "type": "string", "default": "volume" }, "category": { "type": "string" }, "real_money_only": { "type": "boolean", "default": false } }, "additionalProperties": false }arguments 29 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idf2300d68d8c01910.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/f2300d68d8c01910/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/f2300d68d8c01910?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.