# rtcStats (remote · api.rtcstats.com)

Query analyzed WebRTC sessions: observations, deductions, experience scores, and AI summaries.

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

## Components

- remote · `api.rtcstats.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-rtcstats-rtcstats/v1-0-mcp.md), [page](https://verifymcp.io/servers/com-rtcstats-rtcstats/v1-0-mcp)

## Channel facts

- Endpoint: `https://api.rtcstats.com/v1.0/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-07.

- **Endpoint Security**: 63/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 3 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.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 50/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 909 tokens (~303/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% 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 com-rtcstats-rtcstats https://api.rtcstats.com/v1.0/mcp
```

### Codex

```toml
[mcp_servers.com-rtcstats-rtcstats]
url = "https://api.rtcstats.com/v1.0/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rtcstats-rtcstats": {
      "type": "remote",
      "url": "https://api.rtcstats.com/v1.0/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rtcstats-rtcstats --url https://api.rtcstats.com/v1.0/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rtcstats-rtcstats:
    url: "https://api.rtcstats.com/v1.0/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-rtcstats-rtcstats": {
      "type": "http",
      "url": "https://api.rtcstats.com/v1.0/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-07 (score 62, +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-06 (score 61, +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-08-05 (score 60, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-04 (score 60)

First indexed and scored.

## MCP tools (3)

### `get_quota` (~60 tokens)

Returns the application token account: accountName, accountPlan (e.g. free, developer, trial_developer, enterprise), allowedCredits and remainingCredits (monthly plus purchased pool). Requires Authorization: Bearer <application JWT> on the MCP HTTP request.

Output parameters:

- `accountName` (string)
- `accountPlan` (string)
- `allowedCredits` (number)
- `remainingCredits` (number)

### `list_sessions` (~591 tokens)

Lists stored sessions for the application token account: rtcstatsId, createdAt, sessionStart, sessionEnd, title, rtcstatsUrl, embedUrl (Enterprise only), and abstract (denormalized session summary: browser/os, observation types+tags, severity counts, score band). Optional filters: name (title substring, any of), observationTypes (exact type names, any of), observationTags (any of), os, browser, browserVersion, userId, conferenceId, sessionId, hasCritical/hasHigh/hasMedium, hasLowScore/hasMediumScore/hasHighScore. Different filters are AND-combined; multiple values within one filter are OR-combined. Example queries: sessions about "zoom" on Safari + macOS, sessions with network observation tags, sessions having critical observations, sessions with a low experience score. Requires Authorization: Bearer <application JWT> on the MCP HTTP request.

Input parameters:

- `browser` (string): Filter sessions by browser (e.g. "Chrome", "Safari", "Firefox", "Edge").
- `browserVersion` (string): Filter sessions by major browser version (e.g. "142").
- `conferenceId` (string): Filter sessions by the conference identifier carried in the rtcstats JWT (summary metadata conference).
- `hasCritical` (boolean): When true, only sessions with at least one critical-severity observation.
- `hasHigh` (boolean): When true, only sessions with at least one high-severity observation.
- `hasHighScore` (boolean): When true, only sessions whose experience score is high (>= 80).
- `hasLowScore` (boolean): When true, only sessions whose experience score is low (< 60).
- `hasMedium` (boolean): When true, only sessions with at least one medium-severity observation.
- `hasMediumScore` (boolean): When true, only sessions whose experience score is medium (60 to 79).
- `name` (array): Filter sessions whose title contains ANY of these substrings (case-insensitive). E.g. ["zoom"] for all sessions about Zoom.
- `observationTags` (array): Filter sessions whose observations carry ANY of these tags. Valid tags: connectivity, security, audio, video, datachannel, outbound, inbound, peripheral, behavior, network, configuration, cpu, bug.
- `observationTypes` (array): Filter sessions that contain ANY of these observation type strings (exact type name, e.g. ["turnNoConfig"]).
- `os` (string): Filter sessions by operating system (e.g. "macOS", "Windows", "Linux", "Android", "iPhone", "iPad").
- `sessionId` (string): Filter sessions by the session identifier carried in the rtcstats JWT (summary metadata session).
- `userId` (string): Filter sessions by the end-user identifier carried in the rtcstats JWT (summary metadata user).

Output parameters:

- `data` (array)
- `total` (number)

### `get_session` (~214 tokens)

Returns full session payload for one stored session (summary, observations, scores, etc.). Arguments: rtcstatsId (UUID). In data.observations[], each observation has type, severity, category, tags, firstSeenAt and a source object whose properties depend on the category: source.pid (peer connection id), source.sid (stream/datachannel report id), source.cpid (candidate-pair id), source.did (device entry id), source.rid (device row index), source.timestamp (device entry time), source.ssrcId (number, stream SSRC), source.labelId (device name). The top-level label is DEPRECATED and removed in the next schema version (overloaded legacy id; read source.ssrcId / source.sid / source.labelId instead). The full catalog of observation types (with possible severities and tags) is available from GET /v1.0/observations. Requires Authorization: Bearer <application JWT> on the MCP HTTP request.

Input parameters:

- `rtcstatsId` (string, required)

Output parameters:

- `data` (object)
- `embedUrl` (string)
- `processorVersion` (string)
- `rtcstatsId` (string)
- `rtcstatsUrl` (string)

## Diagnostics

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

## Score history

- 2026-08-07: 62
- 2026-08-06: 61
- 2026-08-05: 60
- 2026-08-04: 60

## Links

- Remote endpoint: https://api.rtcstats.com/v1.0/mcp
- Authorisation metadata: https://api.rtcstats.com/.well-known/oauth-protected-resource/v1.0/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-rtcstats-rtcstats/v1-0-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rtcstats-rtcstats/v1-0-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-rtcstats-rtcstats/v1-0-mcp