Docs drift: quickstart/tool counts/API key prefix inconsistent with live surface

[supertrained]

Summary

Several public surfaces disagree with the live product state after the email OTP rollout.

Repro / evidence

1) Quickstart says 21 MCP tools, live server exposes 16

Quickstart copy (https://rhumb.dev/quickstart) says:

"21 tools available: find_services, get_score, get_alternatives, get_failure_modes, execute_capability, and more."

Live MCP server:

npx -y @modelcontextprotocol/inspector --cli npx -y rhumb-mcp@latest --method tools/list

Actual result: 16 tools.

2) Quickstart shows rhumb_live_..., live signup issued rhumb_...

Dogfood signup flow:

1. POST /v1/auth/email/request-code
2. receive OTP email successfully
3. POST /v1/auth/email/verify-code

Live response issued an API key with prefix:

rhumb_...

But Quickstart still shows examples like:

-H "X-Rhumb-Key: rhumb_live_..."

3) Public service-count copy disagrees across pages

• Homepage hero says 1000 scored services
• Homepage lower copy says 1,038 scored services
• llms.txt also says 1,038 scored services

4) MCP install/config examples are inconsistent

• README uses npx -y rhumb-mcp@latest
• Quickstart MCP config currently shows command npx with args ["rhumb-mcp@latest"]

That may be okay in some contexts, but it no longer matches the safer README pattern and adds first-run ambiguity.

Expected

Public docs and onboarding copy should match the live surface:

• accurate MCP tool count
• accurate API key prefix
• consistent service-count claims
• one canonical MCP launch/config example

Impact

None of these are backend outages, but together they create avoidable trust friction exactly where a new user is trying to decide whether Rhumb is precise and reliable.

[supertrained]

Fresh 2026-04-13 weekly dogfood repro.

Still reproducing on the public surface:

• https://rhumb.dev/quickstart still says 21 tools available.
• https://rhumb.dev/blog/getting-started-mcp still says One command. 21 tools. 1,038 scored services. 16 callable providers today.
• Quickstart examples still show X-Rhumb-Key: rhumb_live_... while a fresh email-OTP signup today issued api_key_prefix: rhumb_fd71fe (rhumb_...).
• Quickstart / MCP examples still use npx rhumb-mcp@latest or config without -y, while the npm README uses npx -y rhumb-mcp@latest.
• Homepage copy still disagrees with itself: hero says 1000 scored services, lower copy says 1,038 scored services.

So the docs drift is still live and still visible in the first-run path.