Summary
A vendor shipping its own integration instructions as a tool is a direct answer to the model writing SDK code from a version that no longer exists.
SDK integration is where a model's training cutoff shows up as a bug: a method that was renamed, a flow that changed, an initialisation step that was added. Having the maintainer supply the current instructions at call time is the cheapest possible fix, and it costs the vendor a single tool. Scope is exactly one thing today — the README says more Divvi functionality is planned — so this is useful during an integration and has nothing to offer afterwards.
What it is
A single-tool integration assistant from the Divvi team: it supplies the instructions for wiring the @divvi/referral-sdk into a JavaScript or TypeScript blockchain application.
What you get
- integrate_divvi_referral_sdk returns the integration steps for the referral SDK, covering the transaction-flow changes the integration requires.
Requirements
Nothing to supply.
Setup effort
One command — npx -y @divvi/mcp-server