mcp-tester-helper
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REST_ENABLE_SSL_VERIFY | No | Set to 'false' to skip SSL cert verification | true |
| REST_RESPONSE_SIZE_LIMIT | No | Max response body size in bytes | 10000 |
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| test_requestA | Test a REST API or OpenSearch endpoint on a specific stand. Auth is handled automatically. |
| db_queryA | Execute a read-only SQL query against a stand's PostgreSQL database. Use schema-qualified table names (e.g. "SELECT * FROM orders.users"). |
| os_searchB | Search an OpenSearch index using Query DSL. Use for log analysis and data queries. |
| os_indicesB | List available OpenSearch indices with doc counts and sizes. |
| os_mappingsA | Get field mappings for a specific OpenSearch index. |
| list_servicesA | List available stands and their services, databases, and OpenSearch endpoints from the config file. |
| healthB | Check availability of a stand's infrastructure: services, OpenSearch, and PostgreSQL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Usage Examples | Examples of using all tools with different stands |
| Configuration Guide | How to set up config.json and .env |
| Response Format | Response structure documentation |
TDQS
Scored across 7 tools
Each tool targets a distinct operation: infrastructure listing, health checking, endpoint testing, SQL queries, and three OpenSearch operations (indices, mappings, search). No two tools have overlapping purposes.
Naming follows a mostly predictable pattern: OpenSearch tools use the prefix 'os_', database tool uses 'db_', and general tools use verb_noun (list_services, test_request). 'health' breaks the verb_noun pattern but is understandable.
Seven tools is a well-scoped set for a testing helper server, covering essential operations without being overwhelming or too sparse.
The tools provide comprehensive coverage for read-only testing and debugging of stands, including listing services, health checks, API tests, SQL queries, and OpenSearch exploration. No obvious gaps for the intended purpose.