Vibeleaderboard
Index / tool
Visit github.com
Category
Cybersecurity
Rank
No. 2193Tools index

Previous survey · No. 2207 ·

Type
TOOL
Use case
Security & Identity
GitHub
2 stars
Date

About

MCP Transparency Log is an independent daily record of what public MCP servers actually served, kept as a signed Merkle log that had run for 37 days. Its argument is that publisher signing only proves who published something, not that a tool description is unchanged since an audit, so third-party observation without the server operator's cooperation is needed to detect silent changes.

At a glance

MCP Transparency Log records the tool names, descriptions and schemas that public MCP servers advertise. It is worth consulting when you want to know whether a server’s visible interface changed since you reviewed it.

Good fit

People evaluating an MCP server who need dated evidence of what its tools advertised.

Consider something else when

Use a separate runtime review if you need to know what tool calls actually do or whether an authenticated endpoint behaves the same way.

Start here

Find a server in the public census and compare two dated observations of one tool. Check a description or schema change against the current server before relying on it.

Cost and requirements

The public observations are available to browse. The project documents a Go verifier for checking published hashes and signed tree heads.

Limits to know

The crawler only sees reachable public interfaces at observation time. The log has a single operator and cannot establish what a server does during a real invocation.

Tags

mcptransparency-logmerkle-treesupply-chainmonitoringgo

Tech Stack

Go

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.