# Reqbeat Hiring Signals (remote · mcp.reqbeat.com)

Find companies hiring for a role and geo, qualify them, and watch them for changes.

- Trust score: 52/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.reqbeat.com`: 52/100 (this document), [markdown](https://verifymcp.io/servers/com-reqbeat-hiring-signals/mcp.md), [page](https://verifymcp.io/servers/com-reqbeat-hiring-signals/mcp)

## Channel facts

- Endpoint: `https://mcp.reqbeat.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 45/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1615 tokens (~161/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-reqbeat-hiring-signals https://mcp.reqbeat.com/mcp
```

### Codex

```toml
[mcp_servers.com-reqbeat-hiring-signals]
url = "https://mcp.reqbeat.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-reqbeat-hiring-signals": {
      "type": "remote",
      "url": "https://mcp.reqbeat.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-reqbeat-hiring-signals --url https://mcp.reqbeat.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-reqbeat-hiring-signals:
    url: "https://mcp.reqbeat.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-reqbeat-hiring-signals": {
      "type": "http",
      "url": "https://mcp.reqbeat.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 51, +33)

- [security improvement] Transport: fail → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 18, −31)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 48, −1)

- [security] Tool “who_is_hiring_for” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.28.1 → 1.0.0

### 2026-07-28 (score 49)

First indexed and scored.

## MCP tools (10)

### `is_hiring` (~196 tokens)

WHEN an agent already holds a company and needs to qualify it -- the cheap gate before spending a richer call. ATS/board-only and freshness-floored. Takes the integer `company_id` from an earlier result, not a company name or domain. company_id=1234 -> is_hiring true, open_req_count 7, coverage_status "ats_direct_hit". company_id=5678 -> is_hiring false with coverage_status "no_ats_signal" -- that company has no ATS coverage yet, which is not evidence it is quiet, so do not score it as a negative. No key yet? Pass `plane_api_key` as an empty string and the call answers with a signup link instead of an auth error. To find companies in the first place, use `who_is_hiring_for`.

Input parameters:

- `company_id` (integer, required)
- `idempotency_key`
- `plane_api_key`

### `get_open_reqs` (~129 tokens)

The company's current active reqs, deduped across boards --
    ATS/board-only, freshness-floored. `function` must be a function id
    (as seen in prior results); a plain role name like 'engineering' is
    rejected with an explicit error rather than an empty result. `limit`
    is bounded: an oversized page is rejected rather than truncated.

Input parameters:

- `company_id` (integer, required)
- `country`
- `function`
- `idempotency_key`
- `limit` (integer)
- `plane_api_key`

### `hiring_pulse` (~89 tokens)

A company's hiring velocity/direction/momentum in one call --
    dual-metered via `max_age` (seconds). Cold returns `{job_id, status:
    "crawling"}` instead of a synchronous body, same as the REST route.

Input parameters:

- `company_id` (integer, required)
- `idempotency_key`
- `max_age`
- `plane_api_key`

### `who_is_hiring_for` (~349 tokens)

WHEN an agent needs to FIND the companies worth working -- the sourcing step, before it knows which companies exist. Reverse who's-hiring-for {role, geo} search: companies with active reqs matching `role`/`geo`/`since`, deduped by company, keyset-paginated via `cursor`. `role` is free text matched against the posting title, not an id. `geo` is resolved to a stored country before matching; an unresolvable one is an explicit error, never a quietly partial page. `limit` is bounded -- page through the full set with `cursor` instead of raising it. Billed per company returned (~0.10 USD each) -- an empty result bills nothing. role="backend engineer", geo="USA" -> the companies with matching active reqs, each with its pulse and its matched reqs. geo="Atlantis" -> an explicit unresolvable-country error rather than an empty page. No key yet? On the hosted HTTP endpoint the first calls are free: pass `plane_api_key` as an empty string and the search runs on a shared demo credential -- a smaller page, billed to nobody -- until a per-IP limit is reached, after which the answer becomes a signup link whose minted key finishes this exact search. On any other transport a blank key answers with that signup link straight away. Already holding a company_id and only need a yes/no? Use `is_hiring`.

