Level 1 measurement

What a server did at startup before any tool was used, and where its own README is silent about it. No tool is called, so nothing here tests whether a tool does what it says. Not calibration-backed. Not a ranking.

Get an alert when a measurement changes

A measurement is one run of one version on one date. The next version can do something different, and the page you read last month may no longer describe the package you are installing. Three ways to find out, none of which needs an account here.

Watch the repository

Every page is built from an evidence file in the public repository. Watching it — Custom → Releases, or the whole repository — tells you when any measurement lands, including a re-measurement of a package you care about. The diff shows exactly what changed, because the evidence is the file.

Ask to be told about one package

Open an alert request%0A%0AHow%20to%20reach%20you%3A%0A). You will be notified on that issue when the package is measured again, and the thread stays public so anyone can see what was said.

Or email contact@brydge-ai.com and say which package and what should trigger the message.

Re-run it yourself, on your own schedule

Nothing here is privileged. The harness is public and a measurement is one command:

git clone https://github.com/contactkontey-dotcom/brydge-mcp-measurements
cd brydge-mcp-measurements && node level1/run.ts <package>@<version>

If your run disagrees with a page here, that is a finding about us and we would like the issue.

All measurementsHow we measureRequest a measurementGet an alertPricingHarness and raw evidenceBRYDGE’s calibrated measurements

Report a mistake on this page →