Hiro Radar
REMOTE · FYIFGIFIHGTPTGYDQMET.SUPABASE.CO · SCANNED SEP 24
Hiro Radar: AI-assisted monitoring for leads, competitors, opportunities and web changes.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 378 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · fyifgifihgtptgydqmet.supabase.co
claude mcp add --transport http com-hihirosmartservice-hiro-radar 'https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp'
{
"mcpServers": {
"com-hihirosmartservice-hiro-radar": {
"url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
}
}
} {
"servers": {
"com-hihirosmartservice-hiro-radar": {
"type": "http",
"url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
}
}
} [mcp_servers.com-hihirosmartservice-hiro-radar] url = "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
{
"$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 mcp add com-hihirosmartservice-hiro-radar --url 'https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp' --transport streamable-http
mcp_servers:
com-hihirosmartservice-hiro-radar:
url: "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp" {
"McpServers": {
"com-hihirosmartservice-hiro-radar": {
"Transport": "http",
"Url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
}
}
} assistant mcp add com-hihirosmartservice-hiro-radar -t streamable-http -u 'https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp'
{
"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.
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.
- 23 Sept 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.
- 21 Sept 26 +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.
- 18 Sept 26 +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.
- 17 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Sept 26 75
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 24 Sept 2026 · Probed https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=supabase.co | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 7c35296a896c0a6f13f8495266045d45 |
| SANs: supabase.co, *.supabase.co | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of fyifgifihgtptgydqmet.supabase.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| supabase.co. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 400 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp | Verified | 200 | |
| http (plaintext) | http://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp | HTTPS enforced | 301 | https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp |
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 →
describe_hiro_radar Describe Hiro Radar ~106
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| boundaries | array | yes | – |
| canonicalUrl | string | yes | – |
| category | string | yes | – |
| name | string | yes | – |
| publisher | string | yes | – |
| standardUseCases | array | yes | – |
| workflow | array | yes | – |
No examples provided.
get_hiro_radar_pricing Get Hiro Radar launch pricing facts ~56
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| annualPrepaidDiscountPercent | number | yes | – |
| autoContractCeilingUsd | number | yes | – |
| billingCycleDays | number | yes | – |
| currency | string | yes | – |
| note | string | yes | – |
| policy | string | yes | – |
| startingPriceUsd | number | yes | – |
| surpriseOverage | boolean | yes | – |
No examples provided.
match_hiro_radar_use_case Match a monitoring need to Hiro Radar ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| need | string | yes | The user's monitoring or recurring discovery need, in natural language. |
| Name | Type | Req | Description |
|---|---|---|---|
| canonicalUrl | string | yes | Canonical supporting page when relevant; empty string when not applicable. |
| confidence | number | yes | – |
| matchedUseCase | string | yes | The closest Hiro Radar use case, or Not applicable when relevant is false. |
| productUrl | string | yes | Hiro Radar product page when relevant; empty string when not applicable. |
| reason | string | yes | – |
| relevant | boolean | yes | Whether the described need fits Hiro Radar's supported recurring business-monitoring scope. |
No examples provided.
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.