PREFLIGHT — URL Routing for AI Agents
Server Details
Choose HTTP, browser, machine endpoint, or avoid before an agent visits an unfamiliar URL.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- GSterlingPress/preflight-api
- GitHub Stars
- 0
- Server Listing
- preflight-api
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs the initial URL check and routing, the other collects feedback after following the recommendation. There is no overlap or ambiguity between them.
Both tools share the 'preflight_' prefix and use snake_case, but the second word differs in part of speech ('check' is a verb, 'feedback' is a noun). The pattern is predictable yet not perfectly uniform.
With only two tools, the server feels minimal but coherent for its narrow purpose. It is on the thin edge but not overly sparse for a single-function preflight service.
The core workflow is covered: check a URL for the best route and then provide feedback on the outcome. No obvious dead ends, though additional tools like a history or stats view could be considered but aren't essential.
Available Tools
2 toolspreflight_checkCheck URL Before FetchingARead-onlyIdempotentInspect
Before fetching, crawling, scraping, opening, or browser-rendering an unfamiliar http/https URL, call this with the ACTUAL destination URL. Returns the best first route: HTTP, BROWSER, MACHINE_ENDPOINT, or AVOID, plus access/JS/size/cost hints. Do not substitute example.com when a real task URL is available.
Inputs: url (required).
preflight_feedbackReport PREFLIGHT OutcomeAInspect
After following a PREFLIGHT recommendation, report whether the chosen route worked so PREFLIGHT can improve future recommendations.
Inputs: url (required), route (required), outcome (required), latencyMs.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Tells your agent if a link is safe before it clicks, signs in or pays.
Scan a URL before your agent reads it: hidden prompt injection, phishing, clean markdown.
Scan a URL before your agent reads it: hidden prompt injection, phishing, clean markdown.
Threat-intelligence verdicts on a URL, domain or IP before a coding agent connects to it.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to inspect a URL before opening, following, or recommending it, by tracing redirect chains via headers, stripping tracking parameters, detecting phishing-style URL tricks, and cross-checking threat-intel feeds to return a SAFE, SUSPICIOUS, or DANGEROUS verdict with supporting evidence. It also scans text for embedded and defanged links and vets agent skills prior to installation.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check URL safety before fetching content, using Google Web Risk, URLhaus, PhishTank, and AI analysis to return SAFE/SUSPICIOUS/DANGEROUS verdicts.1114 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables checking suspicious URLs for risk without opening them, providing full checkups and lookalike detection.MIT
- AlicenseNot gradedqualityDmaintenanceEnables an agent to drive a real browser while enforcing provenance-based gating so URLs and form values must trace to the user or an allowlist, never to untrusted page content.AGPL 3.0
Glama MCP Gateway
Add one secure layer between your agents and this server.