You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to the same MCP-2123 branch: once the sanitizer fix makes the
container actually match, two more defects surface for official-registry
slash-named servers (verified end-to-end by CEO on com.pulsemcp/google-flights):
1. os.MkdirTemp rejects a pattern containing a path separator, so the three
extraction temp-dir patterns (mcpproxy-scan-%s-, -scan-full-%s-,
-scan-tools-%s-) failed for '/'-containing names and source fell back to
'none'. Sanitize the name via dockernaming.SanitizeServerName first.
2. handleGetScanReportByJobID read the raw chi jobId param. Scan ids are
scan-<serverName>-<ts> and contain '/', arriving percent-encoded, so the
report endpoint 404'd. Decode via decodePathParam (same pattern the
/servers subtree uses).
Verified result: source_method=docker_extract, 23 files extracted,
tools_exported=3, report endpoint HTTP 200. Adds regression tests:
TestScanTempDirPatternHandlesSlashNames, TestDecodePathParamScanJobID.
Related #MCP-2123
Co-Authored-By: Paperclip <noreply@paperclip.ing>
0 commit comments