Wiza

Official MCP Paid, self-serve Data & Enrichment RESEARCHED Checked 2026-08-25

RESEARCHED Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0.

Vendor: wiza.co · entry id 01-wiza · source 01-data-enrichment.md line 619

What it does

Pulls verified work emails and mobile numbers for people found on LinkedIn or Sales Navigator and exports them to CSV or a CRM.

AI features, separated from automation with an AI label on it

One genuine AI surface, "AI Research" / AI Columns, which takes a natural-language question about a company or contact, scans the public web, and returns a structured answer plus a reasoning string as a filterable column. Everything else, the 850M-contact database, the Chrome extension, the SMTP deliverability check, is a database with a filter and a mail-server ping. Wiza does not disclose which model powers AI Research.

RevOps role

Top-of-funnel contact acquisition sitting between Sales Navigator and the CRM or sequencer, with an optional LLM research column for ICP qualification.

MCP server

Status bucket

Official MCP

Auth

OAuth 2.1 with PKCE for clients that support it, otherwise a static bearer token in the Authorization header using a Wiza API key. Streamable HTTP transport.

Parsed URLs

3 found in the mcp_url field

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-25 and has not been re-fetched since.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://mcp.wiza.co/mcp (docs: https://mcp.wiza.co/usage.html; announced at https://feedback.wiza.co/changelog/wiza-mcp)

Access gate

Gate bucket

Paid, self-serve

Can a solo operator reach it

Yes, by paying, no sales call

api_gate, verbatim from the file:

paid

API documentation

https://docs.wiza.co/

No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.

GitHub health

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

Jobs it can do

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total.

Sources

5 source URLs. Raw sources field, verbatim:

https://wiza.co/pricing, https://docs.wiza.co/, https://mcp.wiza.co/usage.html, https://feedback.wiza.co/changelog/wiza-mcp, https://wiza.co/ai-research

Notes, verbatim from the file

Added 2026-08-25, closing a named warm lead from this file's previous sweep notes. Self-serve tiers are Free $0 (20 valid emails, 5 phones), Starter $49/mo, Email $99/mo, Email + Phone $199/mo, with annual at $990/yr and $1,990/yr. UNRESOLVED CONTRADICTION worth flagging to readers: "API access" appears on the pricing page only under the custom-priced, 3+ seat, annual Team plan, which means a sales call, while the MCP changelog says the server "is available today for all Wiza users" and needs only "a Wiza API key". Neither docs page states a plan requirement. Settling this needs an account, so api_gate is recorded as paid on the pricing page's authority. Documented MCP tools: enrich_contact, enrich_company, get_credits, search_companies, search_prospects.

Provenance

Entry id

01-wiza

Source file

01-data-enrichment.md

Source line

619

Tier

RESEARCHED

last_checked

2026-08-25

Data baked

2026-08-25

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.