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/malkreide/swisstopo-mcpWrote 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/malkreide/swisstopo-mcp/swisstopo)<a href="https://agentmods.dev/mcp/malkreide/swisstopo-mcp/swisstopo"><img src="https://agentmods.dev/badge/mcp/malkreide/swisstopo-mcp/swisstopo/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/malkreide/swisstopo-mcp/swisstopo"><img src="https://agentmods.dev/badge/mcp/malkreide/swisstopo-mcp/swisstopo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swisstopo 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 10d 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
{
"swisstopo": {
"command": "python",
"args": [
"-m",
"swisstopo_mcp.server"
]
}
}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.
- 10d ago First seen · 9 lines scan A ad79531ffc71
swisstopo is an MCP server published in the GitHub repository malkreide/swisstopo-mcp (9 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
swiss-geodata-mcp
MCP server for the Swiss federal geodata (geo.admin.ch) — layer discovery, spatial identify, zoning, heights, coordinate conversion. Runs locally from the swiss-geodata-mcp Python package.
geolens
Apache-2.0 read-only Model Context Protocol (MCP) server for GeoLens. Lets coding agents discover datasets, inspect schemas, and ask spatial questions against any GeoLens instance. Runs locally from the geolens-mcp Python package. Needs 3 environment variables to run.
openstreetmap-mcp-server
Geocode, reverse geocode, and run Overpass spatial queries on OpenStreetMap data. Runs locally from the @cyanheads/openstreetmap-mcp-server npm package. Needs 6 environment variables to run.
zurich-opendata
MCP server "zurich-opendata" as configured in malkreide/zurich-opendata-mcp. Runs zurich_opendata_mcp.server with python.
zurich-opendata-mcp
MCP Server for City of Zurich Open Data — 23 tools for CKAN, geodata, parliament, council resolutions, tourism, and real-time data across 6 APIs. Runs locally from the zurich-opendata-mcp Python package.
osm-edit
Review-first MCP server for previewed, version-checked OpenStreetMap road edits from local GPX surveys. Runs locally from the osm-edit-mcp Python package. Needs 3 environment variables to run.