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/Verifa-Solutions/verifa-mcp-serverWrote 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/verifa-solutions/verifa-mcp-server/verifa)<a href="https://agentmods.dev/mcp/verifa-solutions/verifa-mcp-server/verifa"><img src="https://agentmods.dev/badge/mcp/verifa-solutions/verifa-mcp-server/verifa/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/verifa-solutions/verifa-mcp-server/verifa"><img src="https://agentmods.dev/badge/mcp/verifa-solutions/verifa-mcp-server/verifa.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
verifa 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
{
"verifa": {
"command": "npx",
"args": [
"-y",
"@verifasolutionsinc/mcp-server"
],
"env": {
"VERIFA_API_KEY": "",
"VERIFA_ENV": ""
}
}
}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 · 13 lines scan A 256f4c242767
verifa is an MCP server published in the GitHub repository Verifa-Solutions/verifa-mcp-server (0 stars, last pushed 8d 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
sanctionwise
Verified UK sanctions screening for AI agents — official FCDO UK Sanctions List, not guesses. Runs locally from the sanctionwise npm package.
companieswise
Verified UK company lookup & validation for AI agents — Companies House data, snapshot or live. Runs locally from the companieswise npm package.
taiwan-legal-db
MCP server "taiwan-legal-db" as configured in lawchat-oss/mcp-taiwan-legal-db. Runs mcp_server.server with .venv/bin/python.
regulations-gov-mcp
MCP server for the Regulations.gov API. Federal rulemaking dockets, documents, comments, and comment period tracking. Runs locally from the regulationsgov-mcp Python package. Needs 1 environment variable to run.
dd
Czech & EU due diligence in one call — facts, insolvency, sanctions, VAT, risk score, UBO chain. Runs locally from the @czagents/dd npm package.
eu-registry
EU company registry lookup across 16 countries incl. Sweden Bolagsverket. Runs locally from the @czagents/eu-registry npm package.