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/wb04307201/methodtracelog/methodtracelog-mcpgit clone --depth 1 https://github.com/wb04307201/methodTraceLogWrote 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/wb04307201/methodtracelog/methodtracelog-mcp)<a href="https://agentmods.dev/mcp/wb04307201/methodtracelog/methodtracelog-mcp"><img src="https://agentmods.dev/badge/mcp/wb04307201/methodtracelog/methodtracelog-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
methodTraceLog-mcp 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
{
"methodTraceLog-mcp": {
"command": "jbang",
"args": [
"./methodTraceLog-mcp/target/methodTraceLog-mcp-1.0-SNAPSHOT.jar",
"--method-trace-log.mcp.hosts[0].name=local-dev",
"--method-trace-log.mcp.hosts[0].url=http://localhost:8085",
"--method-trace-log.mcp.hosts[0].description=本地开发",
"--method-trace-log.mcp.hosts[0].api-key=change-me-in-production"
]
}
}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 · 12 lines scan A ff29ebea0c94
methodTraceLog-mcp is an MCP server published in the GitHub repository wb04307201/methodTraceLog (47 stars, last pushed 6d ago), licensed Apache-2.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-30.
Other mcp servers, from other repositories
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
codeindex
MCP server "codeindex" as configured in GetKlai/klai. Launched with bash .claude/scripts/codeindex-mcp-launcher.sh.
dbgprobe-mcp-server
Debug probe Model Context Protocol server for AI agents and developer tooling. Runs locally from the dbgprobe-mcp-server Python package. Needs 9 environment variables to run.
repo-lens-mcp
MCP server for multi-repository AST-based symbol search and API route discovery. Runs locally from the repo-lens-mcp npm package.
broken-link-checker-mcp
MCP server "broken-link-checker-mcp" as configured in davinoishi/BLC-ground. Runs locally from the broken-link-checker-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.