mcp-infra
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| get_processes_by_portsA | Return all running processes listening on the given ports. Args: ports: List of port numbers to check. |
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 ambiguity or overlap with other tools, making disambiguation perfect.
The single tool name follows a clear verb_noun pattern (get_processes_by_ports), and with no other tools, consistency is inherently perfect.
A single tool is too few for a server named 'mcp-infra', which suggests a broader infrastructure management scope, making this an under-scoped and incomplete tool surface.
The tool surface is severely incomplete for an infrastructure domain; it only provides a specific query for processes by ports, lacking any other operations like system monitoring, resource management, or general process handling.