Prediction Market Friction Tracker
REMOTE · PREDICTION-FRICTION-TRACKER-PRODUCTION.UP.RAILWAY.APP · SCANNED AUG 20
Prediction-market fee/KYC/withdrawal data, venue recommendations, and a paid x402 change feed.
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 →
Endpoint Security57
- 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 4 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
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 442 tokens (~110/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · prediction-friction-tracker-production.up.railway.app
claude mcp add --transport http ndrysdal-byte-prediction-friction-tracker https://prediction-friction-tracker-production.up.railway.app/mcp/
[mcp_servers.ndrysdal-byte-prediction-friction-tracker] url = "https://prediction-friction-tracker-production.up.railway.app/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ndrysdal-byte-prediction-friction-tracker": {
"type": "remote",
"url": "https://prediction-friction-tracker-production.up.railway.app/mcp/",
"enabled": true
}
}
} openclaw mcp add ndrysdal-byte-prediction-friction-tracker --url https://prediction-friction-tracker-production.up.railway.app/mcp/ --transport streamable-http
mcp_servers:
ndrysdal-byte-prediction-friction-tracker:
url: "https://prediction-friction-tracker-production.up.railway.app/mcp/" {
"mcpServers": {
"ndrysdal-byte-prediction-friction-tracker": {
"type": "http",
"url": "https://prediction-friction-tracker-production.up.railway.app/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.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 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.
- 15 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Aug 26 59
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 20 Aug 2026 · Probed https://prediction-friction-tracker-production.up.railway.app/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| 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 |
DNSSEC insecure
Validation of prediction-friction-tracker-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://prediction-friction-tracker-production.up.railway.app/mcp/ | Verified | 200 | |
| http (plaintext) | http://prediction-friction-tracker-production.up.railway.app/mcp/ | HTTPS enforced | 301 | https://prediction-friction-tracker-production.up.railway.app/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.
get_changes_info ~79
Describes the change feed -- an append-only log of every detected fee/KYC/withdrawal/API change across venues since a given timestamp. This is the paid, time-sensitive product; it is gated by the x402 protocol (HTTP 402) rather than exposed here, so it stays accurate to call directly for real-time data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_venue ~61
Get one venue's current fee/KYC/withdrawal/API-access data by slug (e.g. 'kalshi', 'polymarket'). Free. Call list_venues first if the slug isn't already known.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | – |
No output schema declared.
No examples provided.
list_venues ~70
List all tracked prediction market venues with their current fee/KYC/withdrawal snapshot. Free. Args: confidence: optional filter -- 'verified', 'stale', or 'unconfirmed'. Use 'unconfirmed' to find venues whose data needs a human check.
| Name | Type | Req | Description |
|---|---|---|---|
| confidence | – | – | – |
No output schema declared.
No examples provided.
recommend_venue ~232
Recommend which tracked prediction-market venue best fits a natural- language need, by weighing fee/KYC/withdrawal/API-access/jurisdiction data against what the query asks for. Free. Use this for comparative "which venue is best for X" questions -- e.g. "lowest fees for high-frequency trading", "I don't want to do KYC", "programmatic API access without a wallet", "fastest withdrawals". For a single already-known venue use get_venue instead; to browse/filter by confidence use list_venues. Based only on the structured fields this tracker collects (fees, KYC, geo restrictions, withdrawal methods/limits, API access, jurisdiction, custody model). It does NOT have liquidity, trading volume, spread, or uptime data -- if the query depends on those, the response says so rather than guessing. Args: query: free-text description of what matters (cost, KYC/privacy, withdrawal speed, API access, jurisdiction, custody, etc). Can combine multiple criteria in one query.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
No output schema declared.
No examples provided.