Fleetpost
PYPI · FLEETPOST-MCP
A mailbox for your machines: read fleet capabilities, send a request. Offline, no server.
Available components
Last scanned (6 hours ago)
Scores higher than 82% of PyPI servers
Category Workflow Automation
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 55 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 557 tokens (~92/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 −14
- Provenance: unverified → fail ▼ security
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 +14
- Provenance: fail → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.93 functional
- 21 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 20 Oct 26 +15
- Malware scan: unverified → pass ▲ security
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 6 Nov 2026 · Analysed pypi/fleetpost-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
fleet_capabilities ~51
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.
| Name | Type | Req | Description |
|---|---|---|---|
| machine | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
fleet_handle ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fleet_read_request ~37
Read one unhandled request from this machine's own inbox, by filename as reported by fleet_status.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fleet_send_request ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| done_means | string | yes | – |
| reply_to | – | – | – |
| to | string | yes | – |
| topic | string | yes | – |
| valid_until | string | yes | – |
| what_is_wanted | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
fleet_status ~107
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
fleet_sync ~50
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · fleetpost-mcp
claude mcp add stanimirtenev-fleetpost-mcp -- uvx fleetpost-mcp
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 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 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 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Fleetpost MCP server under?
Fleetpost declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Fleetpost MCP server?
VerifyMCP ran 16 checks on Fleetpost, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.