Everything the interface can do, an MCP-capable client can do too — under your permissions, with confirmation for anything consequential. Built on the official SDK against the current MCP specification.
The most common way an integration layer becomes a security incident is by running as a service account with broad rights. Noverva's MCP server has no ambient authority at all.
The specification distinguishes three things a server can offer. Noverva uses all three rather than flattening everything into tool calls.
Read tools follow your permissions with no extra ceremony. Write tools state their consequence before they act.
A scoped key, an endpoint, and you are done. Keys carry explicit scopes, can be rotated, and can be revoked without touching anything else.
The key inherits the permissions of the member who created it, and can be scoped down further. It can never be scoped up.