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/LumiRx/num-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/lumirx/num-mcp/num)<a href="https://agentmods.dev/mcp/lumirx/num-mcp/num"><img src="https://agentmods.dev/badge/mcp/lumirx/num-mcp/num/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/lumirx/num-mcp/num"><img src="https://agentmods.dev/badge/mcp/lumirx/num-mcp/num.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
num 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
{
"num": {
"url": "https://itsnum.com/mcp",
"type": "streamable-http"
}
}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 afbf608015eb
num is an MCP server published in the GitHub repository LumiRx/num-mcp (0 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
vibeseo
SEO research, keyword discovery, site audits, Search Console, backlinks and content workflow. Remote server at mcp.vibeseo.dev.
betterstack
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents. Remote server at betterstack.usefulapi.io.
dropbox-sign
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents. Remote server at dropbox-sign.usefulapi.io.
emailoctopus
Manage lists, contacts and campaigns, and read campaign performance reports on EmailOctopus. Remote server at emailoctopus.usefulapi.io.
healthchecksio
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io. Remote server at healthchecksio.usefulapi.io.
lambda-labs
Read GPU instances, types, images, filesystems and firewall rules; launch and terminate instances. Remote server at lambda-labs.usefulapi.io.