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/peopleworks/XAFLogicExplainerWrote 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/peopleworks/xaflogicexplainer/mcp-xaf-logic-explainer)<a href="https://agentmods.dev/mcp/peopleworks/xaflogicexplainer/mcp-xaf-logic-explainer"><img src="https://agentmods.dev/badge/mcp/peopleworks/xaflogicexplainer/mcp-xaf-logic-explainer/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/peopleworks/xaflogicexplainer/mcp-xaf-logic-explainer"><img src="https://agentmods.dev/badge/mcp/peopleworks/xaflogicexplainer/mcp-xaf-logic-explainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
xaf-logic-explainer 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 10d 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
{
"xaf-logic-explainer": {
"command": "XafLogicExplainer.Mcp",
"args": [],
"env": {
"XAFLOGIC_PROJECT": ""
}
}
}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.
- 10d ago First seen · 9 lines scan A 82b85a75ab8a
xaf-logic-explainer is an MCP server published in the GitHub repository peopleworks/XAFLogicExplainer (9 stars, last pushed 2d 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
sharplens
67 semantic C#/.NET analysis tools via Roslyn: navigation, refactoring, codegen, audit. Runs locally from the sharplens-mcp npm package. Needs 3 environment variables to run.
aspnetcore-debugger-mcp
MCP server "aspnetcore-debugger-mcp" as configured in magna-nz/aspnetcore-debugger-mcp. Launched with AspNetCoreDebuggerMcp.
roseline-mcp
MCP server "roseline-mcp" as configured in Atypical-Consulting/RoselineMCP. Launched with RoselineMCP.
dotnet-coverage-mcp
MCP server "dotnet-coverage-mcp" as configured in Hyeonu-Cha/dotnet-coverage-mcp. Launched with dotnet-coverage-mcp. Needs 2 environment variables to run.
resharper-cli-mcp
MCP server "resharper-cli-mcp" as configured in andypgray/resharper-cli-mcp. Launched with Zphil.ReSharperCli. Needs 9 environment variables to run.
nxopen-mcp
MCP server that gives AI coding agents accurate NXOpen .NET API knowledge via hybrid retrieval. Runs locally from the nxopen-mcp Python package.