feat: surface server icon and website URL in MCP serverInfo (SEP-973)

[aliasunder]

Summary

Adds icons and websiteUrl to the Implementation metadata returned during initialize (MCP spec 2025-11-25, SEP-973). Clients that support server icons render the project mark beside the connection instead of a generic or domain-derived favicon.

Why

MCP clients that don't implement SEP-973 fall back to deriving a connection icon from the server URL's domain — for an API Gateway deployment that resolves to the AWS favicon rather than anything project-related. Publishing the icon in serverInfo is the spec-correct, domain-independent fix: compliant clients pick it up immediately, and clients that currently ignore the field (tracked upstream in anthropics/claude-ai-mcp#152) inherit it the moment they add support, with no further server change.

Changes

• src/vault-mcp/mcp-router.ts — SERVER_ICONS (the existing assets/icon-400.png, referenced via its raw GitHub URL so it stays valid regardless of deployment domain) and SERVER_WEBSITE_URL constants, passed to the McpServer constructor alongside the existing name/title/version/description.
• src/vault-mcp/__tests__/mcp-router.test.ts — SERVER_INFO expectation extended to the new fields (exact-match assertion; fails if the metadata is removed).

Verification

• 520/520 tests pass; tsc and eslint clean.
• Mutation-audited: reverting the source change fails exactly the serverInfo metadata test.
• Field support verified against the pinned @modelcontextprotocol/sdk 1.29.0 ImplementationSchema (icons, websiteUrl both present).

Generated with Claude Code

---

Generated by Claude Code

Summary by CodeRabbit

• Chores
  • Added icons array and website URL metadata to MCP server configuration in both test and production implementations.

[coderabbitai]

Warning

Review limit reached

@aliasunder, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 55 minutes and 13 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 1913fc3c-3d16-41c5-81cb-ae50162468a4

📥 Commits

Reviewing files that changed from the base of the PR and between f8ecaef and 46a0731.

📒 Files selected for processing (2)

• src/vault-mcp/__tests__/mcp-router.test.ts
• src/vault-mcp/mcp-router.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/vault-bootstrap-setup-5z5j02

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}