# api [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/rog0x/mcp-api-tools  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/api-9

## Description
HTTP client, JWT decode, header analysis for AI agents

## Tools
Capabilities this server exposes over MCP:

- **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…

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What api MCP server does

The api MCP server groups several HTTP and API inspection tasks behind MCP tools. It can send GET, POST, PUT, DELETE, PATCH, HEAD, and OPTIONS requests with caller-controlled headers, request bodies, authentication, and timeouts. Results include the HTTP status, response headers, response body, and timing data.

It also supports operational checks and inspection tasks. Multiple endpoints can be checked in parallel for status, response time, SSL certificate validity, certificate expiry, and optional response-body validation. URL parsing separates protocol, host, port, path, query parameters, and hash values, while URL construction accepts those parts as inputs.

## How it works

The api MCP server is built as a Node.js package and exposes its functionality through the Model Context Protocol. After the project is installed and built, an MCP client starts the generated `dist/index.js` file with Node. An agent can then invoke individual tools using structured inputs and receive structured results.

JWT inspection is deliberately limited to decoding. The `jwt_decode` tool returns the token header and payload, issued-at and expiry information, and the current expired state, but it does not verify the token's cryptographic signature. This makes it suitable for inspection and troubleshooting, not authentication decisions.

The `header_analyzer` tool can fetch headers from a live URL or assess a supplied headers object. Its review covers security headers such as HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy, along with caching directives, CORS configuration, and cookie attributes. It produces a letter-grade security result.

## Setup and configuration

Install dependencies and compile the project from its repository:

```bash
npm install
npm run build
```

For Claude Desktop, configure an MCP server whose command is `node` and whose argument points to the built `dist/index.js` file. The example uses a local filesystem path, so replace it with the path on your machine.

## Tools and capabilities

- `http_request`: Sends supported HTTP methods with headers, body, authentication, and timeout controls.
- `api_health`: Checks several endpoints concurrently and summarizes healthy, unhealthy, and errored results.
- `jwt_decode`: Decodes JWT headers and payloads without signature verification.
- `url_parse`: Breaks URLs into components or builds URLs from components.
- `header_analyzer`: Reviews supplied or fetched headers for security, caching, CORS, and cookie properties.

The api MCP server fits agents that need direct HTTP testing, basic service monitoring, token inspection, URL manipulation, or an initial review of web response headers.

_Full upstream README: https://allmcps.com/mcp/api-9/readme_

