mcp-rest-api
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_BEARER | No | Bearer token for token-based authentication | |
| REST_BASE_URL | No | Base URL for the REST API (e.g., https://api.example.com) | |
| AUTH_APIKEY_VALUE | No | API key value for API key authentication | |
| AUTH_BASIC_PASSWORD | No | Password for Basic Authentication | |
| AUTH_BASIC_USERNAME | No | Username for Basic Authentication | |
| REST_ENABLE_SSL_VERIFY | No | Enable or disable SSL verification for self-signed certificates | true |
| AUTH_APIKEY_HEADER_NAME | No | Header name for API key authentication (e.g., X-API-Key) | |
| REST_RESPONSE_SIZE_LIMIT | No | Maximum response 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 endpoint and get detailed response information. Base URL: https://api.example.com | SSL Verification enabled (see config resource for SSL settings) | Authentication: No authentication configured | No custom headers defined (see config resource for headers) | The tool automatically: - Normalizes endpoints (adds leading slash, removes trailing slashes) - Handles authentication header injection - Applies custom headers from HEADER_* environment variables - Accepts any HTTP status code as valid - Limits response size to 10000 bytes (see config resource for size limit settings) - Returns detailed response information including: * Full URL called * Status code and text * Response headers * Response body * Request details (method, headers, body) * Response timing * Validation messages | Error Handling: - Network errors are caught and returned with descriptive messages - Invalid status codes are still returned with full response details - Authentication errors include the attempted auth method | See the config resource for all configuration options, including header configuration. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| REST API Usage Examples | Detailed examples of using the REST API testing tool |
| Response Format Documentation | Documentation of the response format and structure |
| Configuration Documentation | Documentation of all configuration options and how to use them |
TDQS
Scored across 1 tool
Only one tool exists, so there is no possibility of confusion between tools.
With a single tool, naming is trivially consistent and follows a clear verb_noun pattern.
The server is named 'mcp-rest-api' but only provides one testing tool, which is far too few for comprehensive REST API interaction; typically multiple CRUD tools are expected.
The server lacks fundamental operations like create, read, update, and delete; it only offers a test request tool, leaving major gaps for any practical REST API workflow.