mcp-api-tools
Related Servers
Alternatives to mcp-api-tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables 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
- AlicenseAqualityCmaintenanceEnables AI agents and developers to audit any URL or domain for seven critical OWASP HTTP security headers, returning an A+ to F grade plus actionable Nginx, Apache, Caddy, and Cloudflare remediation snippets. It also probes /.well-known/security.txt and /security.txt to surface responsible vulnerability disclosure contacts, bug bounty scopes, and PGP keys.2MIT
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with free, keyless QA and LLM-testing tools over Streamable HTTP, including prompt-injection and PII scans, TLS/header/CORS audits, hallucination and RAG checks, eval contracts, and JSON/YAML/CSV utilities across the full server or three focused packs. Every tool returns an actionable verdict such as a pass/fail, score, or diff.MIT
- AlicenseNot gradedqualityCmaintenanceProvides 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
- AlicenseAqualityDmaintenanceEnables AI agents to send HTTP requests to any endpoint with full control over methods, headers, query parameters, and request bodies.120 npmMIT
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.