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/mfreeman451/json-logs-mcp-server/json-logsgit clone --depth 1 https://github.com/mfreeman451/json-logs-mcp-serverWrote 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/mfreeman451/json-logs-mcp-server/json-logs)<a href="https://agentmods.dev/mcp/mfreeman451/json-logs-mcp-server/json-logs"><img src="https://agentmods.dev/badge/mcp/mfreeman451/json-logs-mcp-server/json-logs.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
json-logs 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.
The source is not reproduced here
Licensed MIT-0
The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 9 lines scan A 6f9080f28ca0
json-logs is an MCP server published in the GitHub repository mfreeman451/json-logs-mcp-server (4 stars, last pushed 1y ago), licensed MIT-0. 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
mcp-victorialogs
MCP server "mcp-victorialogs" as configured in VictoriaMetrics/mcp-victorialogs. Runs in Docker (ghcr.io/victoriametrics/mcp-victorialogs:1.9.0). Needs 3 environment variables to run.
json-yaml-toml
MCP server for querying and modifying JSON, YAML, and TOML files using yq. Runs locally from the mcp-json-yaml-toml Python package.
reapfield
MCP server "reapfield" as configured in PedroHenriqueNS/reapfield. Runs locally from the reapfield Python package.
json
MCP server "json", hosted remotely at gateway.pipeworx.io, as configured in pipeworx-io/mcp-json.
mcp-prose-memory
MCP server for persistent memory with JSON storage and atomic fact operations. Runs locally from the mcp-prose-memory npm package.
prism
MCP server "prism" as configured in tools-for-agents/prism. Runs locally from the @tools-for-agents/prism npm package.