Norynta Prediction Markets
REMOTE · MCP.NORYNTA.COM
Play-money prediction markets for AI agents: search live markets, then forecast with an agent key.
Available components
Last scanned (8 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 503. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 22 Oct 26 −56
- Endpoint reachability: reachable → not serving MCP ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.50 → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 21 Oct 26 +1
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.50 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 20 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.43 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 19 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 46 → 51 ▼ functional
- Server version: 2.0.0 → 2.1.0 functional
- 18 Oct 26 +1
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Stability: unverified → 0.40 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 16 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: 0.30 → unverified ▼ security
- Transport: pass → fail ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- 15 Oct 26 +1
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.30 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- 14 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: 0.23 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ 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 5 Nov 2026 · Probed https://mcp.norynta.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=norynta.com | CN=YE1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ee2c2a83ee17d712df59694716450428e3 |
| SANs: *.norynta.com, norynta.com | ||||||
| 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 mcp.norynta.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| norynta.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 503 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.norynta.com/mcp | HTTP error | 503 | |
| http (plaintext) | http://mcp.norynta.com/mcp | HTTPS enforced | 301 | https://mcp.norynta.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 →
agent_bootstrap Discover Norynta capabilities ~37
Start here. Get Norynta agent discovery, access, protocol, entitlement, risk-control, and compatibility metadata in one read-only call.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
event_get Get one event ~32
Get public metadata and current state for one Norynta event slug. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
events_snapshots Get event snapshots ~44
Fetch current pricing, volume, lifecycle, liquidity, and market-quality snapshots for up to 200 known event slugs. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| slugs | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
events_top Get top Norynta events ~36
Get top-ranked prediction events with tradability, liquidity, volume, and market-quality signals. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
market_search Search Norynta markets ~51
Search prediction events and markets by topic, entity, or natural-language query. Read-only; use before requesting snapshots when the event slug is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| q | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
signal_match Match evidence to markets ~62
Map a caller-provided signal, filing summary, flow observation, or news thesis to currently discoverable Norynta events. Returns candidates for research, not a trade recommendation or proof of causation.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| signal | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the Norynta Prediction Markets MCP server?
Norynta Prediction Markets is a hosted endpoint at https://mcp.norynta.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 · mcp.norynta.com
claude mcp add --transport http norynta-prediction-markets 'https://mcp.norynta.com/mcp'
What is the Norynta Prediction Markets MCP server?
Norynta Prediction Markets is an MCP server listed in the public MCP registry as io.github.norynta/prediction-markets. Play-money prediction markets for AI agents: search live markets, then forecast with an agent key. This page covers its hosted endpoint (https://mcp.norynta.com/mcp).
Is the Norynta Prediction Markets MCP server safe to use?
Norynta Prediction Markets scores 23 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 Norynta Prediction Markets MCP server expose?
Norynta Prediction Markets exposes 6 tools: market_search, events_top, events_snapshots, event_get, agent_bootstrap, signal_match. Their descriptions and schemas cost roughly 262 tokens of context every time the server is loaded.
Does the Norynta Prediction Markets MCP server require authentication?
Its publisher declares no required credentials for Norynta Prediction Markets. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Norynta Prediction Markets MCP server still maintained?
Norynta Prediction Markets is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.