PREFLIGHT — URL Routing for AI Agents
REMOTE · PREFLIGHT-API-PRODUCTION-01A2.UP.RAILWAY.APP · SCANNED OCT 4
Choose HTTP, browser, machine endpoint, or avoid before an agent visits an unfamiliar URL.
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 256 tokens (~128/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage73
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 20% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the PREFLIGHT — URL Routing for AI Agents MCP server?
PREFLIGHT — URL Routing for AI Agents is a hosted endpoint at https://preflight-api-production-01a2.up.railway.app/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 · preflight-api-production-01a2.up.railway.app
claude mcp add --transport http gsterlingpress-preflight 'https://preflight-api-production-01a2.up.railway.app/mcp'
{
"mcpServers": {
"gsterlingpress-preflight": {
"url": "https://preflight-api-production-01a2.up.railway.app/mcp"
}
}
} {
"servers": {
"gsterlingpress-preflight": {
"type": "http",
"url": "https://preflight-api-production-01a2.up.railway.app/mcp"
}
}
} [mcp_servers.gsterlingpress-preflight] url = "https://preflight-api-production-01a2.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gsterlingpress-preflight": {
"type": "remote",
"url": "https://preflight-api-production-01a2.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add gsterlingpress-preflight --url 'https://preflight-api-production-01a2.up.railway.app/mcp' --transport streamable-http
mcp_servers:
gsterlingpress-preflight:
url: "https://preflight-api-production-01a2.up.railway.app/mcp" {
"McpServers": {
"gsterlingpress-preflight": {
"Transport": "http",
"Url": "https://preflight-api-production-01a2.up.railway.app/mcp"
}
}
} assistant mcp add gsterlingpress-preflight -t streamable-http -u 'https://preflight-api-production-01a2.up.railway.app/mcp'
{
"mcpServers": {
"gsterlingpress-preflight": {
"type": "http",
"url": "https://preflight-api-production-01a2.up.railway.app/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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Aug 26 0
- Server version: 0.7.4 → 0.7.5 functional
- 13 Aug 26 0
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “preflight_check” rewrote its description, which is the text the model reads security
- “preflight_check” reworded the description of “url” cosmetic
- Tool “preflight_check” changed its title: Check URL Before Fetching cosmetic
- Tool “preflight_feedback” changed its title: Report PREFLIGHT Outcome cosmetic
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 6 Oct 2026 · Probed https://preflight-api-production-01a2.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of preflight-api-production-01a2.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | 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 | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://preflight-api-production-01a2.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://preflight-api-production-01a2.up.railway.app/mcp | HTTPS enforced | 301 | https://preflight-api-production-01a2.up.railway.app/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 →
preflight_check Check URL Before Fetching ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Actual absolute http/https destination URL from the current task. Use before the first fetch or browser request. |
No output schema declared.
No examples provided.
preflight_feedback Report PREFLIGHT Outcome ~59
After following a PREFLIGHT recommendation, report whether the chosen route worked so PREFLIGHT can improve future recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| latencyMs | number | – | – |
| outcome | string | yes | – |
| route | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
What is the PREFLIGHT — URL Routing for AI Agents MCP server?
PREFLIGHT — URL Routing for AI Agents is an MCP server listed in the public MCP registry as io.github.GSterlingPress/preflight. Choose HTTP, browser, machine endpoint, or avoid before an agent visits an unfamiliar URL. This page covers its hosted endpoint (https://preflight-api-production-01a2.up.railway.app/mcp).
Is the PREFLIGHT — URL Routing for AI Agents MCP server safe to use?
PREFLIGHT — URL Routing for AI Agents scores 84 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 PREFLIGHT — URL Routing for AI Agents MCP server expose?
PREFLIGHT — URL Routing for AI Agents exposes 2 tools: preflight_check, preflight_feedback. Their descriptions and schemas cost roughly 165 tokens of context every time the server is loaded.
Does the PREFLIGHT — URL Routing for AI Agents MCP server require authentication?
No. We connected to PREFLIGHT — URL Routing for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PREFLIGHT — URL Routing for AI Agents MCP server still maintained?
PREFLIGHT — URL Routing for AI Agents is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.