mcp-api-tools
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| http_requestA | Make an HTTP request with full control over method, headers, body, authentication, and timeouts. Returns status, headers, body, and timing information. |
| api_healthC | Check the health of multiple API endpoints. Returns status, response time, SSL certificate validity, and optional response body validation for each endpoint. |
| jwt_decodeA | Decode a JWT token without verification. Returns header, payload, expiry, issued-at time, and whether the token is expired. |
| url_parseA | Parse a URL into its component parts: protocol, host, port, path, query parameters, hash, and more. Can also build a URL from parts. |
| header_analyzerB | Analyze HTTP response headers for security (HSTS, CSP, X-Frame-Options, etc.), caching directives, CORS configuration, cookies, and server information. Provides a security grade. |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: health checks, header analysis, HTTP requests, JWT decoding, and URL parsing. The descriptions specify unique domains (API monitoring, security analysis, HTTP client, token inspection, URL manipulation), making misselection unlikely.
All tool names follow a consistent snake_case pattern with clear, descriptive verb_noun combinations (e.g., api_health, header_analyzer). The naming is uniform and predictable across all five tools, enhancing readability and agent usability.
With 5 tools, the count is well-scoped for an API utilities server, covering essential operations without bloat. Each tool earns its place by addressing a distinct aspect of API testing and analysis, making the set manageable and focused.
The tool surface is nearly complete for API testing and analysis, covering health checks, security headers, HTTP requests, JWT handling, and URL parsing. A minor gap exists in lacking tools for more advanced scenarios like API mocking or load testing, but core workflows are well-supported.