Notary record

pypi:mcp@2.2.0

PyPI · checked 21 Oct 2026, 22:49 UTC · checker 2026-10-19.2 · log index 834

Record issued 21 Oct 2026

Issued 21 Oct 2026, 22:49 UTC · pypi:mcp@2.2.0

unfinished

The check could not finish. This is not a pass.

The check could not finish (entry_point_failed), so this is not a pass.

The trace shows what a step attempted. A quiet trace is evidence, not proof.

An unfinished check is not a pass. Nothing here says the package is quiet.

Check another package

Phases

This record does not state its phases one by one; npm records from checker 2026-11-03.1 and Python records from 2026-11-04.3 on do.

Install steps

pypi:mcp has no install step of its own.

No dependency runs anything at install.

What the run reached

No install step reached anything we watch.

Programs
python3
Credentials read
No credential file or variable was opened.
Credentials sent
No decoy left the box.

First import

No first import was recorded for this check.

Dependencies

27 of 27 installed, as npm would on linux x64 musl.

Show all 27
  • anyio==4.15.1
  • httpx2==2.16.0
  • jsonschema==4.26.0
  • mcp-types==2.2.0
  • opentelemetry-api==1.45.1
  • pydantic==2.14.1
  • pyjwt==2.15.1
  • python-multipart==0.0.32
  • sse-starlette==3.5.0
  • starlette==1.9.0
  • typing-extensions==4.16.0
  • typing-inspection==0.4.4
  • uvicorn==0.54.0
  • idna==3.20
  • httpcore2==2.16.0
  • truststore==0.10.5
  • attrs==26.1.0
  • jsonschema-specifications==2025.9.1
  • referencing==0.37.0
  • rpds-py==2026.9.1
  • annotated-types==0.8.0
  • pydantic-core==2.50.1
  • cryptography==50.0.2
  • click==8.5.0
  • h11==0.16.0
  • cffi==2.1.1
  • pycparser==3.11

Since the previous version

No comparison with an earlier version was made for this check.

Sandbox

Decoys not recordedStand-in networkTracer ebpf

network=none; capabilities=all-dropped; rootfs=read-only; user=nobody; harness=separate-user

Signature and transparency log

level
unfinished
verdict
manual_review
reasonCode
entry_point_failed
keyId
322a2536e0d5ec8e
algorithm
ed25519
checker
2026-10-19.2
issuedAt
2026-10-21T22:49:00Z
contentSha256
bde982589473a060ae145e3406e9a5333fe538c97229ba841f5a7f92be004f81
contentSizeBytes
365656 (357 KB)
outputSha256
27aa2bf81e348a69f34d49a3b7d739748a461777d0b7c3333bae0c4c24b38c9d
log index
834

Verify the signature yourself, in your browser, at /verify. Kenwea is not in that loop.

Inclusion proofCheckpointKey list

Issued 21 Oct 2026, 22:49 UTC

What this does and does not say

The claim is about the bytes, not the name.

The signature covers these exact bytes. Another version is another check.

A quiet trace is evidence, not proof.

Code that only runs later, when your app calls it, is out of reach.

A signature is not an endorsement.

It says what happened, not that the code is good.

Twenty checks an hour for each network address. When a limit is ours, the record says unfinished and names it.