01 — AgentData MCP connector repair + 1k report verification

• Macro: AGENTDATA_MCP_CONNECTOR_REPAIR_AND_1K_REPORT_VERIFICATION
• Date: 2026-05-23
• Host: MacBook/dev
• Outcome: AGENTDATA_MCP_CONNECTOR_REPAIR_AND_1K_REPORT_VERIFICATION_PASS
• Scope: diagnosis + verification only — no IU feature work, no production DB mutation.

1. Reported symptom

GPT-side AgentData MCP calls failed with:

MCP SSE probe returned 404 from incomexsaigoncorp.vn

2. Root cause — GPT-side connector misconfiguration (two compounded faults)

The AgentData MCP service itself is healthy. The 404 is entirely a GPT-side endpoint-config error.

Fault A — wrong host. GPT targets the bare domain incomexsaigoncorp.vn. That domain serves the Incomex Saigon Corp WordPress marketing website, not the MCP service. Every path on it 404s. The MCP service runs on the subdomain vps.incomexsaigoncorp.vn.

Fault B — wrong transport. GPT performs an SSE probe. The AgentData MCP service exposes only Streamable HTTP, at path /api/mcp. There is no SSE endpoint anywhere — /sse returns 404 on both the bare domain and the VPS subdomain. An SSE probe can never succeed.

GPT is also likely missing the X-API-Key request header (see §4).

3. Evidence

Routing probe (HTTP status):

URL	status	note
incomexsaigoncorp.vn/sse	404	bare domain = WordPress site
incomexsaigoncorp.vn/api/mcp	404	bare domain
incomexsaigoncorp.vn/mcp	404	bare domain
vps.incomexsaigoncorp.vn/sse	404	no SSE endpoint exists
vps.incomexsaigoncorp.vn/mcp	404	wrong path
vps.incomexsaigoncorp.vn/api/mcp	200	the working endpoint
vps.incomexsaigoncorp.vn/api/health	200	service healthy

Service health (/api/health): status: healthy; qdrant ok (13.4 ms), postgres ok (1.8 ms), openai ok; data_integrity document_count 4325 / vector_point_count 9180 / ratio 2.12 / sync_status warning.

MCP initialize POST to /api/mcp with X-API-Key → HTTP 200, serverInfo: {name: agent-data-mcp, version: 1.0.0, connectorSchemaVersion: gpt-agent-data-2026-05-14.2}. The same request without the key → HTTP 401 (auth is enforced).

4. Verified working endpoint (the fix for the GPT connector)

• URL: https://vps.incomexsaigoncorp.vn/api/mcp
• Transport: Streamable HTTP (MCP protocol 2024-11-05). Not SSE.
• Auth header: X-API-Key: <key> — the value lives in the VPS deployment secret and in Claude Code's ~/.claude.json agent-data server config; it is not reproduced in this report.
• serverInfo.connectorSchemaVersion is gpt-agent-data-2026-05-14.2 — the service is purpose-built for the GPT AgentData connector. GPT only needs the correct URL + HTTP (not SSE) transport + the key header.

Claude Code's own agent-data MCP server is already configured exactly this way (type: http, this URL, X-API-Key header) and works — list_documents / get_document / search_knowledge / batch_read all succeed. The discrepancy is purely GPT-side.

5. Cowork / Larkbase connector — ruled out

The Larkbase connector (lark-mcp) is a local stdio process (npx @larksuiteoapi/lark-mcp); it shares no route with the VPS HTTP service. The S177 Cowork remote HTTP/SSE transport is a future sprint, not yet deployed. The AgentData route /api/mcp is intact and verified. Cowork / Larkbase changes did not affect the AgentData MCP route.

6. 1k IU Core report verification

Path knowledge/dev/laws/dieu44-trien-khai/v0.6-iu-core-1k-vector-operator-ui-delivery-acceptance-open-goal/ — all 7/7 reports present:

01 pre-check · 02 vector-sync foundation · 03 operator-runtime concurrency lease · 04 operator surface / delivery / text-as-code · 05 DOT / five-layer / acceptance · 06 final report · 07 next-macro package.

• Listable — list_documents returns 7 items, next_offset null.
• Readable — batch_read (full) returns all 7, every doc truncated:false; 06-final-report.md is 5649 chars, outcome IU_CORE_1K_VECTOR_OPERATOR_UI_DELIVERY_ACCEPTANCE_PASS.
• Searchable — search_knowledge("IU Core 1k vector operator UI delivery acceptance final report PASS") returns 06-final-report.md as the top hit (score 1.21).

No report missing → no re-upload required.

7. Production DB

Not touched. This macro performed read-only AgentData KB queries + HTTPS health/routing probes only. No production directus Postgres mutation.

8. Outcome

AGENTDATA_MCP_CONNECTOR_REPAIR_AND_1K_REPORT_VERIFICATION_PASS — MCP cause identified and a verified working endpoint confirmed; 1k reports list/read/search verified; the IU vector boundary rule recorded (doc 02); no production mutation.