Define canonical MCP and Vendor architecture

[fredporter]

Summary

• establish MCP as an external adapter boundary, not an internal service bus
• identify the SDK-backed TypeScript bridge as the only viable current base
• document duplicated/non-compliant uCore and uCode MCP paths for hard-cut removal
• define one udos-mcp gateway, initial read-only tool surface, security standards, and PR sequence
• supersede the MCP-for-everything policy
• record the approved Vendor shortlist and rejected provider bridges

Evidence

• direct MCP initialize, initialized, tools/list, and unavailable-service error probe
• cross-repository tracked-file and active-config inventory
• official MCP transport, architecture, tools, registry, SDK, Inspector, reference server, and GitHub server review
• Vendor hygiene check: 18 manifest entries, 10 RAW repos/zips, passed
• documentation non-regression passed
• planning governance passed

Vendor intake completed locally

• modelcontextprotocol/typescript-sdk
• modelcontextprotocol/inspector
• modelcontextprotocol/servers
• modelcontextprotocol/registry
• github/github-mcp-server

Vendor is not itself a Git repository, so its local catalogue changes are intentionally not part of this uCore PR.