MCPKit is an embedded, loopback-only HTTP transport for trusted native host applications. It provides a per-launch bearer token and user-readable discovery files. It does not sandbox tools, authorize individual tool calls, validate a host application's schemas, or make an application safe to expose by itself.

Host applications remain responsible for:

• exposing the minimum necessary tools and data;
• validating every tool argument;
• applying per-capability authorization and user approval;
• preventing secrets or sensitive content from entering logs;
• treating tool output and imported content as untrusted;
• rotating or removing discovery credentials when the server stops; and
• reviewing platform sandbox, file-access, and network entitlements.

MCPKit does not modify third-party client configuration. A client must deliberately read the host application's handshake or registry entry and decide whether to connect.

• Bearer tokens are stored in user-readable files with mode 0600; any process running as the same user may be able to read them.
• Loopback binding prevents remote network access but does not isolate other local processes.
• The HTTP implementation is intentionally small and is not a general-purpose web server.
• Protocol conformance is limited to transport and JSON-RPC types; MCP method behavior is supplied by the host delegate.

Please report security issues privately through GitHub's security-advisory feature. Do not include real user data, credentials, or exploit details in a public issue.