No user-submitted related servers found.
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.