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.
git clone --depth 1 https://github.com/gerardjlynn/gnomonWrote 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/gerardjlynn/gnomon/gnomon)<a href="https://agentmods.dev/mcp/gerardjlynn/gnomon/gnomon"><img src="https://agentmods.dev/badge/mcp/gerardjlynn/gnomon/gnomon.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
gnomon 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 6d 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
{
"gnomon": {
"command": "npx",
"args": [
"tsx",
"mcp/server.ts",
"--vault",
"gnomon=vault"
]
}
}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.
- 6d ago First seen · 11 lines scan A eb5879e12d24
gnomon is an MCP server published in the GitHub repository gerardjlynn/gnomon (0 stars, last pushed 2mo 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
callspec
Stop duct-taping your API stack. One TypeScript route → typed SDK, docs, OpenAPI, and MCP. Runs locally from the callspec npm package.
mcp-server-template
Production-grade MCP Server Template for TypeScript and Node.js. Runs locally from the @qmmughal/mcp-server-template npm package.
ts-graph
MCP server "ts-graph" as configured in couzic/ts-graph-mcp. Runs dist/main.js with node.
imo-rules
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
project-manager
TypeScript Execute (tsx): Node.js enhanced with esbuild to run TypeScript & ESM files. Runs locally from the tsx npm package.
vdiff-mcp
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. Runs locally from the vdiff-mcp npm package. Needs 1 environment variable to run.