MyMCPTools MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MYMCPTOOLS_MCP_URL | No | Override the upstream endpoint the adapter talks to. |
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 |
|---|---|
| search_mcp_serversD | – |
| get_mcp_serverD | – |
| get_server_statusD | – |
| get_server_historyD | – |
| list_server_incidentsD | – |
| list_schema_driftD | – |
| list_categoriesD | – |
| get_catalog_statsD | – |
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 8 tools
Tool names target distinct aspects (search, get, status, history, incidents, schema drift, categories, stats) with only possible overlap between get_mcp_server and search_mcp_servers. Without descriptions, ambiguity is minimal.
Inconsistent verb usage: mixes 'search_', 'get_', and 'list_' prefixes. Also singular vs plural (get_mcp_server vs search_mcp_servers) and no clear pattern.
8 tools is a reasonable number for a server focused on querying and monitoring MCP servers, not overly large or small.
Tools cover searching, fetching details, status, history, incidents, schema drift, categories, and catalog stats, but missing common operations like create, update, or delete. Domain completeness is unclear without descriptions.