# Phlow MCP Server (mcpb · linux-x64)

MCP server for the phlow agent runtime: bounded planner-coder-reviewer agent workflows.

- Trust score: 34/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- mcpb · `linux-x64`: 34/100 (this document), [markdown](https://verifymcp.io/servers/ai-qompass-phlow/phlow-mcp-linux-x64.md), [page](https://verifymcp.io/servers/ai-qompass-phlow/phlow-mcp-linux-x64)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/qompassai/phlow/releases/download/v0.2.1/phlow-mcp-0.2.1-linux-x64.mcpb`
- Transport: `stdio`
- SHA-256: `781d47a91799c0b74299e7f93afad1fbcb09c306aa5c18e4951dc9e9952b5801`

## 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-10-24.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: we found no dependency list to check in this bundle: either it runs a compiled binary, whose bundled manifests we do not read, or none of the package.json, requirements.txt, pyproject.toml or uv.lock files it ships for its runtime declares a dependency we can read (a requirements.txt that only points at a setup.py project, a local path, or a nested requirements file we cannot follow counts as none).
- **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 (Apache-2.0).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 225 tokens (~32/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "flow_attention_publish" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 8 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).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Phlow MCP Server server?

Phlow MCP Server ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 781d47a91799c0b74299e7f93afad1fbcb09c306aa5c18e4951dc9e9952b5801; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/qompassai/phlow/releases/download/v0.2.1/phlow-mcp-0.2.1-linux-x64.mcpb`
- SHA-256: `781d47a91799c0b74299e7f93afad1fbcb09c306aa5c18e4951dc9e9952b5801`

### Verify on macOS / Linux

```bash
echo "781d47a91799c0b74299e7f93afad1fbcb09c306aa5c18e4951dc9e9952b5801  phlow-mcp-0.2.1-linux-x64.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\phlow-mcp-0.2.1-linux-x64.mcpb).Hash -eq "781d47a91799c0b74299e7f93afad1fbcb09c306aa5c18e4951dc9e9952b5801"
```

## 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-10-23 (score 34, +1)

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

### 2026-10-21 (score 33, +1)

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

### 2026-10-20 (score 32, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-19 (score 32)

First indexed and scored.

## MCP tools (7)

### `flow_run` (~28 tokens)

Bounded local planner/coder/reviewer run with real verification

Input parameters:

- `task` (string, required)

### `flow_status` (~19 tokens)

Local health, configured models/checks, editor capabilities

### `flow_check` (~26 tokens)

Run operator-configured named checks; never arbitrary argv

Input parameters:

- `name` (string)

### `flow_attention_alignment` (~35 tokens)

Alignment between your published focus and a partner agent's focus (same saliency snapshot only)

Input parameters:

- `agent_id` (string, required)

### `flow_attention_decide` (~38 tokens)

Coordination decision against a partner agent's focus: parallel, serialize, or reject (stale frame)

Input parameters:

- `agent_id` (string, required)

### `flow_attention_focus` (~30 tokens)

Read a partner agent's currently advertised focus from the coordination board

Input parameters:

- `agent_id` (string, required)

### `flow_attention_publish` (~35 tokens)

Publish your attention focus (ordered salient targets + saliency snapshot hash) to the coordination board

Input parameters:

- `focus` (object, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/ai-qompass-phlow/phlow-mcp-linux-x64#diagnostics

## Score history

- 2026-10-24: 34
- 2026-10-23: 34
- 2026-10-22: 33
- 2026-10-21: 33
- 2026-10-20: 32
- 2026-10-19: 32

## Common questions

### What is the Phlow MCP Server server?

Phlow MCP Server is listed in the public MCP registry as ai.qompass/phlow. MCP server for the phlow agent runtime: bounded planner-coder-reviewer agent workflows. This page covers its MCPB bundle (https://github.com/qompassai/phlow/releases/download/v0.2.1/phlow-mcp-0.2.1-linux-x64.mcpb).

### Is the Phlow MCP Server server safe to use?

Phlow MCP Server scores 34 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 Phlow MCP Server server expose?

Phlow MCP Server exposes 7 tools: flow_run, flow_status, flow_check, flow_attention_alignment, flow_attention_decide, and 2 more. Their descriptions and schemas cost roughly 211 tokens of context every time the server is loaded.

### What licence is the Phlow MCP Server server under?

Phlow MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- Repository: https://github.com/qompassai/phlow
- Website: https://qompass.ai/solutions/phlow-mcp-server/
- Changelog RSS feed: https://verifymcp.io/servers/ai-qompass-phlow/phlow-mcp-linux-x64.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-qompass-phlow/phlow-mcp-linux-x64.json
- HTML version of this page: https://verifymcp.io/servers/ai-qompass-phlow/phlow-mcp-linux-x64