$ loading_
Inspect request headers to debug MCP host and client custom header behavior.
This MCP tool appears intended to inspect request headers for debugging custom header implementations in MCP hosts/clients; it declares no required secrets or remote endpoints, and the source is open for review. No clear high-risk red flags are present in the provided material, but its code-execution nature, access to header data, and low adoption suggest an overall caution rating.
The material states no keys or environment variables are required, which is a positive sign; however, its purpose is to inspect request headers, and headers may contain Authorization, Cookie, or custom tokens, creating a normal risk of exposing sensitive credentials through debugging output or logs.
No remote endpoint or external service integration is declared, and the material does not show data being sent to third-party network locations. Based on the provided information, no explicit data egress path is evident.
The system flags it as executes-code, meaning it runs locally as an MCP service and has code-execution characteristics. This is a normal capability for MCP tools, and the provided material does not show requests for abnormal system privileges beyond what header debugging would typically require.
Its core function is to read and inspect MCP request headers, meaning it can access session-level communication metadata; if those headers contain user identifiers, session information, or auth fields, it may handle sensitive data. The material does not state that it reads or writes local files, and no obvious overbroad access is described.
The source is publicly available under the MIT License, which improves auditability and lowers risk; however, it comes from a third-party registry, has 0 stars, and an unknown maintenance status, so the trust baseline is limited and caution is still appropriate.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "debug-test-mcp" yet — see the docs or source repo.
Inspect all headers received in this MCP request and indicate whether X-Trace-Id, X-Env, and Authorization are present.
A full header list showing whether the target custom headers exist and their values.
Compare the expected request headers with the actual received headers, and identify missing, duplicated, or incorrectly cased headers.
A header diff analysis that helps pinpoint propagation errors in the host or client implementation.
Inspect authentication-related headers in the current MCP request and confirm whether Authorization or other token headers were forwarded to the server.
An authentication header check showing which security-related headers were passed through, missing, or modified.
Debug Node.js programs via V8 Inspector with breakpoints and variable inspection.
Diagnose infrastructure issues with ports, DNS, logs, system health, and SSL checks.
Use 65 deterministic tools to reliably test MCP protocols across transports.
Diagnose system issues, monitor resources, inspect logs, and test connectivity.
Test all MCP protocol features when building and validating clients.
Enable AI to run live GDB debugging sessions on binaries and processes.