mcp-server-dump

The tool's core functionality involves executing user-provided commands (for 'command' transport) or connecting to user-specified HTTP endpoints. While this is the intended design, it inherently relies on the user providing trusted commands or server endpoints. Input validation and path sanitization are implemented for context files, including protection against directory traversal and file size limits. OAuth authentication involves fetching URLs from server metadata, which is standard but carries the inherent risk of interacting with potentially malicious identity providers, although the client implements PKCE and secure token caching. File-system operations for token and registration caches use secure permissions (0o600) and hashed filenames.