# Prediction Market Friction Tracker (remote · prediction-friction-tracker-production.up.railway.app)

Prediction-market fee/KYC/withdrawal data, venue recommendations, and a paid x402 change feed.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `prediction-friction-tracker-production.up.railway.app`: 62/100 (this document), [markdown](https://verifymcp.io/servers/ndrysdal-byte-prediction-friction-tracker/prediction-friction-tracker-production.md), [page](https://verifymcp.io/servers/ndrysdal-byte-prediction-friction-tracker/prediction-friction-tracker-production)

## Channel facts

- Endpoint: `https://prediction-friction-tracker-production.up.railway.app/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 442 tokens (~110/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http ndrysdal-byte-prediction-friction-tracker https://prediction-friction-tracker-production.up.railway.app/mcp/
```

### Codex

```toml
[mcp_servers.ndrysdal-byte-prediction-friction-tracker]
url = "https://prediction-friction-tracker-production.up.railway.app/mcp/"
```

### opencode

```json
{
  "$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

```bash
openclaw mcp add ndrysdal-byte-prediction-friction-tracker --url https://prediction-friction-tracker-production.up.railway.app/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ndrysdal-byte-prediction-friction-tracker:
    url: "https://prediction-friction-tracker-production.up.railway.app/mcp/"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-19 (score 62, +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.

### 2026-08-17 (score 61, +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.

### 2026-08-15 (score 60, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-14 (score 59)

First indexed and scored.

## MCP tools (4)

### `list_venues` (~70 tokens)

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.

Input parameters:

- `confidence`

### `get_venue` (~61 tokens)

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.

Input parameters:

- `slug` (string, required)

### `get_changes_info` (~79 tokens)

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.

### `recommend_venue` (~232 tokens)

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.

Input parameters:

- `query` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ndrysdal-byte-prediction-friction-tracker/prediction-friction-tracker-production#diagnostics

## Score history

- 2026-08-20: 62
- 2026-08-19: 62
- 2026-08-18: 61
- 2026-08-17: 61
- 2026-08-16: 60
- 2026-08-15: 60
- 2026-08-14: 59

## Links

- Remote endpoint: https://prediction-friction-tracker-production.up.railway.app/mcp/
- Repository: https://github.com/ndrysdal-byte/prediction-friction-tracker
- Changelog RSS feed: https://verifymcp.io/servers/ndrysdal-byte-prediction-friction-tracker/prediction-friction-tracker-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/ndrysdal-byte-prediction-friction-tracker/prediction-friction-tracker-production.json
- HTML version of this page: https://verifymcp.io/servers/ndrysdal-byte-prediction-friction-tracker/prediction-friction-tracker-production