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.
npx agentmods add mcp/ringzero787/taxlocus-data/taxlocusgit clone --depth 1 https://github.com/Ringzero787/taxlocus-dataWrote 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/ringzero787/taxlocus-data/taxlocus)<a href="https://agentmods.dev/mcp/ringzero787/taxlocus-data/taxlocus"><img src="https://agentmods.dev/badge/mcp/ringzero787/taxlocus-data/taxlocus.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
taxlocus 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 3d 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.
The source is not reproduced here
Licensed CC-BY-4.0
The repository is licensed CC-BY-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 3d ago First seen · 6 lines scan A 3aee3f4cebf7
taxlocus is an MCP server published in the GitHub repository Ringzero787/taxlocus-data (1 stars, last pushed 9d ago), licensed CC-BY-4.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
chestnyznak
MCP server for Chestniy ZNAK — product marking verification, CRPT (Russia). Runs locally from the @theyahia/chestnyznak-mcp npm package.
evidence
Counter-signed evidence records for agent commerce: receipts, verification, dispute envelopes. Runs locally from the tersign npm package. Needs 7 environment variables to run.
hs-code-classifier-mcp-server
Classify products to official HS codes and validate supplier codes before customs submissions. Runs locally from the hs-code-classifier-mcp npm package. Needs 2 environment variables to run.
customs-mcp-server
MCP server exposing 14 customs / trade capabilities (declarations, ship info, tariff, dual-use screening, AI document maker, ...) as standard Model Context Protocol tools. Built for Claude Desktop / Claude Code / Cursor / Windsurf / Trae / Codex and any M. Runs locally from the @dearmrzhang/customs-mcp-server npm…
classification
Classify, validate & verify HS codes and access tariff compliance data for cross-border trade. Remote server at mcp.avalara.com.
cross-border
Cross-border duty-rate and Trade & Tariff content lookups with product compliance and restrictions. Remote server at mcp.avalara.com.