MCP tool

register_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 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.

Read from com.reqbeat/hiring-signals v1.0.0 on July 30, 2026 at 12:01 UTC · Refreshed every 3 hours

Connect

Reqbeat Hiring Signals is a remote MCP server over streamable HTTP. Paste this into your client's server config, replacing the placeholder with your own key:

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

Endpoint https://mcp.reqbeat.com/mcp, authenticated with the X-API-Key request header.

Input schema

{
  "properties": {
    "url": {
      "title": "Url",
      "type": "string"
    },
    "secret": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Secret"
    },
    "plane_api_key": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "title": "Plane Api Key"
    }
  },
  "required": [
    "url"
  ],
  "title": "register_webhookArguments",
  "type": "object"
}

Calling it

No response is shown because this page never calls this tool. It either needs your own API key or changes state on the server, and publishing a doc page is not a reason to do either. The request above is real -- run it yourself.