Clavis Mcp Server

Name: Clavis Mcp Server
Author: KN0WBOT

@KN0WBOT

About Clavis Mcp Server

Secure credential management for AI agents — encrypted storage, auto-refresh, and rate limiting via a single MCP call. Supports OpenAI, Anthropic, Stripe, GitHub, Brave Search, Kalshi, Coinbase, plus generic API key and OAuth2 for any service.

#credentials #security #authentication #api-keys #oauth #agents

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "clavis": {
      "command": "npx",
      "args": [
        "-y",
        "@clavisagent/mcp-server"
      ],
      "env": {
        "CLAVIS_API_KEY": "<YOUR_API_KEY>",
        "CLAVIS_BASE_URL": "https://clavisagent.com"
      }
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is Clavis Mcp Server?

Clavis Mcp Server provides credential infrastructure for autonomous AI agents. Instead of storing API keys in environment variables or config files, agents retrieve encrypted, auto-refreshed tokens through a single MCP tool call.

How to use Clavis Mcp Server?

Install via npm (@clavisagent/mcp-server) and configure the server to connect your agents. Agents make a single MCP tool call to retrieve encrypted, auto-refreshed tokens. Consult the docs at https://clavisagent.com/docs/mcp.html for detailed setup.

Key features of Clavis Mcp Server

AES-128-CBC + HMAC-SHA256 encryption at rest
Auto OAuth token refresh with proactive 5-minute expiry check and exponential backoff
Redis-backed distributed rate limiting shared across all agents
Full audit logging with timestamped credential access
Dry-run credential check without external API calls
JWT revocation support

Use cases of Clavis Mcp Server

Secure credential management for autonomous AI agents
Centralized API key storage replacing environment variables and config files
Automated OAuth token refresh to maintain uninterrupted agent operations
Distributed rate limiting across a fleet of agents
Auditable credential access for compliance and monitoring

FAQ from Clavis Mcp Server

What services does Clavis Mcp Server support?

OpenAI, Anthropic, Stripe, GitHub, Brave Search, Kalshi, Coinbase, plus generic API key and OAuth2 for any service.

How does credential encryption work?

Credentials are encrypted at rest using AES-128-CBC with HMAC-SHA256.

How does token refresh work?

OAuth tokens are proactively refreshed 5 minutes before expiry using exponential backoff.

Is there rate limiting?

Yes, Redis-backed distributed rate limiting is shared across all agents.

What audit capabilities does it provide?

Every credential access is timestamped and logged for a full audit trail.

Comments

More Search MCP servers

Google Search Console MCP Server

ahonn

A Model Context Protocol (MCP) server providing access to Google Search Console

239

Perplexity MCP Zerver

wysh3

MCP web search using perplexity without any API KEYS

Google Search Tool

web-agent-master

A Playwright-based Node.js tool that bypasses search engine anti-scraping mechanisms to execute Google searches. Local alternative to SERP APIs with MCP server integration.

611

Naver Search MCP Server

isnow890

MCP server for Naver Search API integration. Provides comprehensive search capabilities across Naver services (web, news, blog, shopping, etc) and data trend analysis tools via DataLab API.

Baidu AI Search

baidubce

appbuilder-sdk, 千帆AppBuilder-SDK帮助开发者灵活、快速的搭建AI原生应用

583