# fuast (remote · fuast.com)

Build, deploy and share small full-stack team apps from your AI chat. No account needed to start.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `fuast.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-fuast-fuast/fuast.md), [page](https://verifymcp.io/servers/com-fuast-fuast/fuast)

## Channel facts

- Endpoint: `https://fuast.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (deploy_app).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3047 tokens (~152/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the fuast MCP server?

fuast is a hosted endpoint at https://fuast.com/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.

### Claude

```bash
claude mcp add --transport http com-fuast-fuast 'https://fuast.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-fuast-fuast": {
      "url": "https://fuast.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-fuast-fuast": {
      "type": "http",
      "url": "https://fuast.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-fuast-fuast]
url = "https://fuast.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-fuast-fuast": {
      "type": "remote",
      "url": "https://fuast.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-fuast-fuast --url 'https://fuast.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-fuast-fuast:
    url: "https://fuast.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-fuast-fuast": {
      "Transport": "http",
      "Url": "https://fuast.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-fuast-fuast -t streamable-http -u 'https://fuast.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-fuast-fuast": {
      "type": "http",
      "url": "https://fuast.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 65, +1)

- [functional regression] Schema quality: 2745 → 3047
- [functional] Server version: 2.2.0 → 2.3.0
- [functional] New tool “screenshot_app”

### 2026-11-13 (score 64, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 63)

First indexed and scored.

## MCP tools (20)

### `fuast_guide` (~82 tokens)

Read the fuast guide

Call this first. Returns how to build, check, deploy and share a fuast app with these tools, and the rules a fuast app must follow (file layout, server and client APIs, database, auth, UI). fuast apps are small full-stack TypeScript apps called capsules: server/index.ts and client/index.tsx, no npm packages.

Output parameters:

- `guide` (string)
- `pages` (array)

### `fuast_docs` (~109 tokens)

Read or search the fuast docs

Read one docs page as markdown (page), or search every page for words (search). With neither, lists the pages. Useful pages: capsule-api (every server and client API), database, auth, limits, storage, schedules, email, teams, examples/todo.

Input parameters:

- `page` (string): Page name from the list, for example "capsule-api" or "examples/todo".
- `search` (string): Words to find. Returns matching lines with their page and line number.

Output parameters:

- `markdown` (string)
- `matches` (array)
- `page` (string)
- `pages` (array)
- `title` (string)
- `url` (string)

### `list_templates` (~37 tokens)

List starter templates

Lists the working starter apps a new fuast app can begin from, with what each one demonstrates. Get a template's files with get_template.

Output parameters:

- `templates` (array)

### `get_template` (~88 tokens)

Get a template's files

Returns the source files of one starter template as {path: content}: a complete app that passes check_app and can be sent to deploy_app as is. Change the files to build what the person asked for.

Input parameters:

- `id` (string, required): Template id from list_templates, for example todo.
- `name` (string): Name for the new app. Sets the app's title and its letter icon.

Output parameters:

- `files` (object)
- `id` (string)
- `name` (string)

### `check_app` (~122 tokens)

Check an app without deploying

Builds the files, type checks them and loads the server in a sandbox, without deploying anything. Returns ok with the queries, mutations, tables and tools the app declares, or ok false with diagnostics that carry file, line and message. Call it before deploy_app and fix every diagnostic.

Input parameters:

- `files` (object, required): The whole app as {"relative/path": "file content"}. server/index.ts and client/index.tsx are required. Text files only (.ts .tsx .js .jsx .mjs .json .md .svg .txt .css .html).

Output parameters:

- `code` (string)
- `diagnostics` (array)
- `error` (string)
- `manifest` (object)
- `ms` (number)
- `name` (string)
- `ok` (boolean)
- `sizes` (object)
- `warnings` (array)

### `deploy_app` (~293 tokens)

Deploy an app

Deploys the files and returns the app's URL. With a connected fuast account it creates a new private app in the person's workspace, or updates the app named in app. Without an account it deploys a temporary preview and returns preview_url, claim_url and edit_token: give the person claim_url so they can make the app theirs, and pass edit_token to later calls to keep working on it. Send every file each time; use update_app_files to change a few. A failed build returns diagnostics with file and line and deploys nothing.

Input parameters:

- `app` (string): Slug of an existing app in the connected account to update. Leave out to create a new app.
- `delete_tables` (array): Only when a deploy was refused because the new schema drops tables that hold rows: repeat each table with the exact row count from that error to confirm deleting it.
- `edit_token` (string): To update a preview that was deployed without an account: the edit_token that deploy returned.
- `files` (object, required): The whole app as {"relative/path": "file content"}. server/index.ts and client/index.tsx are required. Text files only (.ts .tsx .js .jsx .mjs .json .md .svg .txt .css .html).
- `name` (string): Name of a new app. Its address is derived from it. Ignored when updating an app.

Output parameters:

- `claim_url` (string)
- `created` (boolean)
- `deploy_id` (string)
- `edit_token` (string)
- `expires_at` (string)
- `limits` (object)
- `manifest`
- `name` (string)
- `next_steps` (array)
- `preview_url` (string)
- `restricted` (boolean)
- `restricted_hint` (string)
- `slug` (string)
- `trust_command` (string)
- `trust_url` (string)
- `unclaimed` (boolean)
- `url` (string)
- `visibility` (string)

### `get_app_source` (~161 tokens)

Get an app's source files

Returns the source of the app's live deploy as {path: content}, with the deploy id to pass to update_app_files as expected_deploy_id. Large apps return the file list only: ask again with paths for the files you need. Secrets (.env files, env values) are never returned.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
- `paths` (array): Only return these files. Leave out for every file.

Output parameters:

- `deploy_id` (string)
- `file_list` (array)
- `files` (object)
- `name` (string)
- `slug` (string)
- `truncated` (boolean)

### `update_app_files` (~252 tokens)

Change some of an app's files

Redeploys the app with a few files changed: files maps each path to its new content, or to null to delete it. Every other file stays as it is. expected_deploy_id must be the app's live deploy (from get_app_source or the last deploy result); if someone deployed in between, nothing changes and you are told to read the source again. Builds and type checks like deploy_app.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `delete_tables` (array): Only when a deploy was refused because the new schema drops tables that hold rows: repeat each table with the exact row count from that error to confirm deleting it.
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
- `expected_deploy_id` (string, required): The deploy id your change is based on.
- `files` (object, required): Changes as {"path": "new content"} to write a file, {"path": null} to delete it.

Output parameters:

- `claim_url` (string)
- `created` (boolean)
- `deploy_id` (string)
- `edit_token` (string)
- `expires_at` (string)
- `limits` (object)
- `manifest`
- `name` (string)
- `next_steps` (array)
- `preview_url` (string)
- `restricted` (boolean)
- `restricted_hint` (string)
- `slug` (string)
- `trust_command` (string)
- `trust_url` (string)
- `unclaimed` (boolean)
- `url` (string)
- `visibility` (string)

### `list_apps` (~46 tokens)

List my apps

Lists the fuast apps the connected account can use: its own, its workspace's, and apps shared with it, with URL, sharing mode and whether the account can manage each one.

Output parameters:

- `apps` (array)

### `get_app` (~123 tokens)

Get an app's status

Returns one app: URL, status, sharing, handlers, recent deploys with their ids (for rollback_app), today's usage and limits, and the names (never the values) of its env vars.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.

Output parameters:

- `active_deploy_id`
- `can_manage` (boolean)
- `claim_url` (string)
- `deploys` (array)
- `env_keys` (array)
- `expires_at` (string)
- `last_deploy_at`
- `manifest`
- `name` (string)
- `owner` (string)
- `preview_url` (string)
- `require_sign_in` (boolean)
- `restricted` (boolean)
- `restricted_hint` (string)
- `shared_with` (array)
- `slug` (string)
- `status` (string)
- `trust_command` (string)
- `trust_url` (string)
- `unclaimed` (boolean)
- `url` (string)
- `usage` (object)
- `visibility` (string)

### `get_logs` (~173 tokens)

Read an app's logs

Returns recent log entries of an app, oldest first: what its handlers wrote with ctx.log, handler errors with stack traces, and platform events such as deploys. Pass the returned cursor as since to read only newer entries.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
- `level` (string): Lowest level to return. Default info.
- `limit` (integer): Most entries to return. Default 50.
- `since` (integer): Cursor from an earlier call: only entries after it.

Output parameters:

- `cursor` (number)
- `entries` (array)
- `slug` (string)

### `screenshot_app` (~302 tokens)

Take a picture of an app

Opens one page of a deployed app in a browser and returns a picture of it, with any errors the page reported while it loaded. Use it after a deploy to see what a person will see, which rows and logs cannot show: a blank page, a broken layout, text that does not fit. A preview deployed without an account is shown as a guest. An app in the account is shown signed in as the connected person. Only for apps the person owns or administers.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `dark` (boolean): The visitor's dark setting. Default light.
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
- `full_page` (boolean): The whole page, not only the first screen.
- `height` (integer): Window height in pixels, to override the default.
- `mobile` (boolean): A phone (390 by 844) instead of a desktop window (1280 by 800).
- `path` (string): The page, as a path from the app's root, like /orders or /orders/12?tab=open. Default /.
- `width` (integer): Window width in pixels, to override the default.

Output parameters:

- `errors` (array)
- `height` (number)
- `signed_in_as`
- `slug` (string)
- `title` (string)
- `url` (string)
- `width` (number)

### `inspect_app` (~226 tokens)

Inspect an app

Reads one thing about a deployed app. manifest: handlers, schema, indexes, endpoints, read metrics. tables: each table with its fields and row count. rows: rows of one table (give table; at most 100 per call, continue with cursor). usage: today's counters and limits. schedules: cron schedules and their last runs. jobs: scheduled jobs. Only the app's owner and workspace admins can inspect.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `cursor` (string): For rows: next_cursor from the previous page.
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
- `limit` (integer): For rows and jobs: most items to return. Default 25.
- `table` (string): For rows: the table name.
- `what` (string, required): What to read.

Output parameters:

- `is_done` (boolean)
- `jobs` (object)
- `manifest` (object)
- `next_cursor`
- `rows` (array)
- `schedules` (array)
- `slug` (string)
- `tables` (array)
- `usage` (object)
- `what` (string)

### `call_app` (~258 tokens)

Run a handler of an app

Runs one query, mutation or action of a deployed app and returns its result and the log lines it wrote, so you can test what you deployed. It runs as the connected person (as: "me", the default), never as anyone else; as: "guest" runs it as a guest visitor and only works on public apps. On a preview deployed without an account every call runs as one guest. Mutations and actions change real data. Only for apps the person owns or administers.

Input parameters:

- `app` (string): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `args`: Arguments: an array of positional values, or one object for handlers that take an object (tool handlers). Default: no arguments.
- `as` (string): Who the handler sees in ctx.auth. Default "me".
- `edit_token` (string): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
- `kind` (string, required): Which kind of handler name is.
- `name` (string, required): Handler name as declared in server/index.ts.

Output parameters:

- `duration_ms` (number)
- `kind` (string)
- `logs` (array)
- `name` (string)
- `ran_as` (string)
- `result`
- `slug` (string)
- `truncated` (boolean)

### `share_app` (~164 tokens)

Share an app

Changes who can open an app. visibility: private (the owner and invited people), workspace (everyone at the owner's company), or public (anyone with the link, guests included). invite adds people by email and sends each an email; remove takes people off the list. Do this only when the person asks for it. Returns the resulting sharing.

Input parameters:

- `app` (string, required): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `invite` (array): Email addresses to give access to.
- `remove` (array): Email addresses to take off the access list.
- `visibility` (string): New sharing mode. Leave out to keep the current one.

Output parameters:

- `invited` (array)
- `removed` (array)
- `shared_with` (array)
- `slug` (string)
- `url` (string)
- `visibility` (string)

### `set_env` (~117 tokens)

Set an app's server secrets

Sets or removes environment variables of an app (read in handlers as ctx.env.NAME). They take effect at once, without a deploy. Values are write-only: no tool returns them, only the names.

Input parameters:

- `app` (string, required): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `set` (object): Variables to set, as {"NAME": "value"}.
- `unset` (array): Names to remove.

Output parameters:

- `keys` (array)
- `set` (array)
- `slug` (string)
- `unset` (array)

### `rollback_app` (~120 tokens)

Roll an app back to an earlier deploy

Makes an earlier deploy of the app live again. deploy_id comes from get_app; without it, the most recent earlier deploy that is ready. The app's data stays as it is; if that deploy's schema cannot hold the current data, nothing changes.

Input parameters:

- `app` (string, required): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `deploy_id` (string): The deploy to make live. Default: the previous ready deploy.

Output parameters:

- `active_deploy_id` (string)
- `previous_deploy_id`
- `slug` (string)
- `url` (string)

### `delete_app` (~123 tokens)

Delete an app for good

Deletes an app and everything in it: its data, stored files, deploys, schedules and custom domains. This cannot be undone. Only the app's owner can do it, and confirm must repeat the app's slug. Do this only when the person explicitly asks for the app to be deleted.

Input parameters:

- `app` (string, required): The app's slug: the first label of its address (my-app for https://my-app.fuast.com). list_apps shows the slugs you can use.
- `confirm` (string, required): The app's slug again, to confirm.

Output parameters:

- `deleted` (boolean)
- `name` (string)
- `slug` (string)
- `warnings` (array)

### `get_claim_link` (~91 tokens)

Get a preview's claim link

For a preview that deploy_app deployed without an account: returns the claim link to give to the person, the preview link, and when the preview is deleted if nobody claims it. Opening the claim link and signing in makes the app theirs.

Input parameters:

- `edit_token` (string, required): The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.

Output parameters:

- `claim_url` (string)
- `deploy_id`
- `expires_at` (string)
- `name` (string)
- `preview_url` (string)
- `slug` (string)
- `status` (string)

### `whoami` (~69 tokens)

Show the connected fuast account

Returns the fuast account this connection acts as: email, workspace, role, and what the connection may do. If no account is connected yet, calling it starts sign-in: call it when the person has a fuast account or wants apps deployed into their own workspace instead of as a temporary preview.

Output parameters:

- `app`
- `client` (string)
- `connected_through` (string)
- `email` (string)
- `email_verified` (boolean)
- `name` (string)
- `scopes` (array)
- `workspace` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-fuast-fuast/fuast#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 66
- 2026-11-18: 66
- 2026-11-17: 66
- 2026-11-16: 65
- 2026-11-15: 65
- 2026-11-14: 64
- 2026-11-13: 64
- 2026-11-12: 63

## Common questions

### What is the fuast MCP server?

fuast is an MCP server listed in the public MCP registry as com.fuast/fuast. Build, deploy and share small full-stack team apps from your AI chat. No account needed to start. This page covers its hosted endpoint (https://fuast.com/mcp).

### Is the fuast MCP server safe to use?

fuast scores 67 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 fuast MCP server expose?

fuast exposes 20 tools: fuast_guide, fuast_docs, list_templates, get_template, check_app, and 15 more. Their descriptions and schemas cost roughly 2,956 tokens of context every time the server is loaded.

### Does the fuast MCP server require authentication?

No. We connected to fuast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the fuast MCP server still maintained?

fuast is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the fuast MCP server?

VerifyMCP ran 13 checks on fuast, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://fuast.com/mcp
- Website: https://fuast.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/com-fuast-fuast/fuast.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-fuast-fuast/fuast/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-fuast-fuast/fuast.json
- HTML version of this page: https://verifymcp.io/servers/com-fuast-fuast/fuast
