Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

fuast

REMOTE · FUAST.COM

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

Available components

+3 this week 67 Trust /100

Last scanned (13 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +1
    • Schema quality: 2745 → 3047 ▼ functional
    • Server version: 2.2.0 → 2.3.0 functional
    • New tool “screenshot_app” functional
  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 63

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://fuast.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fuast.com CN=YR2,O=Let's Encrypt,C=US 22 Sept 2026 21 Dec 2026 RSA 2048 SHA256-RSA 603de963623c4dc242a73dba58554d3ac3c
SANs: fuast.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fuast.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
fuast.com. No DS 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://fuast.com/mcp Verified 200
http (plaintext) http://fuast.com/mcp HTTPS enforced 301 https://fuast.com/mcp
MCP tools · 20 exposed · ~2,956 tokens

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 →

Tool Tokens
call_app ~258

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.

NameTypeReqDescription
appstring–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.
asstring–Who the handler sees in ctx.auth. Default "me".
edit_tokenstring–The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
kindstringyesWhich kind of handler name is.
namestringyesHandler name as declared in server/index.ts.
NameTypeReqDescription
duration_msnumber––
kindstringyes–
logsarray––
namestringyes–
ran_asstringyes–
result–––
slugstring––
truncatedboolean––

No examples provided.

check_app ~122

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.

NameTypeReqDescription
filesobjectyesThe 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).
NameTypeReqDescription
codestring––
diagnosticsarray––
errorstring––
manifestobject––
msnumber––
namestring––
okbooleanyes–
sizesobject––
warningsarray––

No examples provided.

delete_app ~123

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.

NameTypeReqDescription
appstringyesThe 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.
confirmstringyesThe app's slug again, to confirm.
NameTypeReqDescription
deletedbooleanyes–
namestring––
slugstringyes–
warningsarray––

No examples provided.

deploy_app ~293

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.

NameTypeReqDescription
appstring–Slug of an existing app in the connected account to update. Leave out to create a new app.
delete_tablesarray–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_tokenstring–To update a preview that was deployed without an account: the edit_token that deploy returned.
filesobjectyesThe 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).
namestring–Name of a new app. Its address is derived from it. Ignored when updating an app.
NameTypeReqDescription
claim_urlstring––
createdboolean––
deploy_idstringyes–
edit_tokenstring––
expires_atstring––
limitsobject––
manifest–––
namestring––
next_stepsarrayyes–
preview_urlstring––
restrictedboolean––
restricted_hintstring––
slugstringyes–
trust_commandstring––
trust_urlstring––
unclaimedbooleanyes–
urlstringyes–
visibilitystring––

No examples provided.

fuast_docs ~109

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.

NameTypeReqDescription
pagestring–Page name from the list, for example "capsule-api" or "examples/todo".
searchstring–Words to find. Returns matching lines with their page and line number.
NameTypeReqDescription
markdownstring––
matchesarray––
pagestring––
pagesarray––
titlestring––
urlstring––

No examples provided.

fuast_guide ~82

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
guidestringyes–
pagesarray––

No examples provided.

get_app ~123

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.

NameTypeReqDescription
appstring–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_tokenstring–The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
NameTypeReqDescription
active_deploy_id–––
can_manageboolean––
claim_urlstring––
deploysarray––
env_keysarray––
expires_atstring––
last_deploy_at–––
manifest–––
namestring––
ownerstring––
preview_urlstring––
require_sign_inboolean––
restrictedboolean––
restricted_hintstring––
shared_witharray––
slugstringyes–
statusstringyes–
trust_commandstring––
trust_urlstring––
unclaimedboolean––
urlstringyes–
usageobject––
visibilitystring––

No examples provided.

get_app_source ~161

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.

NameTypeReqDescription
appstring–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_tokenstring–The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
pathsarray–Only return these files. Leave out for every file.
NameTypeReqDescription
deploy_idstringyes–
file_listarrayyes–
filesobjectyes–
namestring––
slugstringyes–
truncatedboolean––

No examples provided.

get_claim_link ~91

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.

NameTypeReqDescription
edit_tokenstringyesThe edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
NameTypeReqDescription
claim_urlstringyes–
deploy_id–––
expires_atstringyes–
namestring––
preview_urlstringyes–
slugstringyes–
statusstringyes–

