Skip to main content

Prism MCP for Python

Consuming Model Context Protocol servers as Prism tools, across an explicit trust boundary. The Python port of particle-academy/prism-mcp.

Zero runtime dependencies. Python 3.10+.

pip install prism-ai-mcp
from prism_mcp import Client, TrustPolicy

docs = Client(
    "docs",
    my_transport,
    trust=TrustPolicy.allowing(["search"], pins={"search": "sha256:3f1c…"}),
)


async def search_docs() -> None:
    tools = await docs.list_tools()
    result = await docs.call_tool(tools[0], {"query": "rate limits"})

    print(result.text)

my_transport is a callable that takes a TransportRequest (method, params, headers) and returns an awaitable yielding the decoded server result. An async def transport satisfies that contract. The package opens no connections itself.

Breaking change in 0.2.0: list_tools() and call_tool() must be awaited, and the transport must return an awaitable. Run search_docs() in your application's event loop. A synchronous embedder must manage that loop itself; the package provides one async client path.

Security fix in 0.2.1: in 0.2.0 an async def gate was never awaited. Its coroutine is truthy, so a gate that returned False was read as consent and the call was sent. If you wrote an async gate, upgrade.

Trust

A tool list is not data the model summarises; it is instructions the model follows. So nothing is offered until you say what you trust.

  • TrustPolicy.undeclared() is the default. list_tools() raises server_not_trusted instead of returning the server's tools.
  • TrustPolicy.allowing([...]) offers only the named tools. allowing([]) is a declaration too, and offers nothing.
  • TrustPolicy.allowing_every_tool() offers every tool, including ones the server adds later.
  • Pins. Pass pins={name: digest}. ToolDefinition.digest() covers the tool's name, title, description and input schema, so a server that rewrites a description after you trusted it is refused with tool_definition_changed.

A gate callable (server, tool, arguments) -> bool is asked before every call; returning False raises tool_denied. It may be sync or async def; an async verdict is awaited before anything is sent. The default allows every call that trust admitted, and deny_all refuses them all.

Results

Every result passes through a ResultGuard before it reaches you:

  • A result over max_bytes (65,536 by default) raises result_too_large instead of being truncated.
  • The text is wrapped in an <untrusted-tool-output> tag with a random id per result, so the server's output cannot close the wrapper.
  • A filter callable (server, tool, text) -> text runs before framing, if you pass one. It must be synchronous; one that returns anything but str (an async def filter returns a coroutine) raises TypeError.

The wrapper makes a prompt injection harder. It does not make one impossible, and the guard does not scan the text for injection strings.

Mirrored parameters

A tool's schema can mark an argument with x-mcp-header, which copies the model's value into an Mcp-Param-* request header. A tool whose annotations break the rules (an invalid header name, two arguments mirrored to the same header) is left out of list_tools() rather than repaired.

Protocol

The client speaks MCP 2026-07-28, the stateless revision. Earlier revisions open with an initialize handshake and a session, which this client does not implement. is_stateless_protocol(version) tells the two apart.

Errors

Every failure is an McpError with a stable code: server_not_trusted, tool_definition_changed, tool_denied, result_too_large, mirrored_parameter_refused, unsupported_protocol_version, protocol_failure, tool_call_failed, server_not_configured.

Parity

prism-parity's mcp-tool-digest corpus pins tool digests against the PHP reference and the TypeScript port, so a pin computed in one language holds in the others.

One case is not in that corpus: a schema containing an integral float such as 1.0 digests differently here than in PHP and TypeScript. For such a tool, compute the pin in Python.

License

MIT. See LICENSE.

Metadata

Release files for prism-ai-mcp 0.2.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for prism-ai-mcp 0.2.1
File Size Uploaded Provenance Actions
prism_ai_mcp-0.2.1.tar.gz 12.6 kB With provenance Details for prism_ai_mcp-0.2.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for prism-ai-mcp 0.2.1
File Interpreter ABI Platform Actions
prism_ai_mcp-0.2.1-py3-none-any.whl Python 3 none any Details for prism_ai_mcp-0.2.1-py3-none-any.whl

Total release size: 26.1 kB

Release files / prism_ai_mcp-0.2.1.tar.gz

Download URL prism_ai_mcp-0.2.1.tar.gz
Size 12.6 kB
Tags Source
SHA-256 checksum
How to use checksums
5d02d63bc4c8e86691ebe6616bae5e2e3a7a98bba27b4b4de9674a5e23f8eb84
BLAKE2b-256 checksum
How to use checksums
3afff31ffaf7ecb01854b6739691369531511f9c942fa21af7ba2a0076553670
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 15, 2026.

Transparency log

Release files / prism_ai_mcp-0.2.1-py3-none-any.whl

Download URL prism_ai_mcp-0.2.1-py3-none-any.whl
Size 13.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
706c09c17e40cc9254659d5da036a6f3243ad67cae4108c4f84068dd80431029
BLAKE2b-256 checksum
How to use checksums
e5415bf839b646a75ac02a30899065bb36e96e54d19b393712e8d00202ccea0d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 15, 2026.

Transparency log

Security for prism-ai-mcp 0.2.1

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.

Select from 2 files

Attestation for prism_ai_mcp-0.2.1.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 Oct 15, 2026.

Transparency log

A 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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page