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/lacausecrypto/mcp-belgiumWrote 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/lacausecrypto/mcp-belgium/mcp-belgium-mcp-belgium)<a href="https://agentmods.dev/mcp/lacausecrypto/mcp-belgium/mcp-belgium-mcp-belgium"><img src="https://agentmods.dev/badge/mcp/lacausecrypto/mcp-belgium/mcp-belgium-mcp-belgium/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/lacausecrypto/mcp-belgium/mcp-belgium-mcp-belgium"><img src="https://agentmods.dev/badge/mcp/lacausecrypto/mcp-belgium/mcp-belgium-mcp-belgium.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-belgium 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.
What it actually says
{
"mcp-belgium": {
"command": "npx",
"args": [
"-y",
"mcp-belgium"
],
"env": {
"STIB_API_KEY": "",
"CBEAPI_KEY": ""
}
}
}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 acfb366a8c88
mcp-belgium is an MCP server published in the GitHub repository lacausecrypto/mcp-belgium (5 stars, last pushed 2mo 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
infranode
Keyless open data for 84 German cities: 12 lean read-only MCP tools covering 67 data types. Remote server at mcp.infranode.dev.
ph-civic-data-mcp
MCP server for Philippine civic data: the full PSA OpenSTAT statistical catalog, PSGC locations, infra spending accountability, PSA economy (inflation, labor, poverty, population), one-call area profiles, earthquakes, weather, typhoons, procurement, solar/climate, air quality, vegetation. Runs locally from the…
swiss-transport
MCP server "swiss-transport" as configured in malkreide/swiss-transport-mcp. Launched with swiss-transport-mcp. Needs 1 environment variable to run.
swiss-transport-mcp
MCP server for Swiss public transport – OJP journey planner, real-time departures, disruptions, occupancy, ticket prices, train formations and open data from opentransportdata.swiss. Runs locally from the swiss-transport-mcp Python package.
mcp-nbb
MCP server for the National Bank of Belgium SDMX statistical API. Runs locally from the mcp-nbb Python package. Needs 3 environment variables to run.
luxembourg-mcp
Keyless MCP access to official Luxembourg public data. Runs locally from the luxembourg-mcp Python package.