Universal MCP Bridge & Proxy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| port | No | Port to listen on when using SSE transport (CLI flag --port). | 8080 |
| config | Yes | Path to the universal-mcp.yaml configuration file (CLI flag --config). | |
| transport | No | Transport mode for the MCP server, either 'stdio' or 'sse' (CLI flag --transport). | stdio |
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 |
|---|---|
| findPetsByStatusD | Finds Pets by status |
| getPetByIdC | Find pet by ID |
| run_text_analyzerC | Calculate SHA256 checksum and word stats of a given text. |
| run_sys_healthC | Quick system health check reporter (disk, memory, uptime) |
| db_sample_schemaC | Inspect tables and column schemas in database 'sample.db' |
| db_sample_queryC | Run an SQL query on database 'sample.db' (READ-ONLY) |
| exec_curlC | Executes 'curl'. Help summary: Usage: curl [options...] -d, --data HTTP POST data -f, --fail Fail fast with no output on HTTP errors -h, --help Get help for commands -o, --output Write to file instead of stdout -O, --remote-name Write output to... |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_manifest | Get dynamic manifest of all mounted tools and policies. |
TDQS
Scored across 7 tools
Each tool targets a clearly different operation: pet lookup by status vs. by ID, text analysis, system health, DB schema inspection, DB query, and curl execution. The only mild overlap is findPetsByStatus vs getPetById, but list-vs-get semantics distinguish them. The bigger problem is thematic incoherence, not tool-to-tool confusion.
The set mixes camelCase (findPetsByStatus, getPetById) with snake_case (run_text_analyzer, db_sample_schema, exec_curl) and uses inconsistent verb styles (find/get/run/exec). Names are individually readable but the conventions change from tool to tool.
Seven tools is a reasonable count in isolation and none feels redundant. However, they are an unrelated grab-bag rather than a scoped surface, so the count is fine but the composition is arbitrary.
There is no coherent domain to cover: pet tools lack create/update/delete, the DB exposes only read-only sample/query with no schema mutation, and text/sys/curl are one-off utilities. As a 'universal bridge' the surface is a random sampling with major lifecycle gaps.