@pipeworx/trykitt

Connect: https://pipeworx.io/mcp — every tool in the catalog, including @pipeworx/trykitt’s. Install: one-click buttons

Connect to just the @pipeworx/trykitt pack

https://gateway.pipeworx.io/trykitt/mcp — only @pipeworx/trykitt’s own tools, nothing else in the catalog.

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 1

Find a verified work email by full name + company domain, via TryKitt.ai. Part of the enrich-waterfall finder rotation (fleet #2860).

Tools

  • trykitt_find_email(full_name, domain, linkedin_url?, _apiKey) — email, confidence (0-1), and sources, requested in realtime mode so the HTTP response carries the finished result rather than a job id to poll.

Auth

BYO only. Pass your TryKitt API key as _apiKey (header x-api-key — not Authorization, which several third-party write-ups wrongly assume). Get one at https://trykitt.ai. No platform key (D4).

Data sources

  • https://api.trykitt.ai/job/find_email — email finder (realtime mode).

Verification notes (fleet #2860, 2026-10-08, no vendor key held)

  • Header name confirmed by edge probe, including the “missing vs wrong” distinction: no auth header -> HTTP 401 {"message":"Auth credential not set in request","response_code":401}; x-api-key: invalidkey123 -> HTTP 401 {"message":"Invalid API Key","response_code":401}. Two different messages for two different failures confirms the header is actually being read, not just any 401 default.
  • Response shape is from TryKitt’s public Postman collection and third-party MCP wrapper READMEs (not TryKitt’s own prose docs, which sit behind the same auth wall as the API) — we hold no key, so no successful call was made. Documented shape: { job_id, status, result: { email, confidence, sources } }. This pack treats any status other than "completed" as a loud error rather than a silent no-match, since TryKitt’s job model can also run async — if a live key ever gets back a "pending" status despite realtime: true, that needs a poll step added, and the current code will say so explicitly instead of reporting found: false.
  • Not verified (no key held): whether realtime: true reliably forces a synchronous result on every plan tier; the full set of status values.

Tools

  • trykitt_find_email — Find a verified work email by full name + company domain (or website URL — TryKitt extracts the domain), via TryKitt.ai. Example: trykitt_find_email({ full_name: “Patrick Collison”, domain: “stripe.co

Tools

  • trykitt_find_email — Find a verified work email by full name + company domain (or website URL — TryKitt extracts the domain), via TryKitt.ai. Example: trykitt_find_email({ full_name: Patrick Collison , domain: stripe.com

Regenerated from source · build October 9, 2026