Hiro Radar
by fyifgifihgtptgydqmet.supabase.co in Developer tools
Hiro Radar: AI-assisted monitoring for leads, competitors, opportunities and web changes.
https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp- Tools
- 3
- open to any client
- Uptime
- 66.7%
- last 30 days
- Response time
- 115 ms
- 165 ms slowest 5%
- Last check
- Passed
- 4 h ago, next in 2 h
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"hiro-radar": {
"type": "http",
"url": "https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp"
}
}
}3 tools
- 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…
- match_hiro_radar_use_case
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…
- get_hiro_radar_pricing
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.
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 h ago | Passed | 200 | 106 ms |
| 15 h ago | Passed | 200 | 126 ms |
| 25 h ago | Passed | 200 | 107 ms |
| 36 h ago | Passed | 200 | 134 ms |
| 46 h ago | Passed | 200 | 100 ms |
Show 7 older checks
| 2 days ago | Passed | 200 | 165 ms |
| 3 days ago | Passed | 200 | 115 ms |
| 3 days ago | Passed | 200 | 123 ms |
| 4 days ago | initialize returned HTTP 400 | 400 | 436 ms |
| 6 days ago | initialize returned HTTP 400 | 400 | 190 ms |
| 6 days ago | initialize returned HTTP 400 | 400 | 196 ms |
| 6 days ago | initialize returned HTTP 400 | 400 | 172 ms |