io.github.reiarseni/mockpost
PYPI · MOCKPOST
Local multi-channel message emulator for E2E testing, with MCP tools for LLM agents.
Available components
Last scanned (21 hours ago)
Scores higher than 0% of PyPI servers
Category Testing and QA
Recent critical change
Known CVEs (13 Oct 2026). See the changelog before you install this server.
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 Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 6 of 55 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency74
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to reiarseni/mockpost). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 59 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
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.
- 15 Oct 26 0
- Malware scan: unverified → pass ▲ security
- 13 Oct 26 −19
- Known CVEs: unverified → fail ▼ critical
- Score status: scored → failed ▼ critical
- Dependency health: unverified → 0.95 ▲ functional
- 12 Oct 26 +19
- Known CVEs: fail → unverified ▼ security
- Dependency health: 0.95 → unverified ▼ functional
- Score status: failed → scored ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- License: fail → pass ▲ functional
- Licence: MIT License → MIT functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 13 Sept 26 0
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 0
- Malware scan: unverified → pass ▲ security
- 10 Sept 26 0
- Malware scan: pass → unverified ▼ 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 23 Oct 2026 · Analysed pypi/mockpost@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | reiarseni/mockpost |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/reiarseni/mockpost/.github/workflows/ci.yml@refs/tags/v0.3.0 |
| Rekor log index | 2581775170 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:09f79edf257e88a1394329c61e4c99323f5804a5e5879f6d991215c73d875047 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 14 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-5h2m-4q8j-pqpj | CVE-2025-69196 | high | yes | |
| GHSA-c2jp-c369-7pvx | high | yes | ||
| GHSA-m8x7-r2rg-vh5g | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-mxxr-jv3v-6pgc | CVE-2025-62800 | medium | yes | |
| GHSA-rcfx-77hg-w2wv | high | yes | ||
| GHSA-rj5c-58rq-j5g5 | CVE-2025-62801 | medium | yes | |
| GHSA-rww4-4w9c-7733 | CVE-2026-27124 | high | yes | |
| GHSA-vv7q-7jx5-f767 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
| PYSEC-2026-1364 | CVE-2025-62800 | none | yes | |
| PYSEC-2026-1365 | CVE-2025-62801 | none | yes | |
| PYSEC-2026-2474 | CVE-2025-69196 | none | yes | |
| PYSEC-2026-2475 | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2476 | CVE-2026-27124 | none | yes | |
| PYSEC-2026-338 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 55 packages
| Packages resolved | 55 |
|---|---|
| Stale | 5 |
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the io.github.reiarseni/mockpost MCP server?
io.github.reiarseni/mockpost runs locally as a PyPI package, launched with uvx mockpost. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mockpost
claude mcp add reiarseni-mockpost -- uvx mockpost
What is the io.github.reiarseni/mockpost MCP server?
io.github.reiarseni/mockpost is an MCP server listed in the public MCP registry as io.github.reiarseni/mockpost. Local multi-channel message emulator for E2E testing, with MCP tools for LLM agents. This page covers its PyPI package (mockpost).
Is the io.github.reiarseni/mockpost MCP server still maintained?
io.github.reiarseni/mockpost is still listed as active in the MCP registry. We last reached this channel on 23 October 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 io.github.reiarseni/mockpost MCP server under?
io.github.reiarseni/mockpost declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.