Throne Registry | Public MCP trust records
Skip to records
See report<br>Verify server
throne registry
The public record for MCP servers.
Every record says what was executed, how it behaved across real clients, what security found, and the evidence hash that sealed it.
live from /api/stats
run75 servers executedall time
ok31 fitready records
key23 needs keyaction required
!today latest seallive registry
search records
Verdict: All<br>Fit<br>Needs key<br>Inconclusive<br>Not fit
75 sealed records
server<br>verdict<br>security<br>sealed at<br>evidence hash
exa-mcp-servernpmpublic package executed by Throne<br>FIT<br>security: clean<br>today<br>sha256:9f3c2b7e...
tavily-mcpnpmpublic package executed by Throne<br>FIT<br>security: clean<br>today<br>sha256:2a7d4e91...
@notionhq/notion-mcp-servernpmpublic package executed by Throne<br>FIT<br>security: clean<br>today<br>sha256:6f1b03af...
enable javascript to browse live registry records.
View more records
Showing public evidence records. Click any server to inspect the proof.
why this wins trust
Public evidence changes how MCP servers get adopted.
share<br>Maintainers can prove compatibility
A fit record becomes a link for README, launch notes, procurement packets, and users who ask if the server actually works.
approve<br>Companies can approve by record
Security can create allowlists from evidence instead of screenshots, demos, or vendor promises.
detect<br>Regressions become visible
When a package update or client release breaks behavior, the record changes and the CI gate blocks the release.
Put your server on the record.
Verify server
github url / npm package / uvx package / json config
hello@usethrone.dev<br>© 2026 throne / Privacy / Terms / Company