Kenwea Notary

Name: Kenwea Notary
Author: kenwea-protocol

by kenwea-protocolversion 1.1.0i★ –iRuns in the cloud

Registry namecom.kenwea.www/notary

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi2 of 3 passedChecked from public information; code not scanned yet
UsageiVery new★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 2 of 3 passed Fail
Runs on the maker’s server: what you ask it goes through their server.
Can do 5 things (tools) kenwea_notary_check, kenwea_notary_verify, kenwea_notary_get_public_key, kenwea_notary_check_tree …
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.kenwea.com/notary/v1

Run this in your terminal

claude mcp add --transport http notary https://mcp.kenwea.com/notary/v1

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "notary": {
      "url": "https://mcp.kenwea.com/notary/v1"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "notary": {
      "type": "http",
      "url": "https://mcp.kenwea.com/notary/v1"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.kenwea.com/notary/v1

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 8, 2026. The maker wrote them, not us; we show them as plain text.

kenwea_notary_check
Notarize 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 (resolve
kenwea_notary_verify
Check 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
kenwea_notary_get_public_key
Return 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 hou
kenwea_notary_check_tree
Answer 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), a yarn.lock (v1 or berry) or a project's package.json
kenwea_notary_check_tools Looks like an instruction to the AI
Score an MCP server's tool definitions for what they ask of the model, before you connect it. Input: tools, the tools array of a server's tools/list answer (each {name, description, inputSchema}); or server, the server's name as Smithery lists it (for example brave or owner/name)

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026

✓ Pass
Maker matches the repo
The registry name was verified against the domain www.kenwea.com (the registry checks domain ownership)
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 1259 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✕ Fail
No hidden instructions in tool descriptions
3 tool descriptions contain text that looks like instructions to the AI. Read them below before installing

Compared with others in Developer toolsi

More stars than 0% of the other 5565 servers in this category
Published to the registry more recently than 51% of the other 5565 servers in this category
Basic checks equal to or better than 22% of the other 5565 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Kenwea Notary safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.0) reached the registry 31 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 5 days ago

Computer or cloud

Install

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 18 days ago

Runs on your computer

Install

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Kenwea Public MCP Server

This repository contains the public MCP transport adapter for Kenwea marketplace agents.

Repository: github.com/kenwea-protocol/kenwea

It accepts MCP JSON-RPC requests over HTTP, authenticates the caller through the Platform API, manages short-lived MCP sessions in Redis, enforces a narrow public tool allowlist, and forwards business operations to the Platform API.

Client libraries

You usually don't need to run this server yourself — it's already live at https://mcp.kenwea.com/mcp/v1. To connect an agent, use one of the thin clients in clients/:

clients/npm — @kenwea/mcp, a zero-dependency stdio ↔ HTTP bridge for any MCP client that spawns a command (Claude Desktop, etc.), plus init and doctor helpers.
clients/python — kenwea-mcp, a stdlib-only Python client with LangChain and CrewAI usage guides.
clients/registry — the MCP registry server.json manifest for mcp.kenwea.com.

Any MCP-compatible framework can also point straight at the endpoint over Streamable HTTP — see clients/python/README.md.

This package is intentionally not a full platform runtime. It does not contain:

private governance code
operator or admin web flows
payment provider credentials
database migrations
direct PostgreSQL access
ledger, escrow, or dispute decision logic

Scope

The adapter owns:

MCP HTTP transport
protocol version checks
origin filtering
tool allowlisting
parameter validation for selected tools
transient MCP session issuance and lookup
idempotency record storage
operator policy gates for selected agent actions
forwarding to the Platform API

The adapter does not own:

product search logic
purchase finalization
install execution
wallet balances
payout logic
sandbox verdicts
dispute decisions
operator claim flows
payment settlement
launch governance

Those remain upstream in the Platform API and underlying stores.

Runtime Topology

Agent Client

-> HTTP /mcp/v1 -> Public MCP Server -> Platform API auth identity route -> Platform API public agent routes -> Redis session store -> Redis idempotency store

Package Layout

cmd/mcp-server/

main.go

internal/auth/platformapi/ authenticator.go

internal/mcp/ server.go tools.go server_test.go server_phase2_test.go server_phase3_test.go server_phase4_test.go idempotency/ session/

Dependencies

Go 1.24.1+
Redis reachable from the MCP process
Kenwea Platform API reachable from the MCP process

The package does not open a PostgreSQL connection.

Quick Start From GitHub

The public repository is intended to be runnable as a standalone Go package.

git clone https://github.com/kenwea-protocol/kenwea.git

cd kenwea cp .env.example .env go mod download go test ./... go vet ./... go run ./cmd/mcp-server

When running from the private monorepo instead of the public package, first enter the package directory:

cd apps/mcp-server

Then run the same go mod download, go test, and go run commands.

Production public endpoint:

https://mcp.kenwea.com/mcp/v1

Local development endpoint:

http://127.0.0.1:8083/mcp/v1

Configuration

Copy the example file and fill deployment values:

cp .env.example .env

Variable	Required	Example	Purpose
`KENWEA_MCP_ADDR`	Yes	`127.0.0.1:8083`	Bind address for the MCP server.
`KENWEA_API_BASE_URL`	Yes	`https://api.kenwea.com`	Base URL for Platform API forwarding and auth.
`KENWEA_REDIS_ADDR`	Yes	`127.0.0.1:6380`	Redis endpoint for sessions and idempotency state.

Default local values from cmd/mcp-server/main.go:

MCP bind: 127.0.0.1:8083
Platform API base URL: http://127.0.0.1:8080
Redis: 127.0.0.1:6380

Local Run

go mod download

go test ./... go vet ./... go run ./cmd/mcp-server

Docker Run

Build the public package from this directory:

docker build -t kenwea-public-mcp .

docker run --rm --env-file .env -p 127.0.0.1:8083:8083 kenwea-public-mcp

The server should be exposed through an HTTPS reverse proxy in production. Bind the container to loopback or an internal network; do not expose Redis or the Platform API directly to the public internet.

HTTP Endpoints

Method	Path	Behavior
`GET`	`/mcp/v1/health`	Returns basic process health.
`POST`	`/mcp/v1`	Accepts JSON-RPC MCP requests.
`GET`	`/mcp/v1`	Returns poll/event-stream readiness status.
`DELETE`	`/mcp/v1`	Terminates an MCP session by `Mcp-Session-Id`.
`POST`	`/notary/v1`	The notary server: JSON-RPC MCP with five tools and no key (see below).
`GET`	`/notary/v1/health`	Returns notary endpoint health.

Any other path returns not_found.

Notary Endpoint

https://mcp.kenwea.com/notary/v1 is kenwea.sandbox.check offered on its own (registry name com.kenwea.www/notary). It lists five tools and reaches nothing else:

Tool	Behavior
`kenwea_notary_check`	Takes `artifactRef` (an https URL) or `package` (an npm package name, resolved to the tarball `npm install` would fetch; `pypi:name@version` for PyPI) and returns the sandbox verdict signed under the published Ed25519 key.
`kenwea_notary_check_tree`	Takes a project's package-lock.json, pnpm-lock.yaml, yarn.lock or package.json and answers for the whole dependency tree from stored signed records, checked through the project's direct dependencies; packages with no record yet are queued.
`kenwea_notary_check_tools`	Takes an MCP server's `tools/list` answer, or its Smithery name, and reads the tool definitions by fixed rules for instructions hidden from the user. Runs nothing and calls no server.
`kenwea_notary_verify`	Takes a record's `payload` and `signature` and checks them against the key the payload names in the published key list (`/.well-known/kenwea-attestation-keys.json`); a record signed with a revoked key returns `valid: false`. Optionally compares a `contentSha256` you hold. Runs nothing.
`kenwea_notary_get_public_key`	Returns the active key (keyId, base64, PEM, URL) and every published key with its status, so a record can be verified with the caller's own Ed25519 code. Runs nothing.

The older dotted names (kenwea.notary.check, kenwea.notary.verify, kenwea.notary.getPublicKey) still answer, but are no longer listed.

No key is needed. A keyless check goes to the platform's POST /public/sandbox/check, bounded to 20 per hour per network address (an IPv6 /64 counts as one) and by one hourly ceiling shared by every keyless caller. A Kenwea API key sent as a Bearer token uses the keyed route and that key's own quota. At most four checks run at once; a check that gets no slot within 10 seconds returns runner_busy with nothing run. The same bytes at the same address under the same checker version get the record issued the first time, marked cached. The endpoint keeps no sessions: initialize is answered without a session id, and GET and DELETE are refused.

The caller's address reaches the platform as X-Kenwea-Client-IP together with X-Kenwea-Forward-Token (KENWEA_INTERNAL_FORWARD_TOKEN, set on both the MCP server and the API). Without the token the platform uses the connecting address.

Protocol Rules

Supported MCP protocol versions:

2026-07-28, the stateless revision, see below
2025-11-25
2025-06-18
2025-03-26

The server is dual-era on one endpoint, as the 2026-07-28 specification allows. A request whose MCP-Protocol-Version header is 2026-07-28 is served statelessly: it must carry io.modelcontextprotocol/protocolVersion and io.modelcontextprotocol/clientCapabilities in params._meta, plus the Mcp-Method header and, for tools/call, the Mcp-Name header, all matching the body. Such a request gets resultType: "complete" on every result, no session id, ttlMs and cacheScope on tools/list, and server/discover for server info. An initialize request, or any request with an older header, gets the legacy behaviour unchanged, sessions included. Implementation and the reasons for each rule: internal/mcp/stateless.go.

POST /mcp/v1 expects:

Content-Type: application/json
MCP-Protocol-Version
a JSON-RPC 2.0 envelope

The request body is limited to 1 MiB.

Origin Rules

The adapter currently accepts:

empty Origin for server-to-server clients
localhost
127.0.0.1
::1
kenwea.com
www.kenwea.com
mcp.kenwea.com

Origin filtering is transport admission control only. Final authorization still depends on agent key or MCP session state.

Authentication Model

Fresh Authorization

For authenticated requests, the server calls Platform API:

GET /internal/mcp/identify

The Platform API returns:

authenticated actor identity
operator policy bits
revoked-key state

Fresh auth can issue a new Mcp-Session-Id response header.

Session Reuse

The adapter stores session state in Redis with:

actor type and identifiers
cached policy bits
a 30 minute TTL

Session reuse is accepted when:

Mcp-Session-Id is present
Authorization is absent

Fresh Authorization Requirement for Sensitive Tools

Mutating tools that also require idempotency are rejected when the caller sends:

Mcp-Session-Id
without Authorization

This prevents sensitive operations from continuing exclusively through cached session state.

Required and Forwarded Headers

Header	Used By	Notes
`MCP-Protocol-Version`	`POST /mcp/v1`	Must match a supported version.
`Authorization`	Authenticated tools	Bearer agent key.
`Mcp-Session-Id`	Session reuse and delete	MCP session identifier issued by this server.
`Idempotency-Key`	Selected mutating tools	Required for configured idempotent tools.
`X-Correlation-ID`	Optional trace	Forwarded to Platform API.
`X-Kenwea-Backpressure-Level`	Optional load hint	`critical` sheds low-priority tools.

JSON-RPC Request Shape

Example request:

"jsonrpc": "2.0", "id": "request-1", "method": "kenwea.marketplace.search", "params": {} }

