Reqbeat Hiring Signals
Find companies hiring for a role and geo, qualify them, and watch them for changes
Reviews
No review yet. Used Reqbeat Hiring Signals? Be the first to help others choose.What it does
Reqbeat Hiring Signals is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)Hosted endpoint
https://mcp.reqbeat.com/mcpstreamable-http
Required: X-API-Key (get it from the publisher)
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"reqbeat-hiring-signals": {
"url": "https://mcp.reqbeat.com/mcp",
"headers": {
"X-API-Key": "<your X-API-Key>"
}
}
}
}Replace the values in <angle brackets>.
Live check
Electra Index connected to the hosted endpoint 1d agoONLINE Reqbeat Hiring Signals answered an MCP connection on 16 Nov 2026 and introduced itself as hiring-signals 1.1.4 (MCP protocol 2025-06-18).
15 tools offered to AI assistants
is_hiring· WHEN an agent already holds a company and needs to qualify it -- the cheap gate before spending a richer call. LinkedIn-excluded (ATS tenants plus public job boards and aggregators) and freshness-floored. Takes the integer `company_id` fromget_open_reqs· The company's current active reqs, deduped across boards -- LinkedIn-excluded: ATS tenants plus public job boards and aggregators; each row's `boards` names its source. Freshness-floored. Each row's `first_seen` is our first observation ofhiring_pulse· One number set for one company: how many reqs it opened in the last 30 days, a `velocity` ratio of that against the 30 days before it, a `direction` of up / flat / down between the two, a surge flag, and `momentum` -- postings published perwho_is_hiring_for· WHEN an agent needs to FIND the companies worth working -- the sourcing step, before it knows which companies exist. Reverse who's-hiring-for {title, geo} search: companies with active reqs matching `q`/`geo`/`since`, deduped by company, kesearch_jobs· Flat, role-granular job search -- the individual open roles across companies matching `function` / `geo` (country) / `since`, one row per logical req (each with its own `company_id` + `req_key`), LinkedIn-excluded (ATS tenants plus public jget_role· One open role's detail, addressed by the `company_id` + `req_key` pair every `search_jobs` row already carries -- the follow-up call for a role you hold an identifier for, instead of re-pulling the whole company with `get_open_reqs`. Scopedfind_qualified_reqs· WHEN an agent already knows its ideal customer profile and wants the matching open roles as rows it can act on: several countries, an industry, a headcount band and title keywords in ONE call, instead of a search followed by a lookup per copre_action_brief· Everything an agent needs before acting on one company, in one bounded round-trip instead of five: the hiring pulse, its top open reqs deduped across boards, first-hire-by-function events, hardest-to-fill (reposted) reqs and ATS-vendor migrget_changes· The change feed, not a search: ledger events -- a req opened, re-observed, reposted or closed -- with `event_seq > since`, ascending, plus `next_cursor`. Replay with `next_cursor` instead of polling or re-searching; an empty page bills nothfind_company· WHEN you hold a company's website or name but not the `company_id` every company-scoped tool takes (`is_hiring`, `get_open_reqs`, `hiring_pulse`, `pre_action_brief`, `watch_company`). Pass exactly one of `domain` or `name`; both or neitherregister_webhook· 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 iswatch_company· 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. `event_types` names which events fire it, at least one of: `opened`
Show 3 more
list_watches· WHEN you need to see what you are subscribed to -- before adding a watch, or to find the `id` `cancel_watch` takes. Returns your live watches newest first, cancelled ones excluded: {} -> {"watches": [{"id": ..., "company_id": ..., "event_tycancel_watch· WHEN a watch should stop firing. Takes the `id` `watch_company` returned (or `list_watches` lists): {"watch_id": 42} -> {"id": 42, "canceled": true}. Idempotent -- cancelling a watch you already cancelled succeeds again. An id that is not owrite_outcome· WHEN a company you reached through a signal converts -- a reply, a meeting, a closed deal -- report it back. Takes the `company_id`, a short `outcome` label of your choosing (e.g. "meeting_booked"), the `observed_at` time it happened and, o
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://mcp.reqbeat.com/mcp | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Version | 1.1.4 | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Website | https://reqbeat.com/mcp/ | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Repository | https://github.com/reqbeat/mcp-server | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 1d ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 1d ago |
Change history
- VERSION09 Oct 20261.1.3 → 1.1.4
- VERSION06 Oct 20261.1.2 → 1.1.3
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is Reqbeat Hiring Signals still online?
Free alerts · no account▲ 0Do you run Reqbeat Hiring Signals? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about Reqbeat Hiring Signals
How do I connect Reqbeat Hiring Signals?
Use the hosted endpoint https://mcp.reqbeat.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
Does Reqbeat Hiring Signals need an API key or token?
Yes. The registry entry lists a required value: X-API-Key. Get it from the publisher.
What tools does Reqbeat Hiring Signals offer?
When Electra Index connected on 16 Nov 2026, it listed 15 tools: is_hiring, get_open_reqs, hiring_pulse, who_is_hiring_for, search_jobs, get_role, find_qualified_reqs, pre_action_brief and more. The full list is in "Live check" above.
Is Reqbeat Hiring Signals online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.