SignalRank MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNALRANK_API_URL | No | Base URL of the SignalRank-RAG API. | http://127.0.0.1:8000 |
| SIGNALRANK_SERVICE_TOKEN | Yes | Service token used to authenticate with SignalRank-RAG. |
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 |
|---|---|
| searchA | Search SignalRank and return ranked evidence without LLM synthesis. |
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 1 tool
Only one tool exists, so there is no risk of selecting between overlapping operations. The single 'search' tool has a clear, singular purpose.
The tool name 'search' is a clear, conventional verb, but with only one tool there is no broader verb_noun or convention pattern to evaluate. No inconsistency is present, though the naming style cannot be fully assessed.
A single search tool forms a thin but functionally valid server for ranked-evidence lookup. It is at the low end of acceptable scope and may leave agents wanting supplementary operations.
The search operation covers the core retrieval use case, but the one-tool surface offers no way to fetch evidence by ID, filter results independently, or inspect sources. Secondary workflows may therefore dead-end.