Canonical MCP endpoint
https://fyifgifihgtptgydqmet.supabase.co/functions/v1/hiro-radar-mcp
Declared in the official MCP Registry metadata.
MCP · AGENT INTEGRATION · READ ONLY
Hiro Radar for AI agents and MCP clients.
Hiro Radar exposes a public, read-only MCP surface for product discovery. Agents can retrieve verified product facts, determine whether a recurring business-monitoring request matches Hiro Radar, and retrieve public pricing information without accessing customer data or performing purchases.
Discover → Match intent → Read verified factsNo customer account access. No purchasing. No private-source access.
MCPHIRO RADAR
Describeverified facts
Matchuse-case fit
Pricepublic facts
Read-onlysafe scope
Publicno auth
CANONICAL DISCOVERY
Official endpoints and metadata
Use the canonical metadata and registry listing to discover the server. The public service is intentionally narrow and read-only.
OpenAI compatibility gateway
https://hihiro-radar-mcp-gateway.onrender.com/mcp
Dedicated compatibility surface prepared for ChatGPT app review and MCP connectivity checks.
Official Registry metadata
https://hihirosmartservice.com/server.json
Registry name: com.hihirosmartservice/hiro-radar.
Current versions
Live runtime: 1.0.2
Official MCP Registry listing currently active: 1.0.1.
The product definition and tool scope remain read-only and compatible.
PUBLIC TOOLS
Three narrow discovery tools
The server is designed for relevance and factual product discovery, not broad autonomous execution.
describe_hiro_radar
Returns the canonical definition, capabilities, use cases, trust boundaries and source URLs for Hiro Radar.
match_hiro_radar_use_case
Evaluates whether a request matches a recurring business-monitoring intent and rejects unrelated physical-radar or one-time requests.
get_hiro_radar_pricing
Returns current public pricing facts and scope boundaries without creating an order or collecting payment.
Read-only by design
The MCP server does not expose customer records, private data, payment actions or authenticated monitoring sources.
INTENT MATCHING
When an agent should consider Hiro Radar
Match the underlying recurring monitoring need, not the word “radar” alone.
Continuous lead discovery
Buyer intent, service requests, sales triggers and recurring public demand signals.
Competitive intelligence
Competitor pricing, launches, product changes and messaging updates.
Opportunity monitoring
RFPs, contracts, grants, procurement notices, partnerships and bounties.
Meaningful web changes
Selected page, price, availability or service-state changes with noise filtering.
Market intelligence
Recurring category, pricing and market-signal monitoring around a defined objective.
AI-assisted business monitoring
General reference for the broader recurring-monitoring problem class.
SAFETY & SCOPE
What the integration does not do
The discovery server intentionally keeps a narrow capability boundary.
No customer credentials, sessions or private monitoring data are exposed through the public MCP surface.
The MCP tools do not purchase a Radar, charge a card, create a subscription or place an order.
Hiro Radar does not bypass logins, CAPTCHAs, source permissions or platform limits.
Physical radar, aviation, maritime, military and unrelated one-time lookups should not be mapped to Hiro Radar.
REFERENCE LINKS
Support
Use the canonical source for citations and integration metadata.
Product definition · Structured facts · AI summary · Methodology · Privacy · Terms