LLM Pulse MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LLMPULSE_API_KEY | No | Your LLM Pulse API key. Optional; without it, the server starts in read-only mode. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| llmpulse_mcp_statusA | Check whether this wrapper is configured with an LLM Pulse API key and show setup details for the hosted MCP endpoint. |
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
With only one tool, there is no possibility of confusion between tools. The agent can clearly identify this single tool's purpose without ambiguity.
A single tool trivially follows a consistent naming pattern with itself. No inconsistencies or mixed conventions exist.
The server provides only one tool, which is too few for a meaningful integration. A status check alone does not justify an MCP server; typical servers offer multiple operations for interaction.
The server is severely incomplete: it only checks configuration status and offers no tools to actually use the LLM Pulse API. This creates a dead end for agents seeking to perform real tasks.