Radar
NPM · @PIPEWORX/MCP-RADAR · 2 COMPONENTS
Radar MCP — wraps the Radar Geocoding / Search API (radar.com)
Available components
Last scanned (4 hours ago)
Scores higher than 76% 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-radar). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 722 tokens (~144/item across 5 items; 5 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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.
- 4 Nov 26 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.20 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 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-radar@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-radar |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-radar/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3691873630 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:95360be477bca9150143602be768c93650dbc9d80863c84ca54f31132f83c95972f7cd3040058c874615f54bfdce04a28eb957386126b4d30d987b417 |
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 →
radar_autocomplete ~173
Autocomplete an address/place from partial text using Radar. Returns ranked address/place suggestions with coordinates. Optionally bias results near a lat,lng. Example: radar_autocomplete({ query: "841 broadway new", near: "40.73,-73.99", _apiKey: "prj_live_sk_..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Radar API key (get one free at radar.com). Looks like prj_live_sk_... or prj_live_pk_... |
| limit | number | – | Optional max number of results (default 10) |
| near | string | – | Optional proximity bias as "latitude,longitude", e.g. "40.73,-73.99" |
| query | string | yes | Partial address or place name, e.g. "841 broadway new" |
No output schema declared.
No examples provided.
radar_context ~131
Get place/geofence/region context for coordinates using Radar. Returns geofences, the containing place, and administrative region (country/state/postal code) for a lat/lng. Example: radar_context({ lat: 40.70390, lon: -73.98670, _apiKey: "prj_live_sk_..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Radar API key (get one free at radar.com) |
| lat | number | yes | Latitude, e.g. 40.70390 |
| lon | number | yes | Longitude, e.g. -73.98670 |
No output schema declared.
No examples provided.
radar_geocode ~109
Geocode an address to coordinates using Radar (forward geocoding). Returns the best-match formatted address with latitude/longitude. Example: radar_geocode({ query: "841 Broadway, New York, NY", _apiKey: "prj_live_sk_..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Radar API key (get one free at radar.com) |
| query | string | yes | Full address to geocode, e.g. "841 Broadway, New York, NY 10003" |
No output schema declared.
No examples provided.
radar_ip_geocode ~140
Geolocate an IP address to city/state/country and approximate coordinates using Radar. Omit `ip` to geolocate the caller. Example: radar_ip_geocode({ ip: "8.8.8.8", _apiKey: "prj_live_sk_..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Radar API key (a secret prj_live_sk_... key is required to pass an explicit ip) |
| ip | string | – | Optional IPv4/IPv6 address to geolocate, e.g. "8.8.8.8". If omitted, Radar geolocates the request origin. |
No output schema declared.
No examples provided.
radar_reverse_geocode ~118
Reverse geocode coordinates to an address using Radar. Returns the formatted address for a lat/lng. Example: radar_reverse_geocode({ lat: 40.70390, lon: -73.98670, _apiKey: "prj_live_sk_..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Radar API key (get one free at radar.com) |
| lat | number | yes | Latitude, e.g. 40.70390 |
| lon | number | yes | Longitude, e.g. -73.98670 |
No output schema declared.
No examples provided.
How do I install the Radar MCP server?
Radar runs locally as an npm package, launched with npx -y @pipeworx/mcp-radar. 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-radar
claude mcp add pipeworx-io-radar -- npx -y @pipeworx/mcp-radar
What is the Radar MCP server?
Radar is an MCP server listed in the public MCP registry as io.github.pipeworx-io/radar. Radar MCP, wraps the Radar Geocoding / Search API (radar.com). This page covers its npm package (@pipeworx/mcp-radar).
Is the Radar MCP server safe to use?
Radar 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 Radar MCP server expose?
Radar exposes 5 tools: radar_autocomplete, radar_geocode, radar_reverse_geocode, radar_ip_geocode, radar_context. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.
Is the Radar MCP server still maintained?
Radar 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 Radar MCP server under?
Radar declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.