clavis-mcp-server
Clavis MCP Server
为 Claude Desktop 和 MCP 服务器提供安全的凭据管理。
功能特性
🔐 加密凭据存储 (AES-256)
🔄 自动 OAuth 令牌刷新
⚡ 分布式速率限制
📊 完整的审计日志
Related MCP server: GhostKey
安装
npx @clavisagent/mcp-server或全局安装:
npm install -g @clavisagent/mcp-server在 Claude Desktop 中使用
将以下内容添加到您的 Claude Desktop 配置文件 (claude_desktop_config.json) 中:
{
"mcpServers": {
"clavis": {
"command": "npx",
"args": ["-y", "@clavisagent/mcp-server"]
}
}
}在 Claude Code 中使用
claude mcp add clavis -- npx -y @clavisagent/mcp-server可用工具
工具 | 描述 |
| 获取指定服务的有效访问令牌或 API 密钥 |
| 列出所有已存储凭据的服务 |
| 检查某项服务的凭据状态和过期时间 |
许可证
MIT
Available Tools
4 toolscall_serviceA
RECOMMENDED: Make an API call with server-side credential injection. The credential is fetched from the Clavis vault and injected into the upstream request server-side — the raw API key never enters this conversation. Prefer this over get_credentials: it eliminates prompt-injection exfiltration as an attack vector, because there is no secret in context to exfiltrate.
Inputs: url (required), method (required), service_name (required), data, +3 more.
check_credential_statusA
Check the validity and rate-limit status of credentials for a service without making any external API call. Queries only the Clavis vault (database + Redis). Returns validity, expiry, rate-limit headroom, and last-used timestamp.
Inputs: service_name (required).
get_credentialsA
LEGACY — returns raw credential data into this conversation. Prefer call_service for security: call_service injects credentials server-side so the raw API key is never exposed to the model. Use this only when you must hold the token itself (e.g. handing it to a library that cannot be proxied). Clavis handles token refresh and rotation automatically.
Inputs: service_name (required).
list_servicesA
List all services configured in Clavis for the authenticated developer.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: call_service proxies requests with server-side credential injection, get_credentials returns raw tokens for non-proxy use, list_services enumerates configured services, and check_credential_status inspects vault state without external calls. The overlap between call_service and get_credentials is explicitly addressed with usage guidance, so an agent can select correctly.
All tool names follow a consistent verb_noun pattern in lower_snake_case: call_service, get_credentials, list_services, check_credential_status. The verbs are distinct and clearly map to each tool's function.
With four tools, the set is tightly focused on core Clavis operations: using credentials, retrieving them, listing services, and checking status. This is the right granularity for a credential-management server—not bloated, not thin.
The tool surface covers the full lifecycle of interacting with Clavis-managed credentials: calling an upstream service, retrieving a raw credential when necessary, discovering available services, and checking status/rate limits. Missing features like credential creation or rotation are handled automatically by Clavis, so these are not gaps for the agent.
Related MCP Connectors
Credential broker for AI agents: scoped, revocable API access with policy enforcement and audit.
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
One MCP endpoint for Claude, GPT & Gemini: 100+ tools + no-code connectors + agent workers.
Zero-secret MCP gateway for AI agents: risk-scored, audited calls with human-in-the-loop approval.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEncrypted credential vault with a 21-tool MCP server. Store and manage LLM API keys, service API keys, and OAuth credentials — then let your AI agent list, reveal, rotate, rename, pause, and proxy calls through them.MIT
- AlicenseNot gradedqualityDmaintenanceMCP-native credential vault that enables AI agents to authenticate with external services without exposing secrets, supporting bearer, basic, OAuth2, and other auth patterns via MCP tools.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents and MCP clients to securely store, retrieve, and manage encrypted credentials without hardcoding API keys.AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceCredential vault for LLM agents that stores credentials encrypted and exposes MCP tools for authenticated HTTP requests, web scraping, and credential management, preventing AI assistants from seeing secrets.Apache 2.0