mcp-oracle-h
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ORACLE_BASE_URL | Yes | The base URL for the ORACLE-H server. | https://oracle-h.online |
| ORACLE_SIGNATURE_KEY | Yes | Your unique signature key used for human-on-the-loop validation requests. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| oracle_validateA | Submit a critical or irreversible action to ORACLE-H for human approval. The human operator will receive a Telegram notification with full context and can approve or reject. ALWAYS use this tool before executing any destructive, financial, or irreversible operation. Returns a request_id to use with oracle_poll_status to retrieve the decision. |
| oracle_poll_statusA | Check the current status of a validation request previously submitted via oracle_validate. Poll every 10-15 seconds until status is "approved" or "rejected". If "expired", the human did not respond in time — abort the action. |
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 2 tools
The two tools have completely distinct and non-overlapping purposes: oracle_validate is for submitting actions for human approval, while oracle_poll_status is for checking the status of those submissions. Their descriptions clearly differentiate them, with no ambiguity in functionality.
Both tools follow a consistent 'oracle_verb_noun' pattern (oracle_poll_status and oracle_validate), using snake_case and starting with the server prefix. This makes them predictable and easy to identify within the server's namespace.
With only two tools, the server feels thin for its apparent purpose of handling human approval workflows. While the tools cover the core submit-and-poll cycle, there are likely missing operations like listing pending requests or managing notifications, making the scope underdeveloped.
The server provides basic coverage for the human approval domain with submit and poll operations, but there are notable gaps. Missing tools for operations like canceling requests, viewing request history, or configuring approval settings limit its completeness, though agents can still work with the core workflow.