A35 · Design the MCP Server Registry A35 · 设计 MCP 服务注册中心
Verified source经核实出处
Model Context Protocol is Anthropic-backed (MCP spec). Registry design asked at onsites. Credibility A.
Architecture架构
flowchart LR Dev --> Pub[Publish - signed manifest] Pub --> REV[Security review] REV --> REG[(Registry)] REG --> BROWSE[Catalogue UI / API] Client --> BROWSE BROWSE --> INST[Install to user scope] INST --> AGENT[Agent with tool exposed]
Key decisions关键决策
- **Signed manifests**: publisher key binds server to identity; client verifies signature on install.**签名 manifest**：发布者私钥绑定身份；客户端安装时验签。
- **Scoped permissions** declared in manifest (file access, network, shell); user consent before install.**manifest 声明权限**（文件/网络/shell）；安装前用户同意。
- **Security review tier**: verified badge for audited servers; warning for unreviewed.**安全审核分层**：已审核带徽章；未审核显示警告。
- **Version pinning & signed update channel** to prevent supply-chain attacks.**版本固定 + 签名升级通道**防供应链攻击。
Follow-ups追问
- Search / ranking? full-text + usage popularity + security tier weighting.搜索排序？全文 + 使用热度 + 安全层级加权。
- Runtime isolation? sandbox per MCP server; see O37.运行时隔离？每 MCP server 沙箱（见 O37）。