Knot Verified / Observability and infra
Sentry
getsentry (GitHub) · remote
unverifiable, stale checked , version unknown
The server answered and requires sign-in. Checks past liveness need credentials, so it is unverifiable, not failed.
Checks
| Check | Result | Detail |
|---|---|---|
L0.reachable | pass | |
L0.tls | pass | |
L0.initialize | skipped | auth_required: Bearer realm="OAuth", resource_metadata="https://mcp.sentry.dev/.well-known/oauth-protected-resource/mcp" |
L0.protocol_version | skipped | |
L0.capabilities | skipped |
Numbers
| Uptime | 24h n/a (0) · 7d 100.0% (1) · 30d 100.0% (1) |
|---|---|
| Start latency | p50 196 ms · p95 196 ms |
| Call latency | p50 n/a · p95 n/a |
| Flakiness | n/a |
| Version drift | none seen |
Security facts
| Transport | streamable-http |
|---|---|
| Auth | oauth |
| TLS | TLSv1.3, certificate valid 51 more days |
| Capabilities | n/a |
| Tools | 0 read-only, 0 destructive, 0 unmarked |
| Credentials in URL | no |
Alongside
Not part of the verdict.
| None recorded. |
Badge
<a href="https://connectknot.com/verified/servers/sentry?utm_source=knot-verified&utm_medium=badge&utm_campaign=sentry"><img src="https://connectknot.com/verified/badge/sentry.svg" alt="Knot Verified: Sentry"></a>Source listing · Repository · JSON · Raw results, last 30 days
Request a re-run
Think a check is wrong? Tell us which one. We run the probe again and publish whatever it finds.