Developer · Remote MCP server
Kenwea Notary
Signed third-party verdict on what an npm package or file does when run. No key, no signup.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.kenwea.www/notary- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-09-29
- Updated
- 2026-09-29
- Publisher
- com.kenwea.www · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain www.kenwea.com or a parent domain of it · how
- Website
- www.kenwea.com/verify
- Repository
- github.com/kenwea-protocol/kenwea
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.kenwea.com/notary/v1 | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- kenwea-notary 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
kenwea.notary.check,kenwea.notary.verify,kenwea.notary.getPublicKey - Checked on
- 2026-10-05
How to connect Kenwea Notary
Kenwea Notary is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.kenwea.com/notary/v1, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.kenwea.www
| Server | Runs |
|---|---|
| Kenwea - Sandbox Attestation & Agent MarketplaceSigned sandbox verdicts on any artifact, plus an agent marketplace. No key, no signup, no payment. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
More developer servers
| Server | Runs |
|---|---|
| KeelNetwork diagnostics - ping, traceroute, DNS, port scanning, and connectivity testing. | Local · stdio |
| KeepMySubsManage your KeepMySubs subscriptions, spend, renewals, and bills from any MCP client. | Remote & Local · HTTP, stdioLive check: sign-in required |
| KeibiDropGive two agents on two machines the same encrypted folder. P2P, no cloud, only read bytes move. | Local · stdio |
| KeployEnd-to-end API testing - generate and run tests from OpenAPI, curl, Postman, or real user traffic. | Remote · HTTPLive check: ✓ handshake |
| KEPTA - the memory for AI systemsLocal encrypted memory for AI: hybrid search, 8 MCP tools, one file you own. Free, no cloud. | Local · stdio |
| Kernel MCP ServerAccess Kernel's cloud-based browsers and app actions via MCP (remote HTTP + OAuth). | Remote · HTTPLive check: sign-in required |
| KernelScanLinux kernel CVE analyzer: upload a.config, get a CycloneDX VEX report of affecting CVEs. | Remote · HTTPLive check: ✓ handshake |