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/eranfinish/ezatwork-mcpWrote 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/eranfinish/ezatwork-mcp/ezatwork)<a href="https://agentmods.dev/mcp/eranfinish/ezatwork-mcp/ezatwork"><img src="https://agentmods.dev/badge/mcp/eranfinish/ezatwork-mcp/ezatwork/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/eranfinish/ezatwork-mcp/ezatwork"><img src="https://agentmods.dev/badge/mcp/eranfinish/ezatwork-mcp/ezatwork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ezatwork 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 6 lines scan A f5cfb7a24c18
ezatwork is an MCP server published in the GitHub repository eranfinish/ezatwork-mcp (0 stars, last pushed 2mo ago), with no licence file. 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
freelancer-payment-protection
Command-line client for freelancer-payment-protection: automated invoice escalation, legal document generation, and client risk scoring for freelancers. Runs locally from the freelancer-payment-protection-cli Python package.
investor-relations-mcp
MCP server "investor-relations-mcp" as configured in adelaidasofia/investor-relations-mcp. Launched with https://github.com/adelaidasofia/investor-relations-mcp/releases/download/v0.1.0. Needs 1 environment variable to run.
autorev-mcp
MCP server for AutoRev AI. Run your field service business from Claude: answer calls, book and dispatch jobs, build estimates, chase invoices. Built for HVAC, plumbing, electrical, roofing and pest control. Runs locally from the @autorevai/mcp-server npm package.
peil-mcp
MCP server for Peil — log hours, draft invoices and check where you stand from an AI assistant. Runs locally from the peil-mcp Python package. Needs 2 environment variables to run.
chasa
AI invoice follow-up emails for freelancers. Draft-only, never sends for you. Remote server at api.chasa.io.
withmoxie-mcp-server
MCP server for Moxie CRM integration - manage clients, contacts, projects, invoices, time tracking, and more. Runs locally from the withmoxie-mcp-server npm package.