disburse / docs

MCP connect

disburse ships a Model Context Protocol server, so agents can use search, enrich, and verify as native tools; the same engine as the REST API, exposed as tool calls.

The server lives at /mcp on the same host as the API and is bearer-authenticated with the same API keys.

Available tools

ToolWhat it does
search_peopleFind people by natural-language query or filters
search_companiesFind companies by natural-language query or filters
enrich_personEnrich a person by email: a profile merged across every source, with provenance and verification
enrich_companyFirmographics and signals for a company domain
verify_emailDomain-level email check (syntax, disposable, live MX). Not a mailbox check: it cannot confirm a specific address exists, and the response says so
verify_phoneFormat-level phone check (validity, line type, region, E.164). Does not dial
get_account_infoCredits remaining, monthly reset date, and whether leads can still be received. Free to call

All tools are read-only (declared via MCP annotations, so clients can call them without confirmation prompts) and the search tools declare output schemas and return structuredContent for typed, validated results.

Billing is per lead delivered: 1 credit for each NEW row that carries an email or phone. Contact-free rows, re-delivered leads, searching, filtering and verification are free, and each billed response reports the charge in its Summary.billing section.

Building lists

For "give me N …" requests, pass count (1-500) in ONE call instead of paging: the server paginates, deduplicates and quality-filters internally. Every row carries a match_tier (strict / filtered / ranked) and the response Summary reports composition, what was excluded (with reasons), and a mandatory stopped_reason — so your agent can say "46 verified matches, padded to 100 with labeled close matches" instead of guessing.

json
{ "query": "founders in Australia", "count": 200, "quality_bar": "balanced" }

quality_bar: strict (high-confidence only, may honestly under-fill), balanced (default; strict first, then labeled backfill), broad (ranked). When answering "how many …", use StrongMatches — Total counts the structured filters alone; keywords rank, they never narrow.

Just want the click-by-click setup for Claude? See Connect Claude.

Connect with an API key

Point any MCP client at the Streamable HTTP endpoint and pass your key as a bearer token. For Claude Desktop / Code, add it to your MCP config:

json
{
  "mcpServers": {
    "disburse": {
      "url": "https://api.disburse.dev/mcp",
      "headers": { "Authorization": "Bearer sk_live_your_key" }
    }
  }
}

One-click connect (OAuth)

When the server is deployed with OAuth enabled, clients like Claude can connect with a single "Connect" click instead of a pasted key: you sign in, approve the scopes on the consent screen, and the client is issued a token that maps to your organization. No key handling on the client side.

Both paths authenticate against the same accounts: an API key and an OAuth session resolve to the same org and the same rate limits.