Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/beeswaxpat/chronoverify-mcp/chronoverifygit clone --depth 1 https://github.com/beeswaxpat/chronoverify-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/beeswaxpat/chronoverify-mcp/chronoverify)<a href="https://agentmods.dev/mcp/beeswaxpat/chronoverify-mcp/chronoverify"><img src="https://agentmods.dev/badge/mcp/beeswaxpat/chronoverify-mcp/chronoverify.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
chronoverify scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"chronoverify": {
"command": "npx",
"args": [
"-y",
"chronoverify-mcp"
],
"env": {
"CHRONOVERIFY_API_KEY": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 12 lines scan A 729e139b8ef8
chronoverify is an MCP server published in the GitHub repository beeswaxpat/chronoverify-mcp (2 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
c2pa-mcp
An open-source MCP server that verifies C2PA content credentials and returns LLM-ready provenance verdicts. Built by c2paviewer.com. Runs locally from the @c2paviewer/c2pa-mcp npm package.
mtl-c2pa-mcp
MCP server "mtl-c2pa-mcp" as configured in musictechlab/mtl-c2pa-mcp. Runs locally from the mtl-c2pa-mcp Python package.
orphograph
MCP server "orphograph" as configured in Orphograph/Orphograph. Launched with https://github.com/Orphograph/Orphograph/releases/download/mcp-v0.1.1/orphograph. Needs 2 environment variables to run.
photo-s
批量照片处理工具箱：压缩/转换/调色/EXIF/RAW/去重/选片/REST+MCP — Batch photo toolkit: compress, convert, grade, EXIF, RAW, dedup, cull (CLI + GUI + REST + MCP). Runs locally from the photo-s-tools Python package.
is-it-ai-mcp
MCP server that reads C2PA Content Credentials: what an image declares about its own origin, and whether that declaration still verifies. Runs locally from the is-it-ai-mcp Python package.
groupdocs-metadata-mcp
MCP server "groupdocs-metadata-mcp" as configured in groupdocs-metadata/GroupDocs.Metadata.Mcp. Launched with GroupDocs.Metadata.Mcp. Needs 3 environment variables to run.