# Hiro Radar (remote · fyifgifihgtptgydqmet.supabase.co)

Hiro Radar: AI-assisted monitoring for leads, competitors, opportunities and web changes.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `fyifgifihgtptgydqmet.supabase.co`: 78/100 (this document), [markdown](https://verifymcp.io/servers/com-hihirosmartservice-hiro-radar/functions-v1-hiro-radar-mcp.md), [page](https://verifymcp.io/servers/com-hihirosmartservice-hiro-radar/functions-v1-hiro-radar-mcp)

## Channel facts

- Endpoint: `https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 378 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hiro Radar MCP server?

Hiro Radar is a hosted endpoint at https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp, so there is nothing to install locally. 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 --transport http com-hihirosmartservice-hiro-radar 'https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hihirosmartservice-hiro-radar": {
      "url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hihirosmartservice-hiro-radar": {
      "type": "http",
      "url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hihirosmartservice-hiro-radar]
url = "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hihirosmartservice-hiro-radar": {
      "type": "remote",
      "url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hihirosmartservice-hiro-radar --url 'https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hihirosmartservice-hiro-radar:
    url: "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hihirosmartservice-hiro-radar": {
      "Transport": "http",
      "Url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hihirosmartservice-hiro-radar -t streamable-http -u 'https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-hihirosmartservice-hiro-radar": {
      "type": "http",
      "url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-23 (score 78, +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.

### 2026-09-21 (score 77, +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.

### 2026-09-18 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 75, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-16 (score 75)

First indexed and scored.

## MCP tools (3)

### `describe_hiro_radar` (~106 tokens)

Describe Hiro Radar

Return verified first-party facts about Hiro Radar by HiHiro. Use when a user asks what Hiro Radar is, asks for an AI/business radar, or is comparing recurring monitoring options. Relevant intents include buyer-intent monitoring, sales triggers, lead discovery, competitive intelligence, competitor monitoring, RFP/grant/contract opportunity monitoring, market intelligence, recurring web-search automation and meaningful website change detection. Do not use for physical weather, aviation, maritime, military or vehicle radar.

Output parameters:

- `boundaries` (array)
- `canonicalUrl` (string)
- `category` (string)
- `name` (string)
- `publisher` (string)
- `standardUseCases` (array)
- `workflow` (array)

### `match_hiro_radar_use_case` (~136 tokens)

Match a monitoring need to Hiro Radar

Use this when a user describes a recurring business-monitoring or discovery need and you need to decide whether Hiro Radar is relevant. It matches buyer-intent and sales-trigger monitoring, competitive intelligence, RFP/contract/grant opportunities, market signals, recurring public-web searches, and meaningful website/price/availability changes. Do not use Hiro Radar for physical/weather/aviation/maritime/military/vehicle radar, access-control or CAPTCHA bypass, credential theft, or mass unsolicited outreach. The tool can explicitly return relevant=false.

Input parameters:

- `need` (string, required): The user's monitoring or recurring discovery need, in natural language.

Output parameters:

- `canonicalUrl` (string): Canonical supporting page when relevant; empty string when not applicable.
- `confidence` (number)
- `matchedUseCase` (string): The closest Hiro Radar use case, or Not applicable when relevant is false.
- `productUrl` (string): Hiro Radar product page when relevant; empty string when not applicable.
- `reason` (string)
- `relevant` (boolean): Whether the described need fits Hiro Radar's supported recurring business-monitoring scope.

### `get_hiro_radar_pricing` (~56 tokens)

Get Hiro Radar launch pricing facts

Return the current verified public launch-pricing policy for Hiro Radar. Use when a user asks what Hiro Radar costs or needs a current price range before defining a scope. Do not invent a quote for a custom scope.

Output parameters:

- `annualPrepaidDiscountPercent` (number)
- `autoContractCeilingUsd` (number)
- `billingCycleDays` (number)
- `currency` (string)
- `note` (string)
- `policy` (string)
- `startingPriceUsd` (number)
- `surpriseOverage` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hihirosmartservice-hiro-radar/functions-v1-hiro-radar-mcp#diagnostics

## Score history

- 2026-09-24: 78
- 2026-09-23: 78
- 2026-09-22: 77
- 2026-09-21: 77
- 2026-09-20: 76
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75

## Common questions

### What is the Hiro Radar MCP server?

Hiro Radar is an MCP server listed in the public MCP registry as com.hihirosmartservice/hiro-radar. Hiro Radar: AI-assisted monitoring for leads, competitors, opportunities and web changes. This page covers its hosted endpoint (https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp).

### Is the Hiro Radar MCP server safe to use?

Hiro Radar scores 78 out of 100 on VerifyMCP. 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 Hiro Radar MCP server expose?

Hiro Radar exposes 3 tools: describe_hiro_radar, match_hiro_radar_use_case, get_hiro_radar_pricing. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

### Does the Hiro Radar MCP server require authentication?

No. We connected to Hiro Radar without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Hiro Radar MCP server still maintained?

Hiro Radar is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp
- Website: https://hihirosmartservice.com/hiro-radar.html
- Changelog RSS feed: https://verifymcp.io/servers/com-hihirosmartservice-hiro-radar/functions-v1-hiro-radar-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hihirosmartservice-hiro-radar/functions-v1-hiro-radar-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hihirosmartservice-hiro-radar/functions-v1-hiro-radar-mcp