Turrior

Turrior Hunter

turrior/hunter
PLANNEDFIRST-PARTY

Most roles are not filled by the people who happened to see the ad. Hunter builds a shortlist of people who genuinely match the role, then invites them to apply — and every invitation is one a person can decline once and never receive again.

  • 8 TOOLS
  • SOURCING
  • PLANNED
  • FIRST-PARTY

What this server actually does

  • Match, then invite

    Hunter reads the role, searches the talent base for people whose experience actually lines up, and ranks them before anyone is contacted.

  • You approve the list

    Nothing is sent until a human sees the shortlist. Preview shows exactly who would be contacted and why they matched.

  • One invitation, not a campaign

    Each person gets a single invitation to apply, with the role, the reason they were matched, and a one-click way to opt out for good.

  • Replies land in the pipeline

    Someone who applies arrives in Turrior as a normal candidate, already attributed to the sourcing that found them.

Connect the endpoint

Endpoint: not yet available
Status:   in development

Endpoint will be published when Hunter enters beta.

What your agent can call

READREAD = safe, retrievesWRITEWRITE = performs an action5 read · 3 write · full CRUD

Your client loads only the toolset it needs — group by domain keeps context lean.

    • READ
      hunter_search_talentsSearch the talent base against a role and return ranked matches with reasons.
    • READ
      hunter_list_campaignsSourcing runs to date, by role.

    • WRITE
      hunter_build_shortlistAssemble a named shortlist from search results for review.
    • READ
      hunter_preview_invitationsShow exactly who would be contacted, with the message. No side effects.

    • WRITE
      hunter_send_invitationsSend the invitations. Requires explicit human confirmation.
    • READ
      hunter_invitation_statusDelivery, opens, applications and opt-outs per campaign.
    • READ
      hunter_suppression_listPeople who opted out and must never be contacted again.
    • WRITE
      hunter_stop_campaignStop a run that is still sending.

From prompt to action

  • “Who in the base fits the Berlin backend role?”
    hunter_search_talents
  • “Show me the top 20 before we contact anyone.”
    hunter_build_shortlisthunter_preview_invitations
  • “Send them the invitation.”
    hunter_send_invitations
  • “How many applied from that batch?”
    hunter_invitation_status
  • “Stop the campaign.”
    hunter_stop_campaign

What to keep in mind

Outbound to people who did not apply
Hunter is the only Turrior server that writes to people who never contacted the company. Legal basis (GDPR / CCPA / LGPD) and retention are being settled before general availability — this page will state them concretely once fixed.
Human confirmation before send
Every invitation batch must be previewed and confirmed by a human. `hunter_preview_invitations` is a required stop between shortlist and send.
Every invitation is refusable, once
Each person receives at most one invitation per company. A refusal is permanent — `hunter_suppression_list` blocks any later contact.
Not a mass-email tool
Hunter sends a single invitation per person per role, not a campaign. It will not be exposed as a broadcast primitive.

Security & permissions

  • Human confirmation is enforced

    Invitations cannot be sent by the model alone. The server exposes preview and send as separate tools so the human approval step is unavoidable.

  • Opt-outs are permanent

    The suppression list is queryable and enforced server-side — a person who declines once will not receive a second invitation, regardless of which agent runs the campaign.

Related servers

Browse all
Turrior Hunter — AI Candidate Sourcing MCP Server · Turrior