# Radar (npm · @pipeworx/mcp-radar)

Radar MCP — wraps the Radar Geocoding / Search API (radar.com)

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-radar/radar-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-radar/radar-mcp)
- npm · `@pipeworx/mcp-radar`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar.md), [page](https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-radar`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-radar).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-radar -- npx -y @pipeworx/mcp-radar
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-radar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-radar"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-radar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-radar"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-radar -- npx -y @pipeworx/mcp-radar
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-radar": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-radar"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-radar --command npx --arg -y --arg @pipeworx/mcp-radar
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-radar:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-radar"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-radar": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-radar"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-radar -t stdio -c npx -a -y @pipeworx/mcp-radar
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-radar": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-radar"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +3)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.20
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (5)

### `radar_autocomplete` (~173 tokens)

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_..." })

Input parameters:

- `_apiKey` (string, required): 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, required): Partial address or place name, e.g. "841 broadway new"

### `radar_geocode` (~109 tokens)

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_..." })

Input parameters:

- `_apiKey` (string, required): Radar API key (get one free at radar.com)
- `query` (string, required): Full address to geocode, e.g. "841 Broadway, New York, NY 10003"

### `radar_reverse_geocode` (~118 tokens)

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_..." })

Input parameters:

- `_apiKey` (string, required): Radar API key (get one free at radar.com)
- `lat` (number, required): Latitude, e.g. 40.70390
- `lon` (number, required): Longitude, e.g. -73.98670

### `radar_ip_geocode` (~140 tokens)

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_..." })

Input parameters:

- `_apiKey` (string, required): 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.

### `radar_context` (~131 tokens)

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_..." })

Input parameters:

- `_apiKey` (string, required): Radar API key (get one free at radar.com)
- `lat` (number, required): Latitude, e.g. 40.70390
- `lon` (number, required): Longitude, e.g. -73.98670

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### 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.

### What did VerifyMCP test on the Radar MCP server?

VerifyMCP ran 16 checks on Radar, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-radar
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-radar
- Repository: https://github.com/pipeworx-io/mcp-radar
- Website: https://pipeworx.io/packs/radar
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-radar/pipeworx-mcp-radar