Brivvy MCP (OAuth): on-brand AI content, voice rules, templates, glossary.
Communicationv0.1.0streamable-httpmcp.brivvy.io repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 18 / 25 | HTTP 401 in 348ms — auth required; WWW-Authenticate present: "Bearer resource_metadata="https://mcp.brivvy.io/.well-known/oauth-protected-resource"" |
| protocol | 0 / 15 | handshake not reachable behind auth — unverified |
| tooling | 0 / 0 | auth-gated — tooling unverifiable, excluded from score (grade marked provisional) |
| latency | 10 / 10 | initialize round-trip 348ms |
| provenance | 15 / 15 | description present; repository linked; version 0.1.0; namespace io.github.brivvyHQ matches endpoint/repo |
Score 66/100 · latency 348ms · — tools · protocol access: auth-wellbehaved ⓘ
Security, data integrity, citation quality, and advertised claims are measured separately from protocol uptime. Missing evidence is marked unverified, never converted into a pass.
| Dimension | Metric | Status | Evidence | Source |
|---|---|---|---|---|
| security | authentication_boundary | observed | Live protocol probe observed auth_state=auth-wellbehaved. This describes discovery/access behavior; it is not by itself a vulnerability finding. Observed value: auth-wellbehaved | live_probe |
Machine-readable receipt: /api/trust/io.github.brivvyHQ/mcp.json
Live operational-grade badge, re-probed continuously — not a security or data-quality certification. Put it in your README and link to the complete receipt:
[](https://mcpqueen.com/s/io.github.brivvyHQ/mcp)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-16 22:15 | C | 66 | 348ms |
| 2026-07-13 22:15 | D | 57 | 1680ms |