# PolyBridge (remote · mcp.polybridge.ai)

Calibrated probabilistic foresight for AI agents, powered by live prediction-market signal.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.polybridge.ai`: 67/100 (this document), [markdown](https://verifymcp.io/servers/crowdvector-polybridge-mcp/mcp.md), [page](https://verifymcp.io/servers/crowdvector-polybridge-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.polybridge.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.5`

## 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-03.

- **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 2 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 315 tokens (~157/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http crowdvector-polybridge-mcp https://mcp.polybridge.ai/mcp
```

### Codex

```toml
[mcp_servers.crowdvector-polybridge-mcp]
url = "https://mcp.polybridge.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "crowdvector-polybridge-mcp": {
      "type": "remote",
      "url": "https://mcp.polybridge.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add crowdvector-polybridge-mcp --url https://mcp.polybridge.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  crowdvector-polybridge-mcp:
    url: "https://mcp.polybridge.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "crowdvector-polybridge-mcp": {
      "type": "http",
      "url": "https://mcp.polybridge.ai/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-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 63)

First indexed and scored.

## MCP tools (2)

### `polybridge_search` (~148 tokens)

PolyBridge Search

Search public prediction markets for markets relevant to a natural-language topic or question. Use when you need candidate markets, market URLs, outcomes, statuses, and relevance scores. Do not use for a final probability forecast, market-history lookup, trading, or private/internal data. Scores are relevance scores, not probabilities.

Input parameters:

- `dimensions` (array): Search dimensions to run. Uses all supported dimensions by default.
- `filters`: Optional market filters. Currently only filters.status is supported, with active, closed, or resolved.
- `query` (string, required): Natural-language topic or question to match to public markets.
- `top_k_per_dimension` (integer): Maximum number of candidate markets to return per search dimension.

Output parameters:

- `dimensions_returned` (array)
- `query` (string)
- `request_id` (string)
- `results` (array)
- `total_markets` (integer)
- `warnings` (array)

### `polybridge_forecast` (~109 tokens)

PolyBridge Forecast

Generate a read-only probability forecast for a clearly stated future event by searching relevant prediction markets and synthesizing evidence. Use when the user asks for a probability, outlook, or forecast; use polybridge_search when they only need market discovery. Does not place trades, provide financial advice, or access private/internal data.

Input parameters:

- `include_graph` (boolean): Whether to include the causal graph in the structured response.
- `question` (string, required): Clearly stated future-event forecasting question, 500 characters or fewer.

Output parameters:

- `causal_graph`
- `confidence` (number)
- `confidence_interval`
- `distribution`
- `engine_type`
- `error`
- `latency_ms` (integer)
- `markets_used` (array)
- `metadata` (object)
- `probability`
- `question` (string)
- `reasoning` (string)
- `request_id` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/crowdvector-polybridge-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 65
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 63

## Links

- Remote endpoint: https://mcp.polybridge.ai/mcp
- Website: https://polybridge.ai/api/mcp
- Changelog RSS feed: https://verifymcp.io/servers/crowdvector-polybridge-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/crowdvector-polybridge-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/crowdvector-polybridge-mcp/mcp