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/EtienneBBeaulac/workrailWrote 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/etiennebbeaulac/workrail/workrail-dev)<a href="https://agentmods.dev/mcp/etiennebbeaulac/workrail/workrail-dev"><img src="https://agentmods.dev/badge/mcp/etiennebbeaulac/workrail/workrail-dev/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/etiennebbeaulac/workrail/workrail-dev"><img src="https://agentmods.dev/badge/mcp/etiennebbeaulac/workrail/workrail-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
workrail-dev 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 1mo 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
{
"workrail-dev": {
"type": "http",
"url": "http://localhost:3100/mcp"
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 6 lines scan A ddcfffb59237
workrail-dev is an MCP server published in the GitHub repository EtienneBBeaulac/workrail (4 stars, last pushed 5d 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
sui-mcp
Read-only Sui blockchain analytics: 61 tools, protocol-aware tx decoding, no API keys or wallet. Runs locally from the sui-analytics-mcp npm package. Needs 6 environment variables to run.
reportflow-mcp
Generate PDF reports from Re:port Flow templates via Claude and other AI agents. Runs locally from the reportflow-mcp npm package. Needs 4 environment variables to run.
n8n-ops-mcp
n8nctrl operator control CLI for n8n workflow ops, with MCP and OpenClaw adapters for agents. Runs locally from the n8n-ops-mcp npm package.
opdstar-nhi
The MCP server for Taiwan NHI billing intelligence — rejection codes, audit clauses, drug payment rules, fee schedule, special materials, and appeal case precedents. Helps AI agents answer Taiwan health-insurance billing and audit questions with authorita. Runs locally from the @opdstar/nhi-mcp npm package.
twitterapi-io-mcp-server
Official MCP server for twitterapi.io — Twitter/X data (tweets, users, followers, trends). Runs locally from the @kaitoinfra/twitterapi-io-mcp-server npm package. Needs 1 environment variable to run.
opm-mcp
MCP server "opm-mcp" as configured in ojaogezi/opm-mcp. Launched with opm-mcp.