MemoFlow MCP adapter for Python
Provider-library-independent MCP tool adapter for server-backed MemoFlow activities. It reserves tool budget before dispatch, records immutable invocation and tool-effect transitions, injects a stable idempotency key, and restores settled results from protected durable output before any new budget or network effect.
adapter = McpToolAdapter(client)
result = await adapter.call_tool(McpToolRun(
server=McpServer("notes", version="1"),
tool=McpTool("save_note", version="1", arguments={"note": "hello"}),
budget=AiBudgetEstimate(total_tokens=0, tool_calls=1),
recorded_replay_key="save-note-turn-1",
))
The injected client is structural and must provide an async call_tool
method. This keeps the durability boundary independent of any particular MCP
transport package.
1 maintainer
Metadata
1 maintainer
Release files for memoflow-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| memoflow_mcp-0.1.0.tar.gz | 7.4 kB | With provenance | Details for memoflow_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| memoflow_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for memoflow_mcp-0.1.0-py3-none-any.whl |
Total release size: 13.6 kB
Release files / memoflow_mcp-0.1.0.tar.gz
| Download URL | memoflow_mcp-0.1.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8268bcfca9a1969cdd40a536ac1f557909d546dbdb4cc72964fa9ed147318f58
|
|
BLAKE2b-256 checksum How to use checksums |
2a1630ec181e041cfef0b52a0e4326bf9f0442a61d28140ff3aeea64728edcf1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 16, 2026.
Transparency logRelease files / memoflow_mcp-0.1.0-py3-none-any.whl
| Download URL | memoflow_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
46c569c6d3d99adeb9b1d9259cf13ef84503030ed1f711c89fa1f6e07124dfb8
|
|
BLAKE2b-256 checksum How to use checksums |
67b21a22404bb411c4492bf2d2db19ca31d7b06d329b9d928c77d7e87e51dcd7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 16, 2026.
Transparency logSecurity for memoflow-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for memoflow_mcp-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
