Is there an MCP server for People Search here?

This site documents HTTP APIs. You can wrap POST /api/v1/people/email/find in your own MCP tool — we do not ship a separate MCP people-search server as of this page.

Where do I try a live call?

Use the try panel on /people-search/ with your jv_live_ key, or copy examples from /docs/people-search/.

How do Jev and Treg relate?

Published Treg workflows often use Jev for ICP filtering then Treg tools for enrichment. On this host both decide and email-find share prepaid credits.

Use Cases / ai-agent-people-search

People Search API for AI Agents

Agents that research companies need a reliable work-email find step after ICP filtering. Wiring many enrichment vendors directly is heavy; string-only LLM guesses are unreliable for deliverability.

Try a related template free on this host — 5 anonymous real-API runs with no signup — then ship the same schema with a prepaid jv_live_ key. See is Jev free? and playground.

Try People Search API Get API key API docs

Why Jev

Use Jev decide for typed ICP keep/drop, then call this host’s People Search API for Treg-routed email find/verify under the same prepaid jv_live_ balance. Your orchestrator stays in control — we do not claim native MCP tools unless you wire them yourself.

How to define the decision

1) Decide: pass company/person context; Choice keep/drop (or Score fit). 2) For kept rows, POST /api/v1/people/email/find with full_name+domain and/or linkedin_url; set verify true when you need route-level verification. 3) Branch on HTTP status and usage.remaining_tokens — never log the API key.

When to use Jev

Agent pipelines that already call /api/v1/decide for ICP or routing
Lead enrichment after company/person shortlists
Prepaid metering when you do not want a separate raw Treg token in the client

When not to use Jev

Stalking, harassment, doxxing, or any use without a lawful basis
Expecting a guarantee of email existence or deliverability on every row
Assuming official Treg partnership or identical catalog pricing on this host

Failure modes and human fallback

Upstream or network errors: retry with backoff; do not invent a decision.
Low confidence: route to a human queue or safer default — never auto-act on money/destructive tools.
Schema drift: keep a golden fixture set in CI so label changes fail the build before production.
Personal data — require lawful grounds; see Terms and Privacy.
This host is independent — not TypeSafe or Treg official.
No claim of MCP-native people-search tools on this site unless you implement the client yourself.
Successful calls debit prepaid credits; see usage in the API response.

API example

Same prepaid jv_live_ balance as tools. Output tokens are free on this host's metering model.

curl

curl https://jevtypesafe.org/api/v1/decide \
  -H "Authorization: Bearer jv_live_YOUR_KEY_HERE" \
  -H "Content-Type: application/json" \
  -d '{"state":"Customer: I've been waiting five days for my refund.","questions":{"action":{"type":"choice","instructions":"Decide the next step","criteria":{"allow":"safe","review":"unsure","block":"unsafe"}}}}'

FAQ

Is there an MCP server for People Search here?: This site documents HTTP APIs. You can wrap POST /api/v1/people/email/find in your own MCP tool — we do not ship a separate MCP people-search server as of this page.
Where do I try a live call?: Use the try panel on /people-search/ with your jv_live_ key, or copy examples from /docs/people-search/.
How do Jev and Treg relate?: Published Treg workflows often use Jev for ICP filtering then Treg tools for enrichment. On this host both decide and email-find share prepaid credits.

Related use cases

Ready to build?

Free anonymous tool runs, then prepaid packs and a jv_live_ key — independent host, not affiliated with TypeSafe AI.

See pricing Run a demo