Skip to main content
Glama
mcp-api-tools
by rog0x

@rog0x/mcp-api-tools

HTTP/API testing tools for AI agents, built on the Model Context Protocol.

Tools

http_request

Make any HTTP request (GET, POST, PUT, DELETE, PATCH, HEAD, OPTIONS) with full control over headers, body, authentication, and timeouts. Returns status code, response headers, body, and timing information.

api_health

Check the health of multiple API endpoints in parallel. Returns HTTP status, response time, SSL certificate validity and expiry, and optional response body validation. Includes a summary with counts of healthy, unhealthy, and errored endpoints.

jwt_decode

Decode a JWT token without cryptographic verification. Returns the decoded header and payload, issued-at time, expiry time, and whether the token is currently expired.

url_parse

Parse a URL into its component parts (protocol, host, port, path, query parameters, hash) or build a URL from individual parts.

header_analyzer

Analyze HTTP response headers for security posture (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy), caching directives, CORS configuration, and cookie attributes. Provides a letter grade for security. Can fetch headers from a live URL or analyze a provided headers object.

Related MCP server: MCP HTTP Tester

Installation

npm install
npm run build

Configuration

Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "api-tools": {
      "command": "node",
      "args": ["D:/products/mcp-servers/mcp-api-tools/dist/index.js"]
    }
  }
}

Claude Code

claude mcp add api-tools node D:/products/mcp-servers/mcp-api-tools/dist/index.js

Examples

Make a POST request:

Use http_request to POST to https://httpbin.org/post with JSON body {"key": "value"}

Check API health:

Use api_health to check these endpoints: https://api.github.com, https://httpbin.org/get

Decode a JWT:

Use jwt_decode to decode this token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...

Parse a URL:

Use url_parse to break down https://example.com:8080/api/v1?key=value&debug=true#section

Analyze security headers:

Use header_analyzer to check security headers for https://github.com

License

MIT

Available Tools

5 tools
api_healthC

Check the health of multiple API endpoints. Returns status, response time, SSL certificate validity, and optional response body validation for each endpoint.

Inputs: endpoints (required).

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.

Inputs: headers, url.

http_requestA

Make an HTTP request with full control over method, headers, body, authentication, and timeouts. Returns status, headers, body, and timing information.

Inputs: method (required), url (required), headers, body, +3 more.

jwt_decodeA

Decode a JWT token without verification. Returns header, payload, expiry, issued-at time, and whether the token is expired.

Inputs: token (required).

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.

Inputs: url, build_params.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides HTTP client capabilities to AI agents with 9 tools for REST API testing, including GET, POST, PUT, PATCH, DELETE, batch requests, and URL health checks, using pure Python stdlib.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to inspect, test, validate, compare, and debug HTTP APIs through a structured toolkit, with features such as secret redaction, response contract validation, regression comparison, health checks, and incident investigation workflows.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to audit URLs for security headers, generate CSP Level 3 policies, compute SRI hashes, evaluate WCAG 2.2 contrast, and remediate headers.
      MIT