Prediction Market X Sentiment
REMOTE · PREDICTION-BOT-IGGF.ONRENDER.COM · 2 COMPONENTS · SCANNED OCT 7
Polymarket & Kalshi sentiment from X (Twitter) via Grok. Free daily scores; live scoring via x402.
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 563 tokens (~62/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Prediction Market X Sentiment MCP server?
Prediction Market X Sentiment is a hosted endpoint at https://prediction-bot-iggf.onrender.com/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 · prediction-bot-iggf.onrender.com
claude mcp add --transport http wballztrading1-prediction-bot 'https://prediction-bot-iggf.onrender.com/mcp'
{
"mcpServers": {
"wballztrading1-prediction-bot": {
"url": "https://prediction-bot-iggf.onrender.com/mcp"
}
}
} {
"servers": {
"wballztrading1-prediction-bot": {
"type": "http",
"url": "https://prediction-bot-iggf.onrender.com/mcp"
}
}
} [mcp_servers.wballztrading1-prediction-bot] url = "https://prediction-bot-iggf.onrender.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"wballztrading1-prediction-bot": {
"type": "remote",
"url": "https://prediction-bot-iggf.onrender.com/mcp",
"enabled": true
}
}
} openclaw mcp add wballztrading1-prediction-bot --url 'https://prediction-bot-iggf.onrender.com/mcp' --transport streamable-http
mcp_servers:
wballztrading1-prediction-bot:
url: "https://prediction-bot-iggf.onrender.com/mcp" {
"McpServers": {
"wballztrading1-prediction-bot": {
"Transport": "http",
"Url": "https://prediction-bot-iggf.onrender.com/mcp"
}
}
} assistant mcp add wballztrading1-prediction-bot -t streamable-http -u 'https://prediction-bot-iggf.onrender.com/mcp'
{
"mcpServers": {
"wballztrading1-prediction-bot": {
"type": "http",
"url": "https://prediction-bot-iggf.onrender.com/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.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 10. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Oct 26 72
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 8 Oct 2026 · Probed https://prediction-bot-iggf.onrender.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=onrender.com | CN=WE1,O=Google Trust Services,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6eb1e3fe7d0631ea1337bfa4a321c137 |
| SANs: onrender.com, *.onrender.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of prediction-bot-iggf.onrender.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| onrender.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://prediction-bot-iggf.onrender.com/mcp | Verified | 200 | |
| http (plaintext) | http://prediction-bot-iggf.onrender.com/mcp | HTTPS enforced | 301 | https://prediction-bot-iggf.onrender.com/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 →
get_catalog Route catalog (free) ~25
Free. Machine-readable catalog of every route, price, network and pay-to address.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | – | – | – |
| base_url | – | – | – |
| free | – | – | Free routes |
| network | – | – | Payment network (CAIP-2), e.g. eip155:8453 for Base |
| paid | – | – | Paid routes with prices |
| pay_to | – | – | – |
| service | – | – | – |
No examples provided.
get_daily_scores Daily market scores (free) ~63
Free. Latest daily X (Twitter) sentiment score for each prediction market we track (Polymarket), with the change since the previous day, the catalyst and the market's Yes price. For a fresh score on any other question use get_market_sentiment.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | Time of the newest score |
| count | – | – | – |
| markets | array | – | – |
| note | – | – | – |
No examples provided.
get_health Service status (free) ~19
Free. Service status, prices and the routes available.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| network | – | – | – |
| price_brief | – | – | – |
| price_lite | – | – | – |
| routes | – | – | – |
| status | – | – | – |
No examples provided.
get_market_brief Market brief with live odds ~91
Paid (see get_pricing). Full brief for a market question: score, catalyst, volume trend, change since the previous score, a one-line summary and live Polymarket and Kalshi odds.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | A Polymarket or Kalshi market question in plain words, e.g. 'Will the Fed cut rates in October 2026'. Up to 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | – |
| catalyst | – | – | – |
| error | – | – | Set when a spend cap blocked the call |
| how_to_pay | – | – | – |
| odds | – | – | Live Polymarket and Kalshi Yes prices for the matched market |
| payment_required | – | – | True when no payment was made; accepts and how_to_pay say how to pay |
| price_usd | – | – | – |
| question | – | – | – |
| score | – | – | -100 very bearish .. +100 very bullish |
| score_before | – | – | – |
| scored_at | – | – | – |
| shift | – | – | Change since the previous score |
| summary | – | – | One-line summary |
| url | – | – | – |
| volume_signal | – | – | rising, falling or flat |
No examples provided.
get_market_sentiment Live sentiment for a market ~91
Paid (see get_pricing). Fresh X (Twitter) sentiment for any Polymarket or Kalshi market question: score -100..100, the catalyst driving the chatter and the volume trend.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | A Polymarket or Kalshi market question in plain words, e.g. 'Will the Fed cut rates in October 2026'. Up to 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | – |
| catalyst | – | – | – |
| error | – | – | Set when a spend cap blocked the call |
| how_to_pay | – | – | – |
| payment_required | – | – | True when no payment was made; accepts and how_to_pay say how to pay |
| price_usd | – | – | – |
| question | – | – | – |
| score | – | – | -100 very bearish .. +100 very bullish |
| scored_at | – | – | – |
| url | – | – | – |
| volume_signal | – | – | rising, falling or flat |
No examples provided.
get_pricing Current prices (free) ~20
Free. Current USDC prices for the paid tools.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | – | – | – |
| ladder | – | – | – |
| network | – | – | – |
| price_brief | – | – | Price of /sentiment and /brief, e.g. $0.35 |
| price_lite | – | – | Price of /top and /shift, e.g. $0.35 |
No examples provided.
get_sample Example response (free) ~26
Free. Static example of a sentiment response (not live data) to preview the shape.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| demo | – | – | – |
| example_request | – | – | – |
| example_response | – | – | – |
| note | – | – | – |
No examples provided.
get_sentiment_shift Sentiment change for a market ~78
Paid (see get_pricing). Change in X sentiment for a market question since its previous score, with both timestamps and the catalyst.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | A Polymarket or Kalshi market question in plain words, e.g. 'Will the Fed cut rates in October 2026'. Up to 200 characters. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | – |
| catalyst | – | – | – |
| error | – | – | Set when a spend cap blocked the call |
| how_to_pay | – | – | – |
| payment_required | – | – | True when no payment was made; accepts and how_to_pay say how to pay |
| price_usd | – | – | – |
| prior_scored_at | – | – | – |
| question | – | – | – |
| score_before | – | – | – |
| score_now | – | – | – |
| scored_at | – | – | – |
| shift | – | – | – |
| url | – | – | – |
No examples provided.
get_top_markets Most-discussed markets on X ~49
Paid (see get_pricing). The three Polymarket/Kalshi markets most discussed on X right now, each with a sentiment score (-100..100), catalyst and volume trend.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | – |
| error | – | – | Set when a spend cap blocked the call |
| how_to_pay | – | – | – |
| markets | – | – | Up to 3 markets, each with score, catalyst, volume_signal |
| payment_required | – | – | True when no payment was made; accepts and how_to_pay say how to pay |
| price_usd | – | – | – |
| scored_at | – | – | – |
| url | – | – | – |
No examples provided.
What is the Prediction Market X Sentiment MCP server?
Prediction Market X Sentiment is an MCP server listed in the public MCP registry as io.github.wballztrading1/prediction-bot. Polymarket & Kalshi sentiment from X (Twitter) via Grok. Free daily scores; live scoring via x402. This page covers its hosted endpoint (https://prediction-bot-iggf.onrender.com/mcp).
Is the Prediction Market X Sentiment MCP server safe to use?
Prediction Market X Sentiment scores 73 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 Prediction Market X Sentiment MCP server expose?
Prediction Market X Sentiment exposes 9 tools: get_daily_scores, get_catalog, get_pricing, get_sample, get_health, and 4 more. Their descriptions and schemas cost roughly 462 tokens of context every time the server is loaded.
Does the Prediction Market X Sentiment MCP server require authentication?
No. We connected to Prediction Market X Sentiment without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Prediction Market X Sentiment MCP server still maintained?
Prediction Market X Sentiment is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.