Hi maintainers,
We recently added Model Context Protocol (MCP) to HVTracker, where we independently track public trust and maintenance signals for open-source AI agent projects. Your live profile is here:
Why this might be useful
HVTracker monitors signals that matter for supply-chain safety — signed commits, provenance visibility, license compliance, dependency freshness, maintenance cadence, and more. Having this information surfaced in one place helps contributors and downstream users make faster trust decisions about the tools they depend on.
Adding the badge to your README gives users an independent, at-a-glance view of the project's safety posture — and clicking through lets them inspect the full breakdown. It also helps surface areas where safety signals could be strengthened (e.g., enabling commit signing, adding a SECURITY.md, improving provenance metadata).
Early adopters
Projects like Haystack by deepset have already adopted HVTracker badges in their README, and others like AIPass are in the process of adding them. As more projects participate, the ecosystem gets a shared, transparent baseline for trust.
Badge snippets (ready to use)
[](https://hvtracker.net/agents/model-context-protocol-mcp/)
[](https://hvtracker.net/agents/model-context-protocol-mcp/)
The badges are dynamically generated and always reflect the latest public data — no manual updates needed.
No pressure
Totally fine to close this if it's not the right time. We just wanted to make sure the option was on your radar. If anything on the Model Context Protocol (MCP) profile page looks inaccurate, we're happy to correct it — just let us know.
Thanks for building in the open!
Hi maintainers,
We recently added Model Context Protocol (MCP) to HVTracker, where we independently track public trust and maintenance signals for open-source AI agent projects. Your live profile is here:
Why this might be useful
HVTracker monitors signals that matter for supply-chain safety — signed commits, provenance visibility, license compliance, dependency freshness, maintenance cadence, and more. Having this information surfaced in one place helps contributors and downstream users make faster trust decisions about the tools they depend on.
Adding the badge to your README gives users an independent, at-a-glance view of the project's safety posture — and clicking through lets them inspect the full breakdown. It also helps surface areas where safety signals could be strengthened (e.g., enabling commit signing, adding a SECURITY.md, improving provenance metadata).
Early adopters
Projects like Haystack by deepset have already adopted HVTracker badges in their README, and others like AIPass are in the process of adding them. As more projects participate, the ecosystem gets a shared, transparent baseline for trust.
Badge snippets (ready to use)
The badges are dynamically generated and always reflect the latest public data — no manual updates needed.
No pressure
Totally fine to close this if it's not the right time. We just wanted to make sure the option was on your radar. If anything on the Model Context Protocol (MCP) profile page looks inaccurate, we're happy to correct it — just let us know.
Thanks for building in the open!