Fractera
REMOTE · WWW.FRACTERA.AI · SCANNED SEP 26
Zero-Ops deploy of a private AI workspace to your own VPS — from your AI chat. Free and open-source.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (register_and_deploy). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability56
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4875 tokens (~812/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Fractera MCP server?
Fractera is a hosted endpoint at https://www.fractera.ai/api/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 · www.fractera.ai
claude mcp add --transport http fractera-deploy 'https://www.fractera.ai/api/mcp'
{
"mcpServers": {
"fractera-deploy": {
"url": "https://www.fractera.ai/api/mcp"
}
}
} {
"servers": {
"fractera-deploy": {
"type": "http",
"url": "https://www.fractera.ai/api/mcp"
}
}
} [mcp_servers.fractera-deploy] url = "https://www.fractera.ai/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fractera-deploy": {
"type": "remote",
"url": "https://www.fractera.ai/api/mcp",
"enabled": true
}
}
} openclaw mcp add fractera-deploy --url 'https://www.fractera.ai/api/mcp' --transport streamable-http
mcp_servers:
fractera-deploy:
url: "https://www.fractera.ai/api/mcp" {
"McpServers": {
"fractera-deploy": {
"Transport": "http",
"Url": "https://www.fractera.ai/api/mcp"
}
}
} assistant mcp add fractera-deploy -t streamable-http -u 'https://www.fractera.ai/api/mcp'
{
"mcpServers": {
"fractera-deploy": {
"type": "http",
"url": "https://www.fractera.ai/api/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
- 17 Sept 26 +4
- Stability: fail → pass ▲ security
- 12 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 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
- 18 Aug 26 0
- Stability: 0.73 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “get_ai_development_loop_info” was removed ▼ security
- Tool “get_ai_workspace_architect_info” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 680 → 812 ▼ functional
- “register_and_deploy” added an optional parameter “lang” cosmetic
- “register_and_deploy” reworded the description of “components_selected” cosmetic
- “register_and_deploy” dropped the optional parameter “components” cosmetic
- “retry_deploy” dropped the optional parameter “components” cosmetic
- 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
- 8 Aug 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: excellent → poor functional
- “register_and_deploy” reworded the description of “components” cosmetic
- 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
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 26 Sept 2026 · Probed https://www.fractera.ai/api/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.fractera.ai | CN=WE1,O=Google Trust Services,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | f8fc15d48c8ecd281395f0f8a7161f5f |
| SANs: www.fractera.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.fractera.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| fractera.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | frame-ancestors 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.fractera.ai/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.fractera.ai/api/mcp | HTTPS enforced | 308 | https://www.fractera.ai/api/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 →
check_status Check Deployment Status ~134
Read the current installation progress ONCE, on demand. Call this only when the user explicitly asks how the deploy is going (e.g. "what is the status", "did it finish") — never on a timer and never in a polling loop. The deploy takes 8-14 minutes and the authoritative status channels are the email pipeline + the dashboard; one read on request is enough. Returns the current step, the list of completed steps (~44 total in a full bootstrap), and whether installation is done or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id returned by register_and_deploy or retry_deploy. |
No output schema declared.
No examples provided.
get_project_info Get Project Information ~200
Project reference / help desk about Fractera. Use this to answer ANY user question about what Fractera is, how it works, its architecture, components, modes, data ownership, pricing, use cases, partner program, etc. — especially while a deploy is running and the user wants to learn more. TOKEN-ECONOMY: call with NO arguments first to get the lightweight list of section ids+titles, then call again with a single `section` id to fetch just that section. NEVER try to fetch everything at once; pull only the section(s) relevant to the user question. Set `lang:"ru"` for Russian-speaking users.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the returned content. Defaults to "en". Use "ru" for Russian-speaking users. |
| section | string | – | A section id from the list returned when called with no section. Omit to get the list (table of contents) first. |
No output schema declared.
No examples provided.
get_subdomain Get Workspace Address ~106
Return the final entry address of the server once installation is complete. In phase-1 (IP-first) this is a plain-HTTP Admin URL of the form http://<IP>:3002 — the server has NO domain and NO HTTPS cert yet (attaching a custom domain with HTTPS is an optional later step the user does inside Admin -> Personal Domain). Call this once after check_status reports status="done".
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session_id used during installation. |
No output schema declared.
No examples provided.
get_vps_recommendation Get VPS Recommendation ~57
Return a single recommended VPS provider for users who do not yet have a server. Call this ONLY when the user explicitly says they have no server. The user buys the VPS at this provider and comes back with IP + password.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register_and_deploy Deploy Fractera Workspace ~626
Register a new Fractera user and start the deployment of their server in one atomic call. Use this AFTER you have collected the user's email (entered twice for typo protection), server IP, and root password. Creates the User row (or reuses an existing one with the same email), creates a free Subscription, creates a ServerToken, wipes any previous installation on the target server, and launches bootstrap. The deploy is IP-first (phase-1): the server comes up on plain HTTP at http://<IP>:3002 in 8-14 minutes; it does NOT get a domain or HTTPS cert here (that is an optional later step inside the workspace). Returns session_id (for a single on-demand check_status read — do not poll) and server_token (so the user can recover via retry_deploy if anything breaks). Call this AT MOST ONCE per conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| components_selected | boolean | yes | REQUIRED, must be true. Nothing is selectable any more — every server gets the same set — so this only records that you TOLD the user what gets installed (Q5): the app, the database and file storage… |
| string | yes | The email the user typed (and confirmed by re-typing). Welcome / failure emails go here. | |
| email_confirmed | boolean | yes | REQUIRED, must be true. Set this ONLY after the user has typed their email a SECOND time (Q2) and the two entries match (case-insensitive, trimmed). Do not set it if you only asked once. |
| ip | string | yes | IPv4 address of the user's VPS, e.g. 185.10.20.30. |
| lang | string | – | Optional — the two-letter code of the language the user is talking to you in (e.g. "ru" if the conversation is in Russian). Their new app is built in English PLUS this language, and this language bec… |
| login | string | – | Optional — defaults to "root". Override only if the VPS provider gave a non-root username. |
| password | string | yes | Root password for the VPS. |
| terms_accepted | boolean | yes | REQUIRED, must be true. Set this ONLY after the user has explicitly confirmed in the chat that they (1) have read and agree to Fractera's Terms of Service (https://www.fractera.ai/en/terms) and Priva… |
No output schema declared.
No examples provided.
retry_deploy Retry Failed Deployment ~188
Retry a failed deployment using a server_token (from the failure email, the deploy-progress UI, or the dashboard). Wipes the previous broken install and runs a fresh deploy on the SAME server. Returns a new session_id — poll with check_status. Use this when the user reports a failed deploy or pastes a server_token.
| Name | Type | Req | Description |
|---|---|---|---|
| ip | string | – | Optional — only pass if the user discovered the original IP was wrong (e.g. typo). Otherwise the stored IP is used. |
| login | string | – | Optional — Linux user, defaults to root. |
| password | string | – | Optional — only pass if the user discovered the original password was wrong. Otherwise the stored password is used. |
| server_token | string | yes | The unique server token the user received in the deploy-failure email, the active deploy UI, or the dashboard. Acts as the authorisation for this retry. |
No output schema declared.
No examples provided.
What is the Fractera MCP server?
Fractera is an MCP server listed in the public MCP registry as io.github.Fractera/deploy. Zero-Ops deploy of a private AI workspace to your own VPS, from your AI chat. Free and open-source. This page covers its hosted endpoint (https://www.fractera.ai/api/mcp).
Is the Fractera MCP server safe to use?
Fractera scores 74 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 Fractera MCP server expose?
Fractera exposes 6 tools: register_and_deploy, check_status, get_subdomain, retry_deploy, get_vps_recommendation, get_project_info. Their descriptions and schemas cost roughly 1,311 tokens of context every time the server is loaded.
Does the Fractera MCP server require authentication?
No. We connected to Fractera without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fractera MCP server still maintained?
Fractera is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.