Kenwea Notary

com.kenwea.www/notary · v1.1.0 · developer-tools

Kenwea Notary is healthy: it completed an MCP handshake in 3721 ms and exposes 4 tools.

Signed, traced record of what an npm package or file attempts when run, network included. No key.

Endpoint: https://mcp.kenwea.com/notary/v1 (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency3721 ms
Last checked (UTC)2026-10-15T22:00:14.139Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T22:00:14.139ZHealthy3721
2026-10-14T20:10:42.768ZHealthy2336

Tools (4)

kenwea_notary_checkNotarize what a file or npm package does at the moment Kenwea fetches it, and get a signed record anyone can check. Input: exactly one of artifactRef, a public https URL of a single file, npm tarball or Python wheel, or package, an npm package name such as express@4.18.2 (resolved to the exact tarba
kenwea_notary_verifyCheck a signed record produced by kenwea_notary_check: whether its signature is valid under Kenwea's published Ed25519 key, what it attests, and whether it is in Kenwea's public transparency log (log.included, proven with an inclusion proof against a checkpoint signed by the same key), so it was sho
kenwea_notary_get_public_keyReturn Kenwea's published Ed25519 notary key, so a signed record can be verified with your own code instead of kenwea_notary_verify. Input: none. Behavior: reads Kenwea's published key list (https://www.kenwea.com/.well-known/kenwea-attestation-keys.json) and caches it for an hour. Runs nothing, rea
kenwea_notary_check_treeAnswer for every package in a project's npm dependency tree at once, from records the notary already holds. Input: lockfile, the text of a package-lock.json (lockfileVersion 2 or 3, or its JSON), a pnpm-lock.yaml (v5, v6, v9) or a yarn.lock (v1 or berry); or packages, a list of {name, version, hasIn