Is the Floot MCP server down?

mcp-registry/com.floot/floot · v1.0.0

healthy
Last checked 2026-10-18 05:45 UTC · handshake 343ms

As of 2026-10-18 05:45 UTC, the Floot MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,720
outages (90d)
0
tools
45

Build and publish full-stack web and mobile apps on Floot from any MCP client. Building is free.

Install Floot MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http floot-mcp-server https://mcp.floot.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "floot-mcp-server": {
      "type": "http",
      "url": "https://mcp.floot.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 5 warning(s) across 45 tool(s); ~12,557 tokens of tool definitions.
Scores higher than 7% of 15,352 MCP servers Glimind has audited.
Its tool list costs an agent ~12,557 tokens per session — more than 85% of servers.
71 → 71 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints100
Token cost64
Client compatibility70
Protocol100
Reliability85
Stability20

What to fix (7)

1 tool definition(s) exceed ~1,200 tokens each (largest: update_project_metadata, ~1,275).

Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~675 tokens every session. How to fix →

Tools: update_project_metadata · saves ~675 tokens/session

109 parameter(s) across 45 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: add_dependency, apply_patch, cancel_request, card_upload_asset, copy_file and 40 more

45 tools on one server. Tool-selection accuracy drops as the menu grows, and some clients (e.g. Cursor) cap the number of active tools.

Group tools by task into smaller servers or toolsets, and merge near-duplicates behind one tool with a mode parameter. How to fix →

Handshake + tools/list takes ~2,277 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

In the last 30 days: 1 tool(s) removed and 18 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Runs commands or code supplied by the model. Legitimate for dev tools; clients should require confirmation. Example (run_code_in_browser, name): "run_code_in_browser(code, projectId)"

Declare destructiveHint/readOnlyHint on these tools and say plainly in the description what runs, where, and with what limits. How to fix →

Tools: run_code_in_browser, run_code_in_vm

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.floot/floot"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.floot/floot"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.floot%2Ffloot.svg)](https://glimind.com/server/mcp-registry%2Fcom.floot%2Ffloot?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.floot%2Ffloot?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.floot%2Ffloot.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.floot%2Ffloot.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.floot%2Ffloot?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:0a2bc1dd2f04cd8b…, first seen 2026-10-17, included at leaf 1099 of 20,527. Version history · verify what your client received.

Tools (45)

Compare: most reliable code servers · most reliable files servers · most reliable other servers · most reliable database servers · most reliable retrieval servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Floot MCP server down right now?

As of 2026-10-18 05:45 UTC, the Floot MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Floot MCP server provide?

Floot MCP server advertises 45 tools, including add_dependency, apply_patch, cancel_request, card_upload_asset, copy_file.

How do I install Floot MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.floot.com/mcp

Is the Floot MCP server safe to connect to an AI agent?

Glimind scanned all 45 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Floot MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.