[mashagua]

中文

新增 aws-mcp 服务入口，通过 AWS 官方 MCP Proxy 的本地 stdio 进程连接 AWS 托管 MCP Server。它与 市场技能合集 #226 分开登记，互不构成硬依赖；不是把托管服务部署到本机，也不会安装其他宿主插件。

• 两个发布包均固定到 1.7.0：mcp-proxy-for-aws-cli 包装包通过 uvx --from 获取，实际 mcp-proxy-for-aws 代码包通过 --with 获取；两者都使用明确的 wheel HTTPS URL 和 SHA-256，没有 latest 或无摘要回退。1.7.0 指代理版本，不是远端托管服务版本。
• 默认 --read-only、--disable-telemetry，不加 --skip-auth；端点和操作默认区域明确为 us-east-1。只读筛选依赖远端注解，不能代替 IAM，不承诺所有账户 API 或所有只读调用免费。未填写未经实测的工具数量。
• Apache-2.0 依据为已核对发行包内的 LICENSE/NOTICE；community / allowed，维护者未验证，upstreamEndorsed=false，通用 cloud 图标。Sidecar 的包身份/ref/摘要、审核 ref 和日期保持一致；实际代码包另有摘要约束，详见 review.md。
• 双语简介、详情和安装/使用说明披露 Python >=3.10,<3.15、uv/uvx、网络、用户自行配置的 AWS 身份/凭据、最小 IAM 权限、区域、条款、费用及数据边界。安装不自动登录、申请权限、安装 AWS CLI/技能或创建云资源；缺依赖/连接/授权时停止，不编造成功结果。当前 authType 枚举没有 SigV4，因此用 unknown 并在正文准确说明，不伪装为匿名、Bearer 或已验收的 OAuth。
• 只新增两份 JSON 元数据及 install/usage/review 说明，不复制上游源码、发行包、SDK 或凭据。根统计 25 → 26、MCP 9 → 10，同步更新一个现有测试中的固定数量断言；不修改 Schema、客户端或其他条目。

English

Add an aws-mcp service listing for the managed AWS MCP Server via the official AWS MCP Proxy and local stdio. It is separate from the companion skill collection, is not a local deployment of the managed service and does not configure other hosts.

Pin both the metadata-only CLI wrapper and implementation to 1.7.0 wheels by immutable HTTPS URL and SHA-256, using uvx --from/--with. Keep read-only mode and optional telemetry suppression by default, without anonymous fallback. The proxy version does not pin the remote backend/tool inventory. No unobserved tool count or runtime readiness is claimed.

The independent community listing records Apache-2.0 evidence from the published archive, unverified maintainers, generic branding and no upstream endorsement. Bilingual metadata and instructions cover local runtimes, credentials/IAM, distinct endpoint/operation Regions, terms, charges, data handling, explicit authorization and failure behavior. SigV4 is accurately disclosed in text; the current schema lacks that enum, so authType remains unknown rather than falsely claiming none/Bearer/OAuth. Only catalog metadata/docs and the corresponding count assertion change.

验证 / Validation

• node scripts/validate-registry.mjs — PASS, 26 entries.
• node scripts/catalog/validate-registry.mjs --require-sidecars — PASS.
• node --test scripts/catalog/validator.test.mjs — PASS, 16/16. The initial failure was the old 25-entry/9-MCP assertion; it now matches the added listing.
• Downloaded both published wheels; verified SHA-256, byte sizes, distribution/version/Python metadata and CLI entry point. LICENSE/NOTICE and relevant CLI/filter source bytes match release commit 22f1b3f8b7c4ef37112114b4af3d6c5a6c0a83bb. No Python imports/execution were used for inspection.
• uv pip compile --no-deps --no-config --generate-hashes accepted the two exact wheel requirements and hashes; this checks artifact source resolution only, not full dependency installation or runtime startup.
• Static checks confirm install/connection/doc examples match, package/ref/review dates agree, declared flags exist in the actual release, and local documentation links resolve. Public-information checks passed.

macOS 补测与修正 / Follow-up acceptance and fix (2026-10-25)

• 实际使用固定 uvx 定义，在 Python 3.12.13 / uv 0.11.2 隔离环境安装 76 个本平台适用包并运行上游代理。真实 AWS 凭据未继承，显式空 credentials/config/login-cache，禁用 IMDS。
• 默认签名模式明确报缺凭据；单独授权的匿名只读变体完成 initialize、完整 tools/list（6 个唯一工具）、公开文档检索与正文读取，调用 isError=false。默认目录仍保留 SigV4、只读和遥测关闭，没有匿名降级。
• DesireCore 10.0.187 真实 GUI 暴露 PyPI 版本 URL 的包身份兼容问题；当前 dev 的一致性函数也复现 acquisition.source 不匹配。仅把 provenance URL 改为包主页，保留 ref=1.7.0 与两个 wheel URL/摘要后，函数通过，真实 GUI 从“仅收录”恢复“可接入”。
• 真实 DesireCore 连接 owner 对匿名变体返回 connected / 6 tools；通过正常配置 API 接入独立测试 Agent 后，真实 GUI 对话经过工具审批调用文档检索，审计 success，3 条 URL 与独立探针一致。默认模式的 GUI“测试连接”清楚显示缺凭据。测试变体已通过正常 owner 移除，工具也已消失。
• 仍有主仓库问题：默认安装任务在准备阶段停止后，记录仍为 installing，资源卡片的来源标签却显示“已安装”，详情离线。没有把该默认安装记为验收成功；此显示/任务收尾问题未在本目录 PR 修复。

The actual pinned proxy ran in isolated macOS/Python 3.12.13 with uv 0.11.2. Default signed mode explicitly failed without credentials; a separately authorized anonymous read-only variant initialized, discovered six unique tools and searched/read public documentation. The real DesireCore owner also connected the public variant, and an actual GUI chat invoked its MCP search through normal approval with a successful audit and three matching URLs. The variant was removed through the normal owner afterward.

A live catalog test identified the versioned-PyPI-URL identity mismatch also present in current dev. Switching only the identity URL to the package homepage, while preserving the version ref and both artifact hashes, restored the connectable entry. Default signed installation remains incomplete, and a stopped installing record is misleadingly labeled installed in Resources while details remain offline; that main-repository UI/lifecycle issue is not fixed here.

未读取真实 AWS 凭据、登录 AWS、调用账户业务或创建资源；Windows/Linux、所有工具/业务、全部依赖制品安全性未验收。平台字段仍只是上游声明。未运行本地全量测试或全量 typecheck，审核不是安全认证。

No real AWS credentials, sign-in, account operations or resource creation were used. Windows/Linux, every tool/business workflow and complete dependency safety remain unverified. Platform fields reflect upstream declarations; no full test suite or full typecheck ran, and this is not a security certification.