IEEE 2030.5 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IEEE2030_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| IEEE2030_BASE_URL | Yes | Base URL of your IEEE 2030.5 server | |
| IEEE2030_INSECURE | No | Skip SSL verification (dev only) | false |
| IEEE2030_KEY_PATH | No | Path to private key file (if separate) | |
| IEEE2030_CERT_PATH | No | Path to certificate file (.pem, .crt) | |
| IEEE2030_KEY_VALUE | No | Private key content as string | |
| IEEE2030_CERT_VALUE | No | Certificate content as string |
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 | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ieee2030_statusB | Check IEEE 2030.5 client status and configuration |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| ieee2030_navigation_guide | Comprehensive guide for navigating IEEE 2030.5 resources using HATEOAS principles |
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 possibility of confusion between tools.
With a single tool, naming is trivially consistent. The name follows a clear pattern (ieee2030_status).
The server claims to cover IEEE 2030.5, a complex standard, but offers only one tool. This is an extreme mismatch for the apparent scope.
A single status-check tool is severely insufficient for the domain. Essential operations like configuration, device management, and data exchange are missing.