Skip to content
Back to the index

radar

pipeworx.ioInfrastructure

No liveness check has reached it yet; it has been in the index since 10 Oct 2026. How this is checked

Radar MCP Server exposes five location tools through a hosted Model Context Protocol endpoint. Developers can use it for address autocomplete, forward and reverse geocoding, IP geolocation, and place or geofence context.

Inferred · not functionally tested

WebAPICloud-managed
radar preview
Visit pipeworx.io
1alternative
7features
2026since

Overview

6 features

Purpose: Adding address search, geocoding, IP geolocation, and location context to MCP-enabled applications.

Inferred · not functionally tested

Audience: developers building location-aware AI agents and applications

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: unknown · Self-hosting: unknown

Recorded constraints: pricing: unknown · license: Proprietary · platforms: WEB · deployment: browser, api_only, cloud_managed

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: gateway.pipeworx.io. These links do not verify the individual claims.

In the Frameworks & SDKs space, radar takes a focused approach. Inferred · not functionally tested: It focuses on adding address search, geocoding, IP geolocation, and location context to MCP-enabled applications. Inferred · not functionally tested: It is built as a B2B product for developers building location-aware AI agents and applications. Basis unknown · not verified: It ships for the web and API.

Behind radar is Pipeworx. Inferred · not functionally tested: Key capabilities include address autocomplete, forward geocoding, and reverse geocoding. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Address autocomplete
  • Forward geocoding
  • Reverse geocoding
  • IP geolocation
  • Place context
  • Geofence context

Topics: Inferred · not functionally tested

Tags
mcp-servergeocoding-apiip-geolocationlocation-context

JSON profile · Text profile · Access guide

Built with & integrations

Hosting
Cloudflare
Connectors
MCPAPI
Runs on
BrowserAPI-onlyCloud-managed
Detected from
Cloudflare
cf-ray header

Trust & compliance

Public signals
HTTPS

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed10 Oct · 00:02 UTC
    Radar seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about radar

What is radar?
Inferred · not functionally tested: Radar focuses on adding address search, geocoding, IP geolocation, and location context to MCP-enabled applications. It is catalogued under Frameworks & SDKs on PulseGate.
Who is radar for?
Inferred · not functionally tested: radar is a B2B product built for developers building location-aware AI agents and applications.
What platforms does radar run on?
Basis unknown · not verified: radar runs on the web and API.
Is radar still maintained?
Unverified. radar has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to radar?
Similar projects tracked by PulseGate include cloudflare-radar, Mcp, and Radar.cloudflare-radarMcpRadar
Who makes radar?
radar is developed by Pipeworx.
Does radar have an API or integrations?
Inferred · not functionally tested: Yes — radar exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do