rtcStats
REMOTE · API.RTCSTATS.COM
Query analyzed WebRTC sessions: observations, deductions, experience scores, and AI summaries.
Available components
Last scanned (20 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Monitoring and Observability
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Server version: 1.9.2 → 1.10.0 functional
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Server version: 1.9.1 → 1.9.2 functional
- 28 Aug 26 0
- Server version: 1.9.0 → 1.9.1 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 21 Nov 2026 · Probed https://api.rtcstats.com/v1.0/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.rtcstats.com | CN=YR1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 54052717561b031b25f1a586c5431f29523 |
| SANs: api.rtcstats.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.rtcstats.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| rtcstats.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="rtcstats"
Bearer realm="rtcstats" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=() |
| www-authenticate | Bearer realm="rtcstats" |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.rtcstats.com/v1.0/mcp | Auth required | 401 | |
| http (plaintext) | http://api.rtcstats.com/v1.0/mcp | HTTPS enforced | 308 | https://api.rtcstats.com/v1.0/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 →
get_quota ~60
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| accountName | string | yes | – |
| accountPlan | string | yes | – |
| allowedCredits | number | yes | – |
| remainingCredits | number | yes | – |
No examples provided.
get_session ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| rtcstatsId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| embedUrl | string | – | – |
| processorVersion | string | yes | – |
| rtcstatsId | string | yes | – |
| rtcstatsUrl | string | yes | – |
No examples provided.
list_sessions ~591
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| total | number | yes | – |
No examples provided.
How do I install the rtcStats MCP server?
rtcStats is a hosted endpoint at https://api.rtcstats.com/v1.0/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 · api.rtcstats.com
claude mcp add --transport http com-rtcstats-rtcstats 'https://api.rtcstats.com/v1.0/mcp'
What is the rtcStats MCP server?
rtcStats is an MCP server listed in the public MCP registry as com.rtcstats/rtcstats. Query analyzed WebRTC sessions: observations, deductions, experience scores, and AI summaries. This page covers its hosted endpoint (https://api.rtcstats.com/v1.0/mcp).
Is the rtcStats MCP server safe to use?
rtcStats scores 36 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 rtcStats MCP server expose?
rtcStats exposes 3 tools: get_quota, list_sessions, get_session. Their descriptions and schemas cost roughly 865 tokens of context every time the server is loaded.
Does the rtcStats MCP server require authentication?
Yes. rtcStats asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the rtcStats MCP server still maintained?
rtcStats is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the rtcStats MCP server?
VerifyMCP ran 5 checks on rtcStats, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about rtcStats: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.