MCP.so
ログイン
C

Clavis MCP Server

@KN0WBOT

基本情報

カテゴリ

検索

トランスポート

stdio

作者

KN0WBOT

投稿者

KN0WBOT

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.

Clavis MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

Clavis MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。

概要

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

よくある質問

1

What services does Clavis Mcp Server support?

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

2

How does credential encryption work?

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

3

How does token refresh work?

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

4

Is there rate limiting?

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

5

What audit capabilities does it provide?

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

コメント

「検索」の他のコンテンツ