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/NoBanks/housecallpro-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/nobanks/housecallpro-mcp/housecallpro)<a href="https://agentmods.dev/mcp/nobanks/housecallpro-mcp/housecallpro"><img src="https://agentmods.dev/badge/mcp/nobanks/housecallpro-mcp/housecallpro/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/nobanks/housecallpro-mcp/housecallpro"><img src="https://agentmods.dev/badge/mcp/nobanks/housecallpro-mcp/housecallpro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
housecallpro 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 8d 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
{
"housecallpro": {
"command": "housecallpro-mcp",
"env": {
"HOUSECALLPRO_API_KEY": "your-housecallpro-api-key",
"HOUSECALLPRO_ALLOW_INVOICE": "false"
}
}
}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.
- 8d ago First seen · 9 lines scan A a43b1c748d21
housecallpro is an MCP server published in the GitHub repository NoBanks/housecallpro-mcp (0 stars, last pushed 3mo 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
jobber-mcp
Read the Jobber Client Hub your service providers share: appointments, invoices and quotes. Runs locally from the @chrischall/jobber-mcp npm package.
harvest
Read time entries, projects, clients, tasks and invoices; log and update tracked time. Remote server at harvest.usefulapi.io.
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.
jobkeepr
Manage jobs, customers, scheduling, estimates and invoices for a field service business. Remote server at jobkeepr.com.
connectwise-mcp
ConnectWise Manage MCP server — 45 tools for tickets, projects, agreements, companies, and finance. Runs locally from the connectwise-mcp Python package.
isp2go
ISP2Go CLI — ISP management for coding agents. Customers, billing, networking, tickets. As easy as git. Runs locally from the isp2go npm package. Needs 1 environment variable to run.