nodusai-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODUSAI_API_BASE | No | The base URL for the NodusAI API, used for grounding and signal generation. | https://nodusai.app |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nodus_pricingA | View NodusAI pricing and how to get started. Pay $1 USDC on nodusai.app → get a session token → use it for 3 Oracle signal queries. |
| nodus_get_signalA | Get an Oracle signal for a Polymarket or Kalshi prediction market. Requires a session token from nodusai.app ($1 USDC = 3 queries). Optionally pass a desiredOutcome (YES/NO) to focus the analysis. Returns probability, confidence, reasoning, and grounding sources. |
| nodus_verify_signalA | Retrieve grounding sources for a past signal to verify the Oracle's reasoning. |
| nodus_query_historyC | View your recent NodusAI oracle query history. |
| nodus_admin_statsA | [ADMIN] Platform stats: total queries, breakdown by platform. |
| nodus_admin_queriesC | [ADMIN] Full query registry dump. |
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 6 tools
Most tools have distinct purposes: admin queries vs. admin stats, get_signal vs. verify_signal, pricing vs. query history. However, 'nodus_admin_queries' and 'nodus_admin_stats' could be slightly confused as both provide administrative data, though their specific focuses differ.
All tool names follow a consistent 'nodus_' prefix with descriptive suffixes in snake_case, such as 'nodus_admin_queries', 'nodus_get_signal', and 'nodus_verify_signal'. This pattern is uniform across all six tools, making them predictable and easy to identify.
With 6 tools, the server is well-scoped for its purpose of providing Oracle signals and related administrative and historical functions. Each tool serves a clear role without unnecessary bloat, covering core operations like signal retrieval, verification, pricing, and history.
The tool set covers key aspects: signal retrieval, verification, pricing, query history, and admin functions. A minor gap is the lack of a tool for managing session tokens or handling payments directly, but agents can work around this using the provided pricing and signal tools.