mcp_cimd_server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| say_helloA | Say hello to someone. Args: name: The name to greet (defaults to 'world'). Returns: A friendly greeting. |
| cimd_resolveA | Resolve an OAuth client_id URL to its CIMD metadata document. Implements the server-side CIMD flow: validate the HTTPS URL, fetch the Client ID Metadata Document, validate the schema (client_id match, redirect_uris present, HTTPS redirect URIs), and cache the result with a TTL. SSRF protections are applied. Args: client_id: The client_id URL pointing to the CIMD document (e.g. https://client.example.com/oauth/metadata.json). Returns: The validated client metadata, or an error payload matching the CIMD error semantics (invalid_client / invalid_client_metadata) if resolution fails. |
| cimd_cache_infoA | Inspect the CIMD metadata cache (admin/management tool). Returns: Cache contents with remaining TTL seconds per client_id. |
| cimd_clear_cacheA | Force re-fetch of all cached CIMD metadata (admin tool). Returns: A confirmation message. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: say_hello is a basic greeting, cimd_resolve performs the actual CIMD resolution with caching, cimd_cache_info inspects the cache, and cimd_clear_cache resets it. There is no functional overlap between them.
The cimd_* tools share a clear prefix and describe their actions (resolve, cache_info, clear_cache). However, cimd_cache_info is more noun-like than verb-first, and say_hello breaks the prefix pattern. Overall, the naming is consistent enough to be predictable.
With 4 tools, the server is compact and focuses on the core CIMD resolution domain plus cache management. The unrelated say_hello tool adds a bit of noise but does not make the set feel over- or under-scoped.
The server covers the essential flow: resolving a client_id with caching, viewing cache contents, and clearing the cache. A minor gap is the lack of a tool to invalidate a specific cache entry without clearing all, but for a small CIMD server this is workable.