Repository navigation
Conversation
Adds MCP Transparency Log to the Other section, in alphabetical order (between MCP Server for MCP Registry and MCP Verify).
a-akimov
approved these changes
Nov 19, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
Adds MCP Transparency Log to the Other section, in alphabetical order (between MCP Server for MCP Registry and MCP Verify).
It is an independent, nightly record of the tool surface every remote endpoint in the official registry actually served (tool names, descriptions, input schemas), kept since 2026-08-30 in an append-only RFC 6962 Merkle log with signed tree heads and published leaf hashes, so any figure can be recomputed from a clean clone. The site gives every server a history page and two badges, publishes a nightly cross-check list in the jcs-v1 digest format other observers use, and ships
mcp.lockwith a GitHub Action that fails CI when a pinned server's tools change. It readstools/listonly, never calls a tool, and grades nothing.Its endpoint measurements were consolidated as evidence under #1715 (from #1626). I maintain it.
How Has This Been Tested?
Documentation only. Checked that the link loads and that the entry follows the one-line format of the list.