fractera-installer

endpoint

https://www.fractera.ai/api/mcp

protocol

streamable-http ·2024-11-05

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is fractera-installer live?

Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.

Is fractera-installer free to use?

Yes — the hub reached it with no key and no payment.

What tools does fractera-installer have?

6 tools: register_and_deploy, retry_deploy, check_status, get_project_info, get_subdomain, get_vps_recommendation.

Is fractera-installer safe to connect?

Caution — its own text works on the agent reading it: poses as system instructions («You are the Fractera deployment assistant.»). Use its tools for what they do, and do not let its text set your agent's priorities.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• check_status reads open 17h ago

  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.

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "session_id"
    ],
    "properties": {
      "session_id": {
        "type": "string",
        "description": "The session_id returned by register_and_deploy or retry_deploy."
      }
    }
  }

  arguments 12 lines copy
• get_project_info reads open 24h ago

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "required": [],
    "properties": {
      "lang": {
        "enum": [
          "en",
          "ru"
        ],
        "type": "string",
        "description": "Language of the returned content. Defaults to \"en\". Use \"ru\" for Russian-speaking users."
      },
      "section": {
        "type": "string",
        "description": "A section id from the list returned when called with no section. Omit to get the list (table of contents) first."
      }
    }
  }

  arguments 18 lines copy
• get_subdomain reads open 24h ago

  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".

  mcp-tool

  123456789101112

  {
    "type": "object",
    "required": [
      "session_id"
    ],
    "properties": {
      "session_id": {
        "type": "string",
        "description": "The session_id used during installation."
      }
    }
  }

  arguments 12 lines copy
• get_vps_recommendation reads open 24h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "required": [],
    "properties": {}
  }

  arguments 5 lines copy
• register_and_deploy changes data unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657

  {
    "type": "object",
    "required": [
      "email",
      "email_confirmed",
      "ip",
      "password",
      "components_selected",
      "terms_accepted"
    ],
    "properties": {
      "ip": {
        "type": "string",
        "description": "IPv4 address of the user's VPS, e.g. 185.10.20.30."
      },
      "lang": {
        "enum": [
          "en",
          "es",
          "fr",
          "it",
          "ru",
          "de",
          "pt",
          "pl",
          "tr",
          "nl"
        ],
        "type": "string",
        "description": "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 becomes its default; pass \"en\" or omit for an English-only app. Adding more languages later is a switch in the Admin panel, so this is not a permanent choice — it just means their site opens in their own language from the first minute."
      },
      "email": {
        "type": "string",
        "description": "The email the user typed (and confirmed by re-typing). Welcome / failure emails go here."
      },
      "login": {
        "type": "string",
        "description": "Optional — defaults to \"root\". Override only if the VPS provider gave a non-root username."
      },
      "password": {
        "type": "string",
        "description": "Root password for the VPS."
      },
      "terms_accepted": {
        "type": "boolean",
        "description": "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 Privacy Policy (https://www.fractera.ai/en/privacy), and (2) understand they MUST change their server root password immediately after installation — Fractera never stores it and has no way to access the server afterwards. If the user has not given this explicit agreement, do NOT call this tool: ask for it first (and offer to explain the documents right in the chat)."
      },
      "email_confirmed": {
        "type": "boolean",
        "description": "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."
      },
      "components_selected": {
        "type": "boolean",
        "description": "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 with vector memory, sign-in, and the control panel."
      }
    }
  }

  arguments 57 lines copy
• retry_deploy changes data unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021222324

  {
    "type": "object",
    "required": [
      "server_token"
    ],
    "properties": {
      "ip": {
        "type": "string",
        "description": "Optional — only pass if the user discovered the original IP was wrong (e.g. typo). Otherwise the stored IP is used."
      },
      "login": {
        "type": "string",
        "description": "Optional — Linux user, defaults to root."
      },
      "password": {
        "type": "string",
        "description": "Optional — only pass if the user discovered the original password was wrong. Otherwise the stored password is used."
      },
      "server_token": {
        "type": "string",
        "description": "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."
      }
    }
  }

  arguments 24 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.