Preflight
REMOTE · SKILLFOUNDRY.SYNAPLEX.AI · SCANNED SEP 27
Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm.
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 130 tokens (~130/item across 1 items; 1 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "check_publish_readiness" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 1 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 MCP server?
Preflight is a hosted endpoint at https://skillfoundry.synaplex.ai/products/preflight/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 · skillfoundry.synaplex.ai
claude mcp add --transport http evanfollis-preflight 'https://skillfoundry.synaplex.ai/products/preflight/mcp/'
{
"mcpServers": {
"evanfollis-preflight": {
"url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
}
}
} {
"servers": {
"evanfollis-preflight": {
"type": "http",
"url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
}
}
} [mcp_servers.evanfollis-preflight] url = "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"evanfollis-preflight": {
"type": "remote",
"url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/",
"enabled": true
}
}
} openclaw mcp add evanfollis-preflight --url 'https://skillfoundry.synaplex.ai/products/preflight/mcp/' --transport streamable-http
mcp_servers:
evanfollis-preflight:
url: "https://skillfoundry.synaplex.ai/products/preflight/mcp/" {
"McpServers": {
"evanfollis-preflight": {
"Transport": "http",
"Url": "https://skillfoundry.synaplex.ai/products/preflight/mcp/"
}
}
} assistant mcp add evanfollis-preflight -t streamable-http -u 'https://skillfoundry.synaplex.ai/products/preflight/mcp/'
{
"mcpServers": {
"evanfollis-preflight": {
"type": "http",
"url": "https://skillfoundry.synaplex.ai/products/preflight/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.
- 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
- 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 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
- 31 Jul 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
- 30 Jul 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
- 27 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 26 Jul 26 0
First indexed and scored.
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 27 Sept 2026 · Probed https://skillfoundry.synaplex.ai/products/preflight/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=synaplex.ai | CN=YE1,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 554acface537f0d2d1a43a854d7635596ed |
| SANs: *.synaplex.ai, synaplex.ai | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 skillfoundry.synaplex.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| synaplex.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://skillfoundry.synaplex.ai/products/preflight/mcp/ | Verified | 200 | |
| http (plaintext) | http://skillfoundry.synaplex.ai/products/preflight/mcp/ | Inconclusive | 405 |
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 →
check_publish_readiness ~130
Validate whether an MCP server is publishable on real directories (MCP Registry, Smithery, npm). Provide raw artifact contents. Returns evidence-backed findings with source-linked directory rules.
| Name | Type | Req | Description |
|---|---|---|---|
| manifest | string | – | Raw server.json content |
| package_json | string | – | Raw package.json content |
| pyproject_toml | string | – | Raw pyproject.toml content |
| readme | string | – | Raw README content |
| smithery_yaml | string | – | Raw smithery.yaml content |
| target_directories | array | – | Directories to check against. Defaults to all applicable. |
No output schema declared.
No examples provided.
What is the Preflight MCP server?
Preflight is an MCP server listed in the public MCP registry as io.github.evanfollis/preflight. Check if your MCP server is ready to publish on the MCP Registry, Smithery, or npm. This page covers its hosted endpoint (https://skillfoundry.synaplex.ai/products/preflight/mcp/).
Is the Preflight MCP server safe to use?
Preflight scores 73 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 MCP server expose?
Preflight exposes 1 tool: check_publish_readiness. Their descriptions and schemas cost roughly 130 tokens of context every time the server is loaded.
Does the Preflight MCP server require authentication?
No. We connected to Preflight without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Preflight MCP server still maintained?
Preflight is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.