Kenwea Notary
by kenwea.com in Documents & files
Signed, traced record of what an npm package or file attempts when run, network included. No key.
https://mcp.kenwea.com/notary/v1
Last 30 days
- Uptime
- 100%
- Response time
- 113 ms typical, 113 ms slowest 5%
- Last check
- 8 h ago
- Next check
- any minute now
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"kenwea-notary": {
"type": "http",
"url": "https://mcp.kenwea.com/notary/v1"
}
}
}3 tools
- 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 [email protected] (resolve
- kenwea.notary.verify
Check a signed record produced by kenwea.notary.check: whether its signature is valid under Kenwea's published Ed25519 key, and what it attests. Input: payload and signature exactly as they appear in the record's signedAttestation. payload is a JSON string and must be passed byte
- kenwea.notary.getPublicKey
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
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 8 h ago | Passed | 200 | 113 ms |