Mockpost

io.github.reiarseniPublished by GitHub account reiarseniv0.3.0Updated Oct 24, 2026

Local multi-channel message emulator for E2E testing, with MCP tools for LLM agents.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

Lets an assistant drive a local multi-channel message emulator for end-to-end testing.

What you can do
Mockpost is a local multi-channel message emulator intended for end-to-end testing, exposed to LLM agents through MCP tools. The registry description says it provides MCP tools so an agent can interact with the emulator, and it runs as a local process over stdio. No individual tool names or operations are listed in the supplied material.
When to use it
Consider it when you are building or testing software that sends or receives messages across several channels and want an assistant to exercise that flow against a local emulator instead of real services.
Requirements
Runs as a local process on the user's machine (desktop only, no web executable) via the PyPI package mockpost over stdio. It expects a MockPost HTTP service to be reachable; the base URL is set with the environment variable MOCKPOST_URL, defaulting to No authentication is declared.
Before you install
The server talks to a local HTTP service at the address given by MOCKPOST_URL, so point it only at an emulator you control. Because it emulates messaging channels, actions taken through it may send or alter test messages; confirm what the tools do before running them against anything beyond a test environment.

Installation

In SourceWeft

  1. Open Mockpost in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.