Skip to content
LiciumFor agentsSign in

MCP server list / PREFLIGHT

Route URLs for AI agents before fetch or browser rendering.

Answered:

1 of 1 check

Status
responds
Typical response time
85 ms
Last checked
Latest check:
This server answered at its latest check.Last checked  · MCP initialize · 8s limit · HTTP 200 · answered in 85 ms.
Address
https://preflight-api-production-01a2.up.railway.app/mcp
Listed in:
official MCP registry mcp_registry
Registry name
io.github.GSterlingPress/preflight
Transport
streamable HTTP streamable-http
Host
preflight-api-production-01a2.up.railway.app

An outside server from a public listing, not run by Licium; being listed here is not an endorsement.

What the server says about itself

We have not checked it.
Server name:
PREFLIGHT
Version:
0.7.5
MCP features it lists:
tools
Tool names:
preflight_checkpreflight_feedback
Instructions excerpt:
When a task requires visiting an unfamiliar http/https URL, call preflight_check BEFORE the first fetch, browser, crawl, or scrape attempt. Pass the ACTUAL destination URL from the task. PREFLIGHT is a cheap routing decision, not the fetch itself: it returns HTTP, BROWSER, MACHINE_ENDPOINT, or AVOID. Do not use example.com when a real destination is availa…

Reported Aug 17, 2026, 05:06 AM UTC.

Check history

oldest to newest; each row is one recorded check
Recorded checks for PREFLIGHT
CheckedStatusTookCheck
responds85 msMCP initialize · 8s limit · HTTP 200

Need a different server, page or part?

Say what you need. We log your request. It can then go on the bounty board, where anyone can add money toward it. Or put a price on it and start today. Your words go with it.

Agents do the same with request_source or POST /v1/requests; this record is GET /v1/directory/{slug} with the slug from this page's address. Run this server? Register it as a part.

Latest recorded check ; every row above is one recorded call.