# Fleetpost (pypi · fleetpost-mcp)

A mailbox for your machines: read fleet capabilities, send a request. Offline, no server.

- Trust score: 77/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- pypi · `fleetpost-mcp`: 77/100 (this document), [markdown](https://verifymcp.io/servers/stanimirtenev-fleetpost-mcp/fleetpost-mcp.md), [page](https://verifymcp.io/servers/stanimirtenev-fleetpost-mcp/fleetpost-mcp)

## Channel facts

- Registry: `pypi`
- Package: `fleetpost-mcp`
- Version: `0.2.0`
- 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-09-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 9 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 (good).
  - Tool/resource definitions use about 557 tokens (~92/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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; "fleet_send_request" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 6 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 Fleetpost MCP server?

Fleetpost runs locally as a PyPI package, launched with uvx fleetpost-mcp. 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 stanimirtenev-fleetpost-mcp -- uvx fleetpost-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "stanimirtenev-fleetpost-mcp": {
      "command": "uvx",
      "args": [
        "fleetpost-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stanimirtenev-fleetpost-mcp": {
      "command": "uvx",
      "args": [
        "fleetpost-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add stanimirtenev-fleetpost-mcp -- uvx fleetpost-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stanimirtenev-fleetpost-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "fleetpost-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add stanimirtenev-fleetpost-mcp --command uvx --arg fleetpost-mcp
```

### Hermes

```yaml
mcp_servers:
  stanimirtenev-fleetpost-mcp:
    command: "uvx"
    args: ["fleetpost-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "stanimirtenev-fleetpost-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "fleetpost-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add stanimirtenev-fleetpost-mcp -t stdio -c uvx -a fleetpost-mcp
```

### Other

```json
{
  "mcpServers": {
    "stanimirtenev-fleetpost-mcp": {
      "command": "uvx",
      "args": [
        "fleetpost-mcp"
      ]
    }
  }
}
```

## 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-09-20 (score 77, +1)

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

### 2026-09-18 (score 76, −2)

- [functional] Stability: pass → 0.80

### 2026-09-17 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 78, +1)

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

### 2026-09-13 (score 77, +1)

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

### 2026-09-11 (score 76, −2)

- [security regression] Stability: pass → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Schema quality: 83 → 92
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Stability: pass → 0.80
- [functional] Package version: 0.1.0 → 0.2.0

### 2026-09-10 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 78, +1)

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

## MCP tools (6)

### `fleet_status` (~107 tokens)

What is waiting for this machine: unhandled requests in its inbox, whether the
shared protocol changed, which other machines' capabilities are known, and when the
last coordination cycle ran. Also what this machine is waiting on: requests it sent
that the recipient has not picked up yet (`outstanding_sends`), each with when that
recipient last ran a cycle — null there means it never has, so it will not see the
request at all. Reads local files only.

### `fleet_capabilities` (~51 tokens)

What the machines in this fleet can do. Omit `machine` for all of them. Use this
before asking another machine for something, to check it can actually do it.

Input parameters:

- `machine`

### `fleet_read_request` (~37 tokens)

Read one unhandled request from this machine's own inbox, by filename as reported
by fleet_status.

Input parameters:

- `name` (string, required)

### `fleet_send_request` (~245 tokens)

Ask another machine in the fleet to do something, by dropping a request in its inbox.

The machine may be offline; it will pick the request up on its next cycle. Every field
below is required by the protocol, because a request missing them cannot be acted on.

Ask for an *action*, not for access: if the task needs a credential this machine lacks,
the machine that holds it does the work and returns the result. Secrets never travel.

Args:
    to: Target machine name, as listed by fleet_status.
    topic: Short subject; also becomes part of the filename.
    what_is_wanted: Exactly what should be done.
    done_means: How the other side will know it finished — the acceptance test.
    valid_until: When this stops being worth doing (e.g. "2026-08-20").
    reply_to: Where to put the answer. Defaults to this machine's inbox.

Input parameters:

- `done_means` (string, required)
- `reply_to`
- `to` (string, required)
- `topic` (string, required)
- `valid_until` (string, required)
- `what_is_wanted` (string, required)

### `fleet_handle` (~67 tokens)

Mark a request in this machine's own inbox as done, moving it to inbox/handled/.

Do this only after the work is done and the answer has been sent. A request left at the
top level counts as still pending and will keep being flagged.

Input parameters:

- `name` (string, required)

### `fleet_sync` (~50 tokens)

Run one coordination cycle now: pull this machine's inbox and the fleet's
capabilities, then publish this machine's own descriptors if they changed.

Never executes a request and never changes another machine's data.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/stanimirtenev-fleetpost-mcp/fleetpost-mcp#diagnostics

## Score history

- 2026-09-21: 77
- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 78
- 2026-09-16: 78
- 2026-09-15: 77
- 2026-09-14: 77
- 2026-09-13: 77
- 2026-09-12: 76
- 2026-09-11: 76
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 77
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 73
- 2026-08-29: 73
- 2026-08-28: 72
- 2026-08-27: 72
- 2026-08-26: 71
- 2026-08-25: 71
- 2026-08-24: 70
- 2026-08-23: 70

## Common questions

### What is the Fleetpost MCP server?

Fleetpost is an MCP server listed in the public MCP registry as io.github.StanimirTenev/fleetpost-mcp. A mailbox for your machines: read fleet capabilities, send a request. Offline, no server. This page covers its PyPI package (fleetpost-mcp).

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

Fleetpost scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 Fleetpost MCP server expose?

Fleetpost exposes 6 tools: fleet_status, fleet_capabilities, fleet_read_request, fleet_send_request, fleet_handle, fleet_sync. Their descriptions and schemas cost roughly 557 tokens of context every time the server is loaded.

### Is the Fleetpost MCP server still maintained?

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

## Links

- PyPI project: https://pypi.org/project/fleetpost-mcp/
- Socket report: https://socket.dev/pypi/package/fleetpost-mcp
- Repository: https://github.com/StanimirTenev/fleetpost
- Changelog RSS feed: https://verifymcp.io/servers/stanimirtenev-fleetpost-mcp/fleetpost-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/stanimirtenev-fleetpost-mcp/fleetpost-mcp.json
- HTML version of this page: https://verifymcp.io/servers/stanimirtenev-fleetpost-mcp/fleetpost-mcp