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/hishamalward/mcpclerkWrote 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/hishamalward/mcpclerk/fs-governed)<a href="https://agentmods.dev/mcp/hishamalward/mcpclerk/fs-governed"><img src="https://agentmods.dev/badge/mcp/hishamalward/mcpclerk/fs-governed/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/hishamalward/mcpclerk/fs-governed"><img src="https://agentmods.dev/badge/mcp/hishamalward/mcpclerk/fs-governed.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fs-governed 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
{
"fs-governed": {
"command": "mcpclerk",
"args": [
"serve",
"--policy",
"examples/policy.filesystem.yaml",
"--log",
"audit/mcpclerk.jsonl",
"--approvals",
"approvals"
]
}
}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 · 14 lines scan A 39ef9503ff2f
fs-governed is an MCP server published in the GitHub repository hishamalward/mcpclerk (0 stars, last pushed 18d 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
mcp-guarded-tools
MCP server "mcp-guarded-tools" as configured in ridwanspace/mcp-guarded-tools. Runs locally from the mcp-guarded-tools npm package.
elicitly-free-dev
MCP server "elicitly-free-dev" as configured in elicitly/elicitly. Runs packages/elicitly/dist/cli.mjs with node.
elicitly-free
Local (stdio) MCP server that gives your prompts and Agent Skills MCP elicitation — human-in-the-loop dialogs (elicitconfirm, elicitform) and the elicitdoctor capability report, with no server of your own. Runs locally from the elicitly npm package.
agent-gate
An MCP server that lets an AI agent gate its own work: deterministic checks, refute-first review, and tamper-evident honest receipts. Fleet Mode, as a tool. Runs locally from the mcp-agent-gate Python package.
agentrisk
MCP server "agentrisk" as configured in trycoin-ai/agentrisk. Runs locally from the agentrisk[mcp] Python package.
epacomp-tox-mcp
MCP server "epacomp-tox-mcp" as configured in ToxMCP/comptox-mcp. Runs locally from the epacomp-tox-mcp Python package.