api-testing-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| send-post-requestD | send the post request |
| send-get-requestC | send the get request |
| send-put-requestD | send the put request |
| send-delete-requestD | send the delete request |
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 4 tools
Each tool corresponds to a distinct HTTP method (DELETE, GET, POST, PUT) with no overlap, making it trivial for an agent to select the correct one.
All tools follow a consistent pattern: 'send-{method}-request' with lowercase and hyphens, ensuring predictability.
With 4 tools covering the main HTTP methods (CRUD), the count is well-suited for an API testing server—neither too few nor too many.
The set covers the most common HTTP methods, but omits PATCH and other less common ones. For basic testing, it is sufficiently complete.