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/jagadeesh52423/graylog-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/jagadeesh52423/graylog-mcp/graylog-mcp-server)<a href="https://agentmods.dev/mcp/jagadeesh52423/graylog-mcp/graylog-mcp-server"><img src="https://agentmods.dev/badge/mcp/jagadeesh52423/graylog-mcp/graylog-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/jagadeesh52423/graylog-mcp/graylog-mcp-server"><img src="https://agentmods.dev/badge/mcp/jagadeesh52423/graylog-mcp/graylog-mcp-server.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
Grade A, and why
graylog-mcp-server 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
{ "graylog-mcp-server": { "command": "npx", "args": [ "-y", "graylog-mcp-server" ] } }
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 · 9 lines scan A b791d24223c7
graylog-mcp-server is an MCP server published in the GitHub repository jagadeesh52423/graylog-mcp (0 stars, last pushed 6d 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-10-29.
Other mcp servers, from other repositories
lynx
100% local MCP server for semantic + lexical code search: AST-aware chunking (tree-sitter), hybrid BM25+dense retrieval, optional code knowledge graph. Runs locally from the lynx-mcp Python package.
graylog-mcp
Query logs from Graylog: get streams, search messages, aggregate, and get full data. Runs locally from the @jperelli/graylog-mcp npm package. Needs 3 environment variables to run.
yokozuna-mcp
MCP server (stdio) wrapping the Sumo Logic Search Job API for agent-driven log triage. Runs locally from the yokozuna-mcp npm package.
codebrain
Know what breaks before you break it. Structural knowledge graph for codebases — impact analysis, dead code detection, health scores. No LLM required. Runs locally from the codebrain Python package.
chromedevtoolsmcp-mcp
A paid remote MCP for AI agent browser DevTools MCP, built to return verdicts, receipts, usage logs. Remote server at chromedevtoolsmcp.clauxel.com.
gdb-mcp
Model Context Protocol server for driving GDB from an LLM. Runs locally from the gdb-mcp Python package.