No examples provided.

get_logs ~173

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.

NameTypeReqDescription
appstring–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_tokenstring–The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
levelstring–Lowest level to return. Default info.
limitinteger–Most entries to return. Default 50.
sinceinteger–Cursor from an earlier call: only entries after it.
NameTypeReqDescription
cursornumberyes–
entriesarrayyes–
slugstring––

No examples provided.

get_template ~88

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.

NameTypeReqDescription
idstringyesTemplate id from list_templates, for example todo.
namestring–Name for the new app. Sets the app's title and its letter icon.
NameTypeReqDescription
filesobjectyes–
idstringyes–
namestring––

No examples provided.

inspect_app ~226

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.

NameTypeReqDescription
appstring–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.
cursorstring–For rows: next_cursor from the previous page.
edit_tokenstring–The edit_token deploy_app returned when it deployed a preview without an account. It is a secret: keep it in this conversation only.
limitinteger–For rows and jobs: most items to return. Default 25.
tablestring–For rows: the table name.
whatstringyesWhat to read.
NameTypeReqDescription
is_doneboolean––
jobsobject––
manifestobject––
next_cursor–––
rowsarray––
schedulesarray––
slugstringyes–
tablesarray––
usageobject––
whatstringyes–

No examples provided.

list_apps ~46

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
appsarrayyes–

No examples provided.

list_templates ~37

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
templatesarrayyes–

No examples provided.

rollback_app ~120

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.

NameTypeReqDescription
appstringyesThe 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_idstring–The deploy to make live. Default: the previous ready deploy.
NameTypeReqDescription
active_deploy_idstringyes–
previous_deploy_id–––
slugstringyes–
urlstring––

No examples provided.

screenshot_app ~302

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.

NameTypeReqDescription
appstring–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.
darkboolean–The visitor's dark setting. Default light.
edit_tokenstring–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_pageboolean–The whole page, not only the first screen.
heightinteger–Window height in pixels, to override the default.
mobileboolean–A phone (390 by 844) instead of a desktop window (1280 by 800).
pathstring–The page, as a path from the app's root, like /orders or /orders/12?tab=open. Default /.
widthinteger–Window width in pixels, to override the default.
NameTypeReqDescription
errorsarrayyes–
heightnumberyes–
signed_in_as–––
slugstringyes–
titlestring––
urlstringyes–
widthnumberyes–

No examples provided.

set_env ~117

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.

NameTypeReqDescription
appstringyesThe 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.
setobject–Variables to set, as {"NAME": "value"}.
unsetarray–Names to remove.
NameTypeReqDescription
keysarrayyes–
setarray––
slugstringyes–
unsetarray––

No examples provided.

share_app ~164

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.

NameTypeReqDescription
appstringyesThe 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.
invitearray–Email addresses to give access to.
removearray–Email addresses to take off the access list.
visibilitystring–New sharing mode. Leave out to keep the current one.
NameTypeReqDescription
invitedarray––
removedarray––
shared_witharrayyes–
slugstringyes–
urlstringyes–
visibilitystringyes–

No examples provided.

update_app_files ~252

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.

NameTypeReqDescription
appstring–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_tablesarray–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_tokenstring–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_idstringyesThe deploy id your change is based on.
filesobjectyesChanges as {"path": "new content"} to write a file, {"path": null} to delete it.
NameTypeReqDescription
claim_urlstring––
createdboolean––
deploy_idstringyes–
edit_tokenstring––
expires_atstring––
limitsobject––
manifest–––
namestring––
next_stepsarrayyes–
preview_urlstring––
restrictedboolean––
restricted_hintstring––
slugstringyes–
trust_commandstring––
trust_urlstring––
unclaimedbooleanyes–
urlstringyes–
visibilitystring––

No examples provided.

whoami ~69

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
app–––
clientstring––
connected_throughstring––
emailstringyes–
email_verifiedboolean––
namestring––
scopesarrayyes–
workspaceobject––

No examples provided.

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.

remote · fuast.com

# add to Claude Code
claude mcp add --transport http com-fuast-fuast 'https://fuast.com/mcp'
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.