Local-MCP-Bridge
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 |
|---|---|
| health_checkA | Return basic server health without exposing host or project information. |
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 possibility of confusion or overlap. It is clearly distinct by default.
The single tool name 'health_check' follows a standard snake_case verb_noun pattern, which is consistent and predictable.
The server has only one tool, which is extremely thin for most server purposes. However, if the sole purpose is health monitoring, it could be seen as minimal but functional; generally, this is borderline.
A single health check tool provides almost no functional coverage. There are no other operations, and the server's purpose seems to be only to verify liveness, which is severely limited.