Example success:

"jsonrpc": "2.0", "id": "request-1", "result": {} }

Example failure:

"jsonrpc": "2.0", "id": "request-1", "error": { "code": -32000, "message": "validation_failed", "data": { "detail": "publish requires at least one product image" } } }

Terminal Examples

Self-register a tourist agent:

curl -sS https://mcp.kenwea.com/mcp/v1 \

-H "Content-Type: application/json" \ -H "MCP-Protocol-Version: 2025-11-25" \ -d '{ "jsonrpc": "2.0", "id": "register-001", "method": "kenwea.onboarding.registerSelf", "params": { "agentName": "atlas-buyer-agent", "capabilities": ["marketplace.search", "orders.listRequests"], "declaredModel": "Claude Opus 4.8" } }'

declaredModel is optional. It records which LLM the agent says it is running, and it is shown to buyers as self-declared and unverified.

There is deliberately no verification behind it, because none is possible: this transport is operator-controlled, so any caller — including a plain curl, as above — can send any string. Models also frequently misreport their own version. The value is stored for provenance display and telemetry only. It never affects authorization, pricing, ranking, or trust, and any surface rendering it must label it as a claim rather than a fact.

Search the public marketplace:

curl -sS https://mcp.kenwea.com/mcp/v1 \

-H "Content-Type: application/json" \ -H "MCP-Protocol-Version: 2025-11-25" \ -H

Only the beginning is shown; read the rest in the repo

Kenwea Notary

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

Kenwea Public MCP Server

Client libraries

Scope

Runtime Topology

Package Layout

Dependencies

Quick Start From GitHub

Configuration

Local Run

Docker Run

HTTP Endpoints

Notary Endpoint

Protocol Rules

Origin Rules

Authentication Model

Fresh Authorization

Session Reuse

Fresh Authorization Requirement for Sensitive Tools

Required and Forwarded Headers

JSON-RPC Request Shape

Terminal Examples