Input parameters:

- `cursor`
- `geo`
- `idempotency_key`
- `limit` (integer)
- `plane_api_key`
- `role`
- `since`

### `search_jobs` (~230 tokens)

Flat, role-granular job search -- the individual open roles across
    companies matching `role` (function) / `geo` (country) / `since`, one
    row per logical req (each with its own `company_id` + `req_key`),
    ATS-only + freshness-floored. Keyset-paginated via the opaque `cursor`
    (a prior call's `next_cursor`). Use `who_is_hiring_for` for the
    company-granular reverse view. `role` must be a function id (as seen
    in prior results); a plain role name like 'engineering' is rejected
    with an explicit error rather than an empty result. `limit` is
    bounded: an oversized page is rejected rather than truncated, so page
    through the full set with `cursor` instead of raising `limit`.

Input parameters:

- `cursor`
- `geo`
- `idempotency_key`
- `limit` (integer)
- `plane_api_key`
- `role`
- `since`

### `pre_action_brief` (~87 tokens)

The motion atoms + history primitives pre-joined into one
    bounded, compact call -- dual-metered via `max_age`. Cold returns
    `{job_id, status: "crawling"}`, same as the REST route.

Input parameters:

- `company_id` (integer, required)
- `idempotency_key`
- `max_age`
- `plane_api_key`

### `get_changes` (~145 tokens)

The `since=cursor` diff feed -- ledger events with `event_seq >
    since`, plus a `next_cursor`. Meters one `change` unit per event
    returned, independent of poll count. A free-tier caller is
    freshness-floored, the same as every other free-tier read. `limit` is
    bounded: an oversized page is rejected rather than truncated, so
    replay with `next_cursor` instead of raising `limit`.

Input parameters:

- `company_id`
- `event_type`
- `idempotency_key`
- `limit` (integer)
- `plane_api_key`
- `since` (integer, required)

### `register_webhook` (~184 tokens)

Register the delivery target a watch fires to, and get back the
    `webhook_endpoint_id` `watch_company` needs -- call this first if you
    do not already hold one. Idempotent: registering the same `url` twice
    returns the same id, so retrying is safe and never leaves you with two
    endpoints. `secret` is optional; supply one to verify the
    `X-Plane-Signature` on delivered payloads, omit it and one is
    generated (it is never returned). Registration itself is free -- the
    `watch_company` call that follows is what bills.

    Plane session only: `webhook_endpoints` is plane-owned and this tool reads
    no corpus table.

Input parameters:

- `plane_api_key`
- `secret`
- `url` (string, required)

### `watch_company` (~87 tokens)

Subscribe to a company's hiring events on a registered webhook --
    `webhook_endpoint_id` must belong to the same customer as the
    authenticated key. Meters one `watch` unit.

Input parameters:

- `company_id` (integer, required)
- `event_types` (array, required)
- `idempotency_key`
- `plane_api_key`
- `webhook_endpoint_id` (integer, required)

### `write_outcome` (~119 tokens)

Write back a conversion outcome for `company_id` -- the
    label-flywheel substrate. Appends to `outcome_labels` scoped to the
    caller's own customer.

    Plane session only: `outcome_labels` is plane-owned (Phase 1 dropped its
    one foreign key into the corpus) and this tool reads no corpus table.

Input parameters:

- `company_id` (integer, required)
- `observed_at` (string, required)
- `outcome` (string, required)
- `plane_api_key`
- `req_key`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-reqbeat-hiring-signals/mcp#diagnostics

## Score history

- 2026-08-03: 52
- 2026-08-02: 52
- 2026-08-01: 51
- 2026-07-31: 18
- 2026-07-30: 49
- 2026-07-29: 48
- 2026-07-28: 49

## Links

- Remote endpoint: https://mcp.reqbeat.com/mcp
- Authorisation metadata: https://mcp.reqbeat.com/.well-known/oauth-protected-resource/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-reqbeat-hiring-signals/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-reqbeat-hiring-signals/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-reqbeat-hiring-signals/mcp
