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/fainir/niceWrote 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/fainir/nice/nice-hub)<a href="https://agentmods.dev/mcp/fainir/nice/nice-hub"><img src="https://agentmods.dev/badge/mcp/fainir/nice/nice-hub/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/fainir/nice/nice-hub"><img src="https://agentmods.dev/badge/mcp/fainir/nice/nice-hub.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nice-hub 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
{ "nice-hub": { "command": "npx", "args": [ "-y", "nice-hub" ] } }
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 · 9 lines scan A 05b07734cea5
nice-hub is an MCP server published in the GitHub repository fainir/nice (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
trusty-squire
Trusty Squire signs up / in to websites for you so you don’t have to. Runs locally from the @trusty-squire/mcp npm package.
mcp
Credential broker that signs your AI agent up to SaaS dev tools, within a signed spending mandate. Runs locally from the @trusty-squire/mcp npm package.
treg
MCP server "treg", hosted remotely at treg.to, as configured in superdesigndev/treg.
phantom-secrets-mcp
Stop AI coding agents from leaking API keys. Local proxy swaps real secrets for phm tokens. Runs locally from the phantom-secrets-mcp npm package.
mcp-stdio
Stdio-to-HTTP gateway — connects MCP clients to remote HTTP MCP servers. Runs locally from the mcp-stdio Python package.
db-mcp
SQLite MCP server with OAuth 2.1, HTTP/SSE, 122 tools, and smart tool filtering. Runs locally from the db-mcp npm package.