# io.github.floomhq/floom (npm · @floomhq/mcp-server)

Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.

- Trust score: 69/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-04

## Components

- npm · `@floomhq/mcp-server`: 69/100 (this document), [markdown](https://verifymcp.io/servers/floomhq-floom/floomhq-mcp-server.md), [page](https://verifymcp.io/servers/floomhq-floom/floomhq-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@floomhq/mcp-server`
- Version: `0.1.6`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-08-04.

- **Supply Chain Security**: 83/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known medium-severity CVE affects hono 4.12.33, reached via @modelcontextprotocol/sdk > hono. A fixed version is available.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (96 of 100), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 123 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1744 tokens (~54/item across 32 items; 32 tools + 0 resources), lean.
  - 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add floomhq-floom -- npx -y @floomhq/mcp-server
```

### Codex

```bash
codex mcp add floomhq-floom -- npx -y @floomhq/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "floomhq-floom": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@floomhq/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add floomhq-floom --command npx --arg -y --arg @floomhq/mcp-server
```

### Hermes

```yaml
mcp_servers:
  floomhq-floom:
    command: "npx"
    args: ["-y", "@floomhq/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "floomhq-floom": {
      "command": "npx",
      "args": [
        "-y",
        "@floomhq/mcp-server"
      ]
    }
  }
}
```

## 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-08-04 (score 69, −1)

- [security regression] CVE-2026-69207 affects this package: medium
- [security regression] Known CVEs: partial → fail

### 2026-08-03 (score 70, +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-08-02 (score 69, +49)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 20, −1)

- [security improvement] Malware scan: unverified → pass
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-31 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (32)

### `deploy` (~133 tokens)

Deploy Python code to Floom and get a usable URL. Accepts raw Python source or a base64-encoded ZIP. Optionally include a floom.yaml config to declare endpoint schemas, secrets, and resource requirements.

Input parameters:

- `code` (string, required): Python source code or base64-encoded ZIP bundle
- `config` (object): floom.yaml configuration: declare endpoint schemas, required secrets, and resource settings
- `name` (string, required): Project name (lowercase, hyphens allowed)
- `requirements` (array): Python package requirements (e.g. ["requests==2.31.0", "pandas"])

### `run` (~203 tokens)

Execute an action on a deployed Floom app. Preferred: use app_slug + action for simple invocation. Alternative: use project_id + endpoint_id + version_id for explicit control.

Input parameters:

- `action` (string): Action name (e.g. "count", "generate"). Used with app_slug.
- `app_slug` (string): App slug for simple invocation (e.g. "my-app")
- `callback_url` (string): URL to receive a POST with the run result when it completes (webhook)
- `endpoint_id` (string): Endpoint ID (e.g. "post--generate_invoice"). Used with project_id.
- `json` (object): JSON body to send to the endpoint
- `params` (object): Query parameters
- `project_id` (string): Project ID (alternative to app_slug)
- `timeout_seconds` (number): Max execution time in seconds (default 60)
- `version_id` (string): Version ID. Used with project_id.

### `list_projects` (~15 tokens)

List all deployed Floom projects.

### `get_project` (~45 tokens)

Get details for a Floom project including endpoint schemas and input parameters. Use this before calling run to see what inputs an endpoint expects.

Input parameters:

- `project_id` (string, required): Project ID

### `manage_secrets` (~73 tokens)

Manage secrets for a Floom project. Supports list, set, and delete operations.

Input parameters:

- `action` (string, required): Action to perform
- `key` (string): Secret key (required for set/delete)
- `project_id` (string, required): Project ID
- `value` (string): Secret value (required for set)

### `get_logs` (~45 tokens)

Get recent run logs for a Floom project.

Input parameters:

- `limit` (number): Number of recent runs to fetch (default 10)
- `project_id` (string, required): Project ID

### `list_versions` (~44 tokens)

List all versions of a Floom project. Shows which version is dev (latest deploy) and which is prod (promoted).

Input parameters:

- `project_id` (string, required): Project ID

### `promote` (~63 tokens)

Promote a version to production. By default promotes the current dev version. Runs a health check; auto-rolls back if the check fails.

Input parameters:

- `project_id` (string, required): Project ID
- `version_id` (string): Version ID to promote (defaults to current dev version)

### `rollback` (~38 tokens)

Rollback production to a previous version.

Input parameters:

- `project_id` (string, required): Project ID
- `version_id` (string, required): Version ID to rollback to

### `storage_set` (~78 tokens)

Store a persistent key-value pair for a Floom project. Values persist across runs and deploys.

Input parameters:

- `key` (string, required): Storage key (alphanumeric, dots, underscores, hyphens; max 256 chars)
- `project_id` (string, required): Project ID
- `value`: Value to store (any JSON-serializable data)

### `storage_get` (~37 tokens)

Retrieve a stored value for a Floom project.

Input parameters:

- `key` (string, required): Storage key
- `project_id` (string, required): Project ID

### `storage_delete` (~37 tokens)

Delete a stored value for a Floom project.

Input parameters:

- `key` (string, required): Storage key
- `project_id` (string, required): Project ID

### `storage_list` (~31 tokens)

List all stored keys for a Floom project with usage info.

Input parameters:

- `project_id` (string, required): Project ID

### `create_share_link` (~61 tokens)

Create a public share link for a Floom endpoint. Share links allow anyone to run the endpoint without authentication.

Input parameters:

- `endpoint_id` (string, required): Endpoint ID to share (e.g. "post--generate")
- `project_id` (string, required): Project ID

### `list_share_links` (~29 tokens)

List all share links for a Floom project.

Input parameters:

- `project_id` (string, required): Project ID

### `disable_share_link` (~50 tokens)

Disable a share link for a Floom project. The link will no longer be accessible.

Input parameters:

- `project_id` (string, required): Project ID
- `share_id` (string, required): Share link ID to disable

### `fetch_context` (~72 tokens)

Fetch external data from a URL and attach it as context to a Floom project. Context data enhances AI-powered endpoints.

Input parameters:

- `name` (string, required): Context name (alphanumeric, hyphens, underscores)
- `project_id` (string, required): Project ID
- `url` (string, required): URL to fetch context from

### `list_contexts` (~29 tokens)

List all context entries for a Floom project.

Input parameters:

- `project_id` (string, required): Project ID

### `delete_context` (~40 tokens)

Remove a context entry from a Floom project.

Input parameters:

- `context_id` (string, required): Context ID to remove
- `project_id` (string, required): Project ID

### `delete_project` (~38 tokens)

Delete a Floom project and all its data (versions, runs, secrets, storage).

Input parameters:

- `project_id` (string, required): Project ID to delete

### `update_project` (~47 tokens)

Update a Floom project name or slug.

Input parameters:

- `name` (string): New project name
- `project_id` (string, required): Project ID
- `slug` (string): New project slug

### `deploy_from_github` (~73 tokens)

Deploy a Floom app directly from a GitHub repository URL.

Input parameters:

- `github_ref` (string): Branch or tag to deploy (default: main)
- `github_url` (string, required): GitHub repository URL (e.g. "https://github.com/user/repo")
- `name` (string, required): Project name

### `list_templates` (~17 tokens)

List available starter templates for Floom projects.

### `get_template` (~30 tokens)

Get details and code preview for a Floom starter template.

Input parameters:

- `template_id` (string, required): Template ID

### `create_from_template` (~47 tokens)

Create a new Floom project from a starter template.

Input parameters:

- `name` (string): Project name (defaults to template name)
- `template_id` (string, required): Template ID to create from

### `get_context` (~38 tokens)

Retrieve stored context data for a Floom project.

Input parameters:

- `context_id` (string, required): Context ID
- `project_id` (string, required): Project ID

### `refresh_context` (~39 tokens)

Re-fetch context data from its source URL.

Input parameters:

- `context_id` (string, required): Context ID to refresh
- `project_id` (string, required): Project ID

### `create_schedule` (~141 tokens)

Create a cron schedule that automatically runs an endpoint at specified intervals.

Input parameters:

- `cron` (string, required): Cron expression (e.g. "*/5 * * * *" for every 5 minutes, "0 9 * * *" for daily at 9am)
- `endpoint_id` (string, required): Endpoint ID to schedule (e.g. "post--generate")
- `input` (object): JSON input to pass to the endpoint on each run
- `project_id` (string, required): Project ID
- `timeout_seconds` (number): Max execution time per run (default: 60)
- `timezone` (string): IANA timezone (default: UTC)

### `list_schedules` (~29 tokens)

List all cron schedules for a Floom project.

Input parameters:

- `project_id` (string, required): Project ID

### `delete_schedule` (~40 tokens)

Delete a cron schedule from a Floom project.

Input parameters:

- `project_id` (string, required): Project ID
- `schedule_id` (string, required): Schedule ID to delete

### `enable_webhooks` (~52 tokens)

Enable public inbound webhooks for a Floom project. Once enabled, external services can trigger runs via POST /v1/webhooks/:slug/:action without authentication.

Input parameters:

- `project_id` (string, required): Project ID

### `disable_webhooks` (~30 tokens)

Disable public inbound webhooks for a Floom project.

Input parameters:

- `project_id` (string, required): Project ID

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/floomhq-floom/floomhq-mcp-server#diagnostics

## Score history

- 2026-08-04: 69
- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 20
- 2026-07-31: 21
- 2026-07-30: 28
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@floomhq/mcp-server
- Socket report: https://socket.dev/npm/package/@floomhq/mcp-server
- Repository: https://github.com/floomhq/floom
- Changelog RSS feed: https://verifymcp.io/servers/floomhq-floom/floomhq-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/floomhq-floom/floomhq-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/floomhq-floom/floomhq-mcp-server