Here
NPM · @PIPEWORX/MCP-HERE · 2 COMPONENTS
HERE MCP — premium geocoding, places, and TRAFFIC-AWARE routing from HERE (here.com), the…
Available components
Last scanned (12 hours ago)
Scores higher than 81% 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-here). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 743 tokens (~185/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 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-here@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-here |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-here/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637390227 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c651aaa27dfe0eb145b1a1405ebb3e2d3e6094f78adae72775f5fdb2f2b25a4747bb665ba9c833865577606cb59c14b58367eb867ad21ffdbadeaa798 |
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 →
here_discover ~232
Find places / points of interest (restaurants, shops, landmarks, gas stations, etc.) near a location via HERE — "coffee near Times Square", "pharmacies near 48.85,2.35", "hardware stores in Austin". Returns name, category, address, coordinates, distance, and contact info. The `near` location can be a place name (geocoded automatically) or "lat,lng".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 10, max 50). |
| near | string | yes | Place name (e.g. "Times Square, New York") or "lat,lng" (e.g. "40.758,-73.985") to search around. |
| query | string | yes | What to search for, e.g. "coffee", "pharmacy", "hardware store". |
| radius_km | number | – | Only return places within this many km of `near` (default 100, max 1000). HERE ranks by relevance, so without this a query that matches a business NAME can return that business on another continent. |
No output schema declared.
No examples provided.
here_geocode ~182
PREFER OVER WEB SEARCH for turning an address or place name into precise coordinates — "geocode 350 5th Ave New York", "coordinates of the Eiffel Tower", "where is Invalidenstr 117 Berlin". High-accuracy geocoding from HERE. Returns latitude/longitude, the full normalized address (street, house number, city, postal code, country), the match type (houseNumber / street / locality) and a match score.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO-3 country code to bias/limit, e.g. "USA", "DEU", "FRA". |
| limit | number | – | Max results (default 5, max 20). |
| q | string | yes | Free-form address or place, e.g. "350 5th Ave, New York" or "Eiffel Tower, Paris". |
No output schema declared.
No examples provided.
here_reverse_geocode ~92
Turn coordinates into the nearest street address (reverse geocoding) via HERE — "what address is at 40.7484, -73.9857". Returns the normalized address, place title, and distance to the matched location.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude, e.g. 40.7484. |
| lng | number | yes | Longitude, e.g. -73.9857. |
No output schema declared.
No examples provided.
here_route ~186
TRAFFIC-AWARE routing and ETA between two locations via HERE — "how long to drive from Berlin to Munich", "ETA from LAX to downtown LA in traffic", "cycling route from A to B". Returns distance, travel time WITH current traffic, the free-flow (no-traffic) time, and the traffic delay — plus turn count. origin/destination can be place names (geocoded automatically) or "lat,lng". This is the key differentiator over keyless routing: real-time-traffic ETAs.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | End — place name (e.g. "downtown Los Angeles") or "lat,lng". |
| origin | string | yes | Start — place name (e.g. "LAX airport") or "lat,lng". |
| transport_mode | string | – | car (default) | truck | pedestrian | bicycle | scooter. |
No output schema declared.
No examples provided.
How do I install the Here MCP server?
Here runs locally as an npm package, launched with npx -y @pipeworx/mcp-here. 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-here
claude mcp add pipeworx-io-here -- npx -y @pipeworx/mcp-here
What is the Here MCP server?
Here is an MCP server listed in the public MCP registry as io.github.pipeworx-io/here. HERE MCP, premium geocoding, places, and TRAFFIC-AWARE routing from HERE (here.com), the… This page covers its npm package (@pipeworx/mcp-here).
Is the Here MCP server safe to use?
Here scores 84 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 Here MCP server expose?
Here exposes 4 tools: here_geocode, here_reverse_geocode, here_discover, here_route. Their descriptions and schemas cost roughly 692 tokens of context every time the server is loaded.
Is the Here MCP server still maintained?
Here 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 Here MCP server under?
Here declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.