Recipe · MCP + Claude

An agent that qualifies accounts by hiring pulse

Your agent answers “which of these accounts should we work this week?” with observed hiring data: found, gated and ranked in one conversation. Sign up, copy the API key on screen, and connect over MCP: the free tier needs no card.

Step 1: connect the server

Reqbeat Hiring Signals is a remote MCP server over streamable HTTP. Paste the config into your client: Claude Desktop, Claude Code, or any MCP-capable agent stack. Send your API key in the X-API-Key header. Sign up and the key is on screen, no card.

{ "url": "https://mcp.reqbeat.com/mcp",
  "headers": {
    "X-API-Key": "YOUR_REQBEAT_API_KEY" } }

claude mcp add --transport http reqbeat \
  https://mcp.reqbeat.com/mcp \
  --header "X-API-Key: $REQBEAT_API_KEY"

Step 2: give it the qualification loop

The system prompt is three rules, mapped to three tools:

find_company: resolve a domain or name to the company_id every other tool takes. Never billed.
is_hiring: the cheap gate before a richer call. A company with coverage_status: "no_ats_signal" is unknown, not quiet. Do not score it as a negative.
hiring_pulse: new reqs in 30 days, velocity vs the 30 before, direction, surge flag. Rank on this.

"Qualify these 40 domains for our
 backend-tooling ICP."

→ find_company({domain: "stripe.com"})
→ is_hiring({company_id: 1234})
  // {is_hiring: true, open_req_count: 7,
  //  coverage_status: "ats_direct_hit"}
→ hiring_pulse({company_id: 1234})
  // {new_roles_30d: 60, velocity: 0.68,
  //  direction: "down", is_surge: false}

// everything before outreach,
// one bounded round-trip:
pre_action_brief({company_id: 1234})
// pulse + top open reqs (deduped across
// boards) + first-hire-by-function +
// reposted (hard-to-fill) reqs

Step 3: close the loop

When a qualified account converts (a reply, a meeting, a closed deal), the agent reports it back with write_outcome. Your outcome data accrues against the signals that produced it, visible only to your account.

Notes on cost and correctness

who_is_hiring_for bills per company returned ($0.10 each). An empty result costs nothing. find_company, is_hiring gates and list_watches are never billed.
Errors are explicit. An unresolvable geo is an error that names the rule, never a partial page. Let the agent read them.
REST and MCP calls on one key share one rate budget, so a hybrid stack meters predictably.

Your agent can call these tools this afternoon. The key is on screen at signup.

Start free, no card