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/TAG-IT-NETWORK/tagit-dashboardWrote 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/tag-it-network/tagit-dashboard/verify-nfc-verify)<a href="https://agentmods.dev/mcp/tag-it-network/tagit-dashboard/verify-nfc-verify"><img src="https://agentmods.dev/badge/mcp/tag-it-network/tagit-dashboard/verify-nfc-verify/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/tag-it-network/tagit-dashboard/verify-nfc-verify"><img src="https://agentmods.dev/badge/mcp/tag-it-network/tagit-dashboard/verify-nfc-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
nfc-verify 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
{
"nfc-verify": {
"url": "https://verify.tagit.network/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.
- 8d ago First seen · 6 lines scan A 0f9a6288ed51
nfc-verify is an MCP server published in the GitHub repository TAG-IT-NETWORK/tagit-dashboard (0 stars, last pushed yesterday), licensed Apache-2.0. 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
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
react-profiler-mcp
MCP server "react-profiler-mcp" as configured in UmarHassanKhan929/react-profiler-mcp. Runs locally from the react-profiler-mcp npm package.
clerk
MCP server "clerk", hosted remotely at mcp.clerk.com, as configured in FloB95/qrcodly.
storybook-mcp
MCP server "storybook-mcp", hosted remotely at localhost, as configured in yannbf/mealdrop.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.