osm-edit-mcp@0.4.1
VERIFIED· not startedPublisher claims: "Review-first MCP server for safe OpenStreetMap POI nodes and polygons, duplicate review, node tag edits and GPX road edits" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
API_KEYOSM_DEV_CLIENT_SECRETOSM_PROD_CLIENT_SECRETor--reauthorizeConfiguration, not credentials: ALLOWED_ORIGINS, OSM_DEV_CLIENT_ID, OSM_DEV_REDIRECT_URI, OSM_EDIT_MCP_ENV_FILE, OSM_PROD_CLIENT_ID, OSM_PROD_REDIRECT_URI, OSM_USE_PROD_API- Where it talks to
- no vendor host named in the codeAlso openstreetmap.org, overpass-api.de — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names openstreetmap.org, overpass-api.de as well as its own vendor. The guard injects API_KEY, OSM_DEV_CLIENT_SECRET, OSM_PROD_CLIENT_SECRET only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 83/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
USER_AGENT = f"osm-edit-mcp/{config.mcp_server_version} (+https://github.com/skywinder/osm-edit-mcp)"Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# Never consume an unrelated .env from the MCP host's workingFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.monkeypatch.setattr(config, "osm_overpass_url", "file:///etc/passwd")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.tracked_output = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# from an unrelated working-directory .env.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env.production",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."""An MCP host's unrelated or binary .env must not affect startup."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.(tmp_path / ".env").write_bytes(b"\x00GITCRYPT\xff")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env.example",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Please set OSM_DEV_CLIENT_ID and OSM_DEV_CLIENT_SECRET in your .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Set OSM_EDIT_MCP_ENV_FILE=/absolute/path/to/.env to load dotenv credentials.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."Please set OSM_PROD_CLIENT_ID and OSM_PROD_CLIENT_SECRET in your .env file"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.