feat(mcp): add enterprise diagnostic mock server#2670
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@reachjalil is attempting to deploy a commit to the Different AI Team on Vercel. A member of the Team first needs to authorize it. |
Agent integration rehearsal update — 2026-07-11This source branch is published at e1569ec and was exercised in the independent combined rehearsal, #2675. The rehearsal confirmed the realistic pre-registered ServiceNow-style confidential-client path, the read-only catalog test, distinct credential and provider-permission failures, stable UI row targeting, bounded callback replacement, listener cleanup, fail-closed runtime controls, and operation-only denial and throttling faults. Status remains deliberately separate:
This PR remains based on upstream dev because the controlled parent branch exists only on the Jalil fork. #2674 is the approval ledger; this PR is the source and evidence branch. |
Important
Parent MCP diagnostics release: #2674
Parent integration status: Not integrated. Verified by Jalil: Not started.
This source PR remains the workspace for its focused fixes and evidence. After Jalil reviews and accepts this level, the verified change will be integrated into
feature/mcp-diagnostics-releaseand the parent ledger will be updated. Because the parent branch intentionally exists only on Jalil's fork, GitHub cannot use it as the literal base of an upstream-repository PR; this PR therefore remains based ondevwhile pointing to the parent release tracker.Intent
Provide a deterministic enterprise MCP diagnostic server that can run beside an isolated Den, exercise realistic ServiceNow and Microsoft OAuth/MCP behavior, and drive a safe read-only connection test from the Den Connections UI.
What changed
generic, ServiceNow, Work IQ, Microsoft enterprise, and Agent 365 Mail profiles with synthetic data only.POST /v1/mcp-connections/:connectionId/test, a credential-scoped read-only initialize/catalog/teardown probe with stable safe failures. It never starts authorization, DCRs, writes PKCE state, refreshes credentials, or invokes a tool.Enterprise references
mcp_serverscope, manual registration, Client Secret Post, and OAuth endpoint topology: https://www.servicenow.com/docs/r/intelligent-experiences/configure-client-connect-server.htmlMcpServers.Mail.Allmanifest contract: https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-mail-work-iq and https://learn.microsoft.com/en-us/microsoft-agent-365/developer/toolingMicrosoft marks the Mail contract as preview, so the identifiers are centralized and the fixtures record their verification date.
Security and correctness
Reviewer focus
scripts/mock-oauth-mcp-server.mjsand its enterprise/fault fixturesee/apps/den-api/src/capability-sources/external-mcp-client.tsurl-guard.tsPOST /v1/mcp-connections/:connectionId/testauthorization and read-only behaviorValidation
git diff --check./bin/openwork-hub check mcp mcp-diagnostic-mock-serverFollow-ups
This is the second of three independent MCP diagnostic PRs. It is based directly on
dev; overlapping MCP transport surfaces with the structured-diagnostics and live-tracing PRs will need normal merge sequencing.