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/FrancoisChastel/sydonia-toolkitWrote 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/francoischastel/sydonia-toolkit/customs-query-tester)<a href="https://agentmods.dev/mcp/francoischastel/sydonia-toolkit/customs-query-tester"><img src="https://agentmods.dev/badge/mcp/francoischastel/sydonia-toolkit/customs-query-tester/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/francoischastel/sydonia-toolkit/customs-query-tester"><img src="https://agentmods.dev/badge/mcp/francoischastel/sydonia-toolkit/customs-query-tester.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
customs-query-tester 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 12d 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 AGPL-3.0
The repository is licensed AGPL-3.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.
- 12d ago First seen · 13 lines scan A 4f75eb8263d6
customs-query-tester is an MCP server published in the GitHub repository FrancoisChastel/sydonia-toolkit (2 stars, last pushed 1mo ago), licensed AGPL-3.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
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.
douanecode-mcp
MCP server exposing DouaneCode customs code search (HS/NC8/TARIC) to AI agents. Runs locally from the douanecode-mcp Python package. Needs 1 environment variable 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…
tariff-resolver
MCP server "tariff-resolver" as configured in opsloft/tariff-resolver. Runs dist/index.js with node.
mcp-comex-brasil
MCP server "mcp-comex-brasil" as configured in PHIAI-IO/mcp-comex-brasil. Runs locally from the mcp-comex-brasil npm package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.