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/freshworks-developers/fw-dev-toolsWrote 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/freshworks-developers/fw-dev-tools/fw-dev-mcp)<a href="https://agentmods.dev/mcp/freshworks-developers/fw-dev-tools/fw-dev-mcp"><img src="https://agentmods.dev/badge/mcp/freshworks-developers/fw-dev-tools/fw-dev-mcp/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/freshworks-developers/fw-dev-tools/fw-dev-mcp"><img src="https://agentmods.dev/badge/mcp/freshworks-developers/fw-dev-tools/fw-dev-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
fw-dev-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 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
{
"fw-dev-mcp": {
"url": "https://mcp.freshworks.dev/mcp",
"headers": {
"Authorization": "Bearer ${user_config.mcp_auth_token}"
}
}
}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 · 8 lines scan A bfc074bb0843
fw-dev-mcp is an MCP server published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 1mo 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
skillsmith
Publish versioned agent skills to a team-scoped registry, track drift, and deprecate stale ones. Runs locally from the @skillsmith/mcp-server npm package.
skillsmith
MCP server "skillsmith" as configured in smith-horn/skillsmith. Launched with ./scripts/mcp-skillsmith-launcher.sh.
skillsmith-doc-retrieval
MCP server "skillsmith-doc-retrieval" as configured in smith-horn/skillsmith. Launched with ./scripts/mcp-doc-retrieval-launcher.sh.
ruflo
MCP server "ruflo" as configured in smith-horn/skillsmith. Launched with ./scripts/mcp-ruflo-launcher.sh.
langsmith
MCP server "langsmith" as configured in latestaiagents/agent-skills. Runs locally from the @anthropic/mcp-langsmith npm package. Needs 3 environment variables to run.
redis
MCP server "redis" as configured in latestaiagents/agent-skills. Runs locally from the @anthropic/mcp-redis npm package. Needs 1 environment variable to run.