MCP Setup · iGaming Finder

What is MCP?

MCP (Model Context Protocol) lets AI assistants like Claude Desktop, Cursor, and Codex call iGaming Finder tools directly. Ask questions in natural language and get operator intelligence data without writing code.

Hosted setup

Use one Streamable HTTP endpoint in every client:

text

https://mcp.igamingfinder.com/mcp

No Node install, copied API key, environment variable, or JSON file is required. The client opens iGaming Finder OAuth in your browser. Sign in (or create a free account), review igf:read / igf:spend, choose a session credit budget, and approve.

Claude Desktop and Claude.ai

Open Settings → Connectors, add a custom connector, and paste the hosted URL. Claude completes Dynamic Client Registration and S256 PKCE automatically.

Claude Code

bash

claude mcp add --transport http --scope user igaming-finder https://mcp.igamingfinder.com/mcp

Open Claude Code and complete the browser OAuth prompt when the connector first runs.

Cursor

Open Cursor's MCP settings, add a remote/HTTP server named igaming-finder, and use the hosted URL. Complete OAuth in the browser; do not add an Authorization header.

Codex

bash

codex mcp add igaming-finder --url https://mcp.igamingfinder.com/mcp
codex mcp login igaming-finder

Session safety

The connector receives a revocable opaque token, never your stable account API key.
Paid tools require the igf:spend scope and cannot exceed the immutable budget you approve.
account_show reports both account credits and the connector's budget/used/reserved/available counters.
A client disconnect that sends OAuth revocation revokes only this connector session without rotating your account API key. You can also inspect budgets, usage, client identity, and revoke any session from Account → Connectors. Signing out of the website alone does not revoke connector tokens.
Free previews are available before a paid call. Paid responses continue to report actual credits_charged.

$ help --topic=info

The npm/stdio server remains an advanced local fallback. It uses the CLI's owner-only credential store and the same 14-tool catalog; prefer hosted OAuth unless you specifically need self-hosted local execution.

Available Tools

Once connected through OAuth, the AI assistant gets the full toolset (one tool per API operation; paid tools state their CreditCost key and every billed response includes credits_charged):

Tool	What it does	Billing
`signals_list`	Cursor-only licensed-market-entry feed; returns stable `signal_ref`, Company/License refs, regulatory facts, evidence, quality, coverage, billing, and `next_cursor`	per Signal row
`companies_search_preview`	Result count + cost estimate before paying	free
`companies_search`	Paid discovery search over companies; rows carry `company_ref`	per result
`companies_resolve`	Authoritative profile by `company_ref` / domain / name / license; optional exact-Domain or all-eligible-Domain firmographics	per profile + delivered Domain result
`companies_people`	Decision-maker contacts for a company	per contact
`licenses_search_preview`	License search preview	free
`licenses_search`	Paid license search; pivots to issuing company	per result
`licenses_resolve`	Authoritative license profile	per profile
`domains_resolve`	Trust verdict plus optional freshness-gated Operator Launch Profile; keeps Licensee, website operator claims, and technical relationships separate	per delivered composition
`domains_search`	The set of domains by verdict/geo/time — bulk blocklist and change feed	per row
`account_show`	Plan + account credits + hosted session budget remaining	free
`exports_create`	Create a CSV/JSON export (async)	by result count
`exports_show`	Poll an export started by `exports_create`	free
`exports_download`	Retrieve a completed export as an embedded resource (local file in stdio fallback)	free

For signals_list, pass the previous next_cursor as after with the same market and occurrence-date filters. Each MCP invocation receives a fresh idempotency key automatically. Omitted Signal compositions are not_requested; requested Signal firmographics/contacts remain not_available in V1 and add no optional charge.

For companies_resolve, request include: ["firmographics"] explicitly. Pass a related domain_ref to select one Domain, or omit it to enrich every eligible Domain. Omission is intentional fan-out: each available fresh, cached, or stale Domain result uses the configured per-result rate below, so set max_credits to a budget you approve for the profile plus all candidate Domains before acquisition. allow_stale_on_error defaults to true; use false for strict unavailability after a transient refresh failure.

Cost: 12 credits / delivered Domain result

Example prompts:

"Poll the Anjouan licensed-market-entry Signal feed and return each signal_ref, license_ref, and authorized domain"
"Find MGA-licensed crypto casinos — preview the cost first"
"Resolve stake.com, then use its first domain_ref to request firmographics for exactly that Domain without exceeding the max_credits budget I provide"
"Resolve this Company with firmographics for every eligible Domain; keep stale-on-error enabled and refuse the call if the preflight total exceeds the max_credits budget I provide"
"Resolve stake.com and pull decision-maker contacts"
"Check the trust verdict for roobet.com — which regulators license it, which block it?"
"Resolve ncc.bet with include operator_launch_profile, max_age_days 7, and max_credits 6; report launch state, legal claims, website emails, evidence refs, and the 1+5 billing breakdown without treating technical relationships as ownership"

Example Conversations

Competitive analysis:

"Show new Anjouan licensees since 2026-01-01, then continue from next_cursor"
"Which operators licensed by MGA feature both Evolution and Pragmatic Play but don't accept crypto?"

Market research:

"List all domains that were blocklisted in the last 7 days"

Due diligence:

"Get the full profile for betway.com, including all licenses and payment methods"

$ help --topic=tip

domains_resolve validates the exact include catalog before calling the API. An available Operator Launch Profile costs 5 credits in addition to the 1-credit verdict; an unavailable profile returns an explicit reason and adds no optional charge. Use a new MCP invocation for each new request—the client sends a fresh idempotency key automatically.

Hosted MCP tools draw from account credits while also respecting the smaller connector-session budget you approved. Previews and status lookups are free; searches, resolves, contacts, Signals, and exports are billed at the standard rates — see the Credit Costs table in the API reference.