PREFLIGHT — URL Routing for AI Agents
Choose HTTP, browser, machine endpoint, or avoid before an agent visits an unfamiliar URL.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'preflight_feedback' description lacks action verbin preflight_feedback
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"preflight": {
"url": "https://preflight-api-production-01a2.up.railway.app/mcp"
}
}
}Remote endpoints
https://preflight-api-production-01a2.up.railway.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢preflight_check(url)
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.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"format": "uri",
"description": "Actual absolute http/https destination URL from the current task. Use before the first fetch or browser request."
}
},
"required": [
"url"
],
"additionalProperties": false
}⚪preflight_feedback(url, route, outcome, latencyMs)
After following a PREFLIGHT recommendation, report whether the chosen route worked so PREFLIGHT can improve future recommendations.
Input Schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"format": "uri"
},
"route": {
"type": "string",
"enum": [
"HTTP",
"BROWSER",
"MACHINE_ENDPOINT",
"AVOID"
]
},
"outcome": {
"type": "string",
"enum": [
"success",
"failure"
]
},
"latencyMs": {
"type": "number",
"minimum": 0,
"maximum": 300000
}
},
"required": [
"url",
"route",
"outcome"
],
"additionalProperties": false
}Community
Evidence