SaSame MCP Observatory — Certified (continuously monitored MCP servers)

Level 3 of the readiness ladder. Observed (we measured it from outside) → Claimed (the owner proved control) → Certified (SaSame continuously re-audits the claimed endpoint via a reproducible test).

What “Certified” means here (and what it does not):
• The endpoint is claimed — the owner proved control.
• SaSame has re-audited it on ≥ 2 reproducible cycles and it still clears the A/B bar. We do not call anything “continuously monitored” until it literally is.
• The signed certificate is auto-renewed every cycle (14-day validity) only while the bar holds. Drop below B and certified status is withdrawn that same cycle — see grade changes.
• self_owned rows are SaSame’s own servers, shown for transparency and never counted as third-party traction.

How to get your server Certified (free, no application):
• Claim your endpoint → (one click; prove control via .well-known / DNS / repo).
• SaSame re-audits every 6h — after ≥ 2 reproducible cycles still at the A/B bar, your server is auto-promoted here.
• See the A/B criteria · correct / delist any time.

Certified servers

Server	Grade	Passes	Cycles	Since	Cert
live-vps.sasame.online (SaSame own)	A	10/10	11	2026-06-18	signed cert

Grade changes / drops (claimed servers only)

Server	Change	Last checked
No grade drops among monitored servers.

Certified is the only rung where SaSame asserts ongoing responsibility, so it is granted sparingly and revoked automatically. Re-audit cadence: every 6h. Verify any cert offline with the issuer pubkey (302a300506032b6570032100...). Generated 2026-06-18T18:48:15.747Z.