Multi-Protocol MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | 监听特定内网IP（例如：192.168.1.100） | |
| MCP_PORT | No | 端口，默认3001 | |
| MCP_DOMAIN | No | 内网域名 | |
| MCP_BASE_PATH | No | 基础路径，默认 /mcp |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mockfuncC | 这是一个模拟接口的工具 |
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 confusing it with others. The tool is trivially distinct.
There is only one tool name, so there is no pattern to be inconsistent with. The name is at least a valid identifier.
The server is named 'Multi-Protocol MCP Server', implying support for multiple protocols, yet it exposes only a single vague mock tool. This is a severe mismatch between scope and implementation.
The single tool description is minimal and does not indicate any comprehensive coverage of multi-protocol functionality. There are no clear operations or lifecycle coverage, leaving the stated purpose unfulfilled.