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/fouomene/geodataplacefinderWrote 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/fouomene/geodataplacefinder/mcp-server-geodata-placefinder)<a href="https://agentmods.dev/mcp/fouomene/geodataplacefinder/mcp-server-geodata-placefinder"><img src="https://agentmods.dev/badge/mcp/fouomene/geodataplacefinder/mcp-server-geodata-placefinder/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/fouomene/geodataplacefinder/mcp-server-geodata-placefinder"><img src="https://agentmods.dev/badge/mcp/fouomene/geodataplacefinder/mcp-server-geodata-placefinder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp-server-geodata-placefinder 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 GPL-3.0
The repository is licensed GPL-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 · 10 lines scan A 675712940b25
mcp-server-geodata-placefinder is an MCP server published in the GitHub repository fouomene/geodataplacefinder (0 stars, last pushed 3mo ago), licensed GPL-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
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.
swisstopo
MCP server "swisstopo" as configured in malkreide/swisstopo-mcp. Runs swisstopo_mcp.server with python.
swisstopo-mcp
MCP server for Swiss federal geodata (Swisstopo APIs). Runs locally from the swisstopo-mcp Python package.
placeroot
Ground AI agents in open map data. MCP server for Overture Maps — compact answers, no API key. Runs locally from the placeroot Python package. Needs 1 environment variable to run.
osm-mcp
Geocoding, walking/driving/cycling distances, route optimization, isochrones and POI search on OSM. Runs locally from the osm-mcp npm package. Needs 4 environment variables to run.
norwegian-data-mcp
Norwegian public data (companies, statistics, addresses) as MCP tools. No API keys. Runs locally from the norwegian-data-mcp Python package.