That instruction is worth taking at face value: build against discovery, not against a snapshot, or an integration will break quietly when a tool is renamed. The rest of the posture is careful in the same direction — read-only consent by default, per-tool annotations so a client can enforce that, and a documented recommendation to rehearse in a test org. For a product that chases customers for money, doing that rehearsal is not optional.
Billabex's endpoint for their receivables product. The base URL is per-account and not printed in the docs; their developer guide explicitly tells integrators not to copy a tool catalogue but to discover the tools at runtime.
35 tools across the collection workflow, each carrying annotations such as readOnlyHint so a client can tell reads from writes before calling. Because the docs ask integrators to discover rather than hard-code, treat the count as of its capture date.
OAuth 2.1 with PKCE and standards-based discovery. Consent starts at mcp:read, and the documentation recommends pointing a test organisation with no sensitive data at it first.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen