Back to Browse

Clavis MCP Server

Developer ToolsModerate6.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Encrypted credential vault for AI agents — auto OAuth refresh, rate limiting, audit logging.

About

Encrypted credential vault for AI agents — auto OAuth refresh, rate limiting, audit logging.

Security Report

6.2
Moderate6.2Moderate Risk

The Clavis MCP server is well-designed with strong security practices. It implements proper authentication via JWT, avoids storing secrets in logs or context when possible (via server-side credential injection), and includes comprehensive testing. The code is clean with appropriate error handling and input validation. Minor concerns around broad exception handling and the legacy get_credentials tool (which is appropriately flagged as unsafe) do not significantly impact the overall security posture. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

4 files analyzed · 7 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-kn0wbot-clavis": {
      "args": [
        "-y",
        "@clavisagent/mcp-server"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Clavis MCP Server

Secure credential management for Claude Desktop and MCP servers.

Features

  • 🔐 Encrypted credential storage (AES-128-CBC + HMAC-SHA256, via Fernet)
  • 🛡️ Server-side credential injection — the raw key never enters the conversation
  • 🔄 Automatic OAuth token refresh
  • 📡 Thin forwarding layer — rate limiting, audit logging, and usage tracking are all handled by the Clavis server

Installation

npx @clavisagent/mcp-server

Or install globally:

npm install -g @clavisagent/mcp-server

Usage with Claude Desktop

Add the following to your Claude Desktop configuration file (claude_desktop_config.json):

{
  "mcpServers": {
    "clavis": {
      "command": "npx",
      "args": ["-y", "@clavisagent/mcp-server"],
      "env": {
        "CLAVIS_API_KEY": "eyJ..."
      }
    }
  }
}

Usage with Claude Code

claude mcp add clavis -- npx -y @clavisagent/mcp-server

Configuration

VariableRequiredDefaultDescription
CLAVIS_API_KEYyesYour Clavis JWT, from POST /v1/auth/login. Not the cla_… key shown at sign-up.
CLAVIS_API_URLnohttps://clavisagent.comBase URL of your Clavis instance. Set this for self-hosted deployments.

Available Tools

ToolDescription
call_serviceRecommended. Make an API call with server-side credential injection — the credential is injected into the upstream request server-side, so the raw key never enters the conversation.
get_credentialsLegacy. Returns the raw access token or API key for a named service. Prefer call_service.
list_servicesList all services with stored credentials
check_credential_statusCheck the status and expiry of credentials for a service

Security note

Prefer call_service over get_credentials. call_service keeps the secret server-side, so a prompt injection has no credential in context to exfiltrate. get_credentials places the raw key in the conversation and exists only for callers that must hold the token themselves.

License

MIT

Reviews

No reviews yet

Be the first to review this server!

Clavis MCP Server - Encrypted credential vault for AI agents — auto OAuth | MCP Marketplace