Opentripmap
NPM · @PIPEWORX/MCP-OPENTRIPMAP · 2 COMPONENTS
OpenTripMap MCP — wraps the OpenTripMap Places API (dev.opentripmap.org)
Available components
Last scanned (2 hours ago)
Scores higher than 77% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-opentripmap). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 900 tokens (~225/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-opentripmap@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-opentripmap |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-opentripmap/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685173374 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f155e391130f8366d2d06b869d7c9a3c33dd24c7c1154cc5b1aa8cdba05f22db9bda82a7f3861bea1f48aeba2682159a6bdf24c81dcb5f691771f0821 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
opentripmap_autosuggest ~227
Typeahead / partial-name search for POIs near a lat/lon point. Matches place names by prefix within a radius — good for "find places starting with X near here". Returns matching POIs with xid, name, kinds, distance, and coordinates. Example: opentripmap_autosuggest({ name: "louv", lat: 48.8566, lon: 2.3522, radius: 5000, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | OpenTripMap API key |
| kinds | string | – | Optional comma-separated category filter |
| lang | string | – | Two-letter language code (default "en") |
| lat | number | yes | Latitude of the search center |
| limit | number | – | Max results to return (default 50) |
| lon | number | yes | Longitude of the search center |
| name | string | yes | Partial place name to match, e.g. "louv" |
| radius | number | yes | Search radius in meters, e.g. 5000 |
No output schema declared.
No examples provided.
opentripmap_geoname ~163
Resolve a city / place name to geographic coordinates and metadata (lat, lon, population, country, timezone). Use this to turn a place name into a lat/lon you can feed to opentripmap_places_radius. Example: opentripmap_geoname({ name: "Paris", country: "FR", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | OpenTripMap API key |
| country | string | – | Optional ISO 3166 two-letter country code to disambiguate, e.g. "FR", "US" |
| lang | string | – | Two-letter language code (default "en") |
| name | string | yes | City or place name, e.g. "Paris", "Kyoto" |
No output schema declared.
No examples provided.
opentripmap_place_detail ~145
Get full details for a single place by its OpenTripMap xid (obtained from opentripmap_places_radius or opentripmap_autosuggest). Returns name, address, categories, Wikidata/Wikipedia links, description extract, image, and website. Example: opentripmap_place_detail({ xid: "N123456", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | OpenTripMap API key |
| lang | string | – | Two-letter language code for text (default "en") |
| xid | string | yes | OpenTripMap place id (xid), e.g. "N123456" or "W789" |
No output schema declared.
No examples provided.
opentripmap_places_radius ~311
Find points of interest (tourist attractions, museums, restaurants, historic sites, etc.) within a radius of a lat/lon point. Returns matching POIs with xid, name, kind categories, distance from the center, and coordinates. Example: opentripmap_places_radius({ lat: 48.8566, lon: 2.3522, radius: 1000, kinds: "museums", limit: 20, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | OpenTripMap API key (free at https://dev.opentripmap.org/register) |
| kinds | string | – | Optional comma-separated category filter, e.g. "museums", "historic,architecture", "foods". See OpenTripMap "kinds" taxonomy. |
| lang | string | – | Two-letter language code for names (default "en") |
| lat | number | yes | Latitude of the search center, e.g. 48.8566 |
| limit | number | – | Max number of POIs to return (default 50) |
| lon | number | yes | Longitude of the search center, e.g. 2.3522 |
| radius | number | yes | Search radius in meters, e.g. 1000 |
| rate | string | – | Optional minimum importance rating: "1","2","3","1h","2h","3h" (h = has Wikidata/heritage). Filters to more notable places. |
No output schema declared.
No examples provided.
How do I install the Opentripmap MCP server?
Opentripmap runs locally as an npm package, launched with npx -y @pipeworx/mcp-opentripmap. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-opentripmap
claude mcp add pipeworx-io-opentripmap -- npx -y @pipeworx/mcp-opentripmap
What is the Opentripmap MCP server?
Opentripmap is an MCP server listed in the public MCP registry as io.github.pipeworx-io/opentripmap. OpenTripMap MCP, wraps the OpenTripMap Places API (dev.opentripmap.org). This page covers its npm package (@pipeworx/mcp-opentripmap).
Is the Opentripmap MCP server safe to use?
Opentripmap scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Opentripmap MCP server expose?
Opentripmap exposes 4 tools: opentripmap_places_radius, opentripmap_place_detail, opentripmap_geoname, opentripmap_autosuggest. Their descriptions and schemas cost roughly 846 tokens of context every time the server is loaded.
Is the Opentripmap MCP server still maintained?
Opentripmap is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Opentripmap MCP server under?
Opentripmap declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.