[aterga]

Summary

Follow-up to #211, which brought docs/anthropic-directory-submission.md up to Anthropic's current connector docs and logged the 2026-09-28 submission. This PR adds the submission-log entries the doc was meant to carry: that the submission date fell inside an OAuth disruption, the first reviewer feedback (by email on 2026-10-28, blocking the listing on one critical issue), and that the guard change the reviewers asked for has since landed on main, with what still stands between here and the reply.

History note: this branch originally did the same doc update as #211 from the same base. After #211 merged, main was merged in taking #211's version of the doc wholesale (its facts are the better ones: the listing's slug is icp, and the status date is 2026-10-27), so the only changes left against main are the log entries below. Main has been merged in again after #213 and #214, which updated blocker 2's description of the guard.

Related issues

Follows #211. References #203 (CIMD became the default registration mode on 2026-09-24, the migration behind the disruption), #212 (which already addressed the reviewers' optional unknown-app suggestion), and #213 / #214 (the guard change the reviewers asked for, merged 2026-10-28).

Changes

• Submission log, OAuth disruption: new bullet for 2026-09-25 to 2026-10-01, the OAuth disruption caused by the DCR-to-CIMD migration. A user reported DCR failing with HTTP 400 "redirect URI not permitted" on 2026-09-25, and OpenAI's reviewer could not complete the sign-in flow on 2026-10-01. A reviewer who tried the connector in that window would have failed at sign-in; the fix is live. The bullet says what to answer if reviewer feedback cites a sign-in failure.
• Submission log, reviewer feedback (2026-10-28): the Anthropic MCP Directory team's review. Critical: the financial guard matched method names only, so transfer, withdraw and swap passed it and reached the target canister; they asked for value-moving capability to be detected from the canister's own interface, for common non-standard value methods to be refused, for the server instructions to stop describing the guard as incomplete, and for a reply describing what the guard covers. Everything else passed, and the optional unknown-app suggestion was already addressed by Ask the user for an unknown app's URL instead of sending the model to a web search #212. The 2026-09-28 entry no longer says there was no feedback.
• Submission log, guard change landed (2026-10-28): Refuse every update to a canister that provides ICRC-1/ICRC-2 methods #213 detects a financial canister from the interface it publishes and requires a published, readable interface for any update call, refusing on a failed read; Refuse update calls whose method name carries a financial keyword #214 refuses method names carrying a financial keyword on every canister. Still pending before the reply: the server instructions' "not a complete filter" clause, a release reaching production, and confirming the reviewers' test app publishes its candid:service.

Testing

Docs-only change; no Rust or dashboard code touched.

• cargo build --locked --all-targets — not applicable (no code change)
• cargo test --locked --all-targets — not applicable (no code change)
• cargo fmt --all / cargo clippy --all-targets (tree is warning-free) — not applicable (no code change)
• npm test --prefix monitoring/mcp-status (if the dashboard changed) — not applicable
• bash .github/scripts/scan-internal-identifiers.sh origin/main...HEAD — clean
• git diff origin/main touches only the submission log of the one doc

Checklist

• I have read the Contributing guidelines.
• Docs (README / comments) updated for any user-visible change.
• No secrets, credentials, or internal-only information are included.

🤖 Generated with Claude Code

https://claude.ai/code/session_01Ui6YJGczXE8vZv2pjyxX2F

[Copilot]

🟡 Changes recommended

The documentation incorrectly implies v0.5.1 passed the staging-candidate gate, although it was published before that process was introduced for subsequent releases.

1 open issue

• Clarify 0.5.1 predates the staging-candidate release process · New

What changed in this PR

Updates the Anthropic connector submission guide to reflect current directory requirements and record the Internet Computer listing’s submission status.

Changes:

• Refreshes portal, submitter eligibility, review-status, and testing guidance.
• Adds a submission log covering review progress, the OAuth disruption, and escalation steps.
• Updates blocker notes and the submission-day checklist with recorded progress and release-process context.

File	Description
docs/​anthropic-directory-submission.md	Refreshes directory guidance and records submission history and checklist progress.

_{Review effort: Balanced}