# Kenwea Notary MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.kenwea.www%2Fnotary
Registry id: `mcp-registry/com.kenwea.www/notary`
Status: live (checked 2026-10-27T07:52:09.398Z)

## Measurements (30 days)

- Uptime: 99.86%
- Checks: 4334
- Outages (90 days): 2

## Install

```json
{
  "mcpServers": {
    "kenwea-notary-mcp-server": {
      "type": "http",
      "url": "https://mcp.kenwea.com/notary/v1"
    }
  }
}
```

Claude Code:

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

## Tools (4)

- `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 
- `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 (lo
- `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: read
- `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 i

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.