prophetkey-mcp
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| prophetkey_list_keysA | List all API keys stored in ProphetKey. Returns safe_keys (not real keys) for use with the local proxy. |
| prophetkey_get_key_infoA | Get detailed information about a specific API key (name, provider, safe_key, health status). Does NOT return the real key value. |
| prophetkey_proxy_statusA | Get the current status of the ProphetKey local proxy (running, port, keys count, request stats). |
| prophetkey_health_checkA | Run a health check on all stored API keys (expiry, usage, security score). |
| prophetkey_make_requestA | Make an API request through the ProphetKey proxy. The proxy automatically injects the real API key. The AI agent never sees the real key. |
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 5 tools
Each tool has a clearly distinct purpose: listing keys, retrieving key details, checking proxy status, running health checks, and making proxied requests. There is no meaningful overlap that would cause an agent to select the wrong tool.
All tools follow a consistent `prophetkey_` prefix with snake_case verb_noun names. The pattern is uniform and predictable across the entire set.
Five tools is a well-scoped size for this server's purpose. Each tool covers a distinct aspect of interacting with ProphetKey and its proxy without unnecessary bloat or redundancy.
The set covers the core workflows: discovering keys, inspecting key details, checking health, monitoring the proxy, and making authenticated requests. Lifecycle operations like adding or deleting keys are absent, but they appear intentionally handled outside the MCP server rather than being an obvious gap.