hiring_pulse — Reqbeat Hiring Signals MCP Tool
hiring_pulse
(hiring pulse) is one of 14 tools on the
Reqbeat Hiring Signals
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call hiring_pulse from your client
- Claude Code Reqbeat Hiring Signals hiring_pulse run in your project directory
- Claude Desktop Reqbeat Hiring Signals hiring_pulse ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Reqbeat Hiring Signals hiring_pulse ~/.cursor/mcp.json
- VS Code Reqbeat Hiring Signals hiring_pulse .vscode/mcp.json
- Zed Reqbeat Hiring Signals hiring_pulse ~/.config/zed/settings.json
- Windsurf Reqbeat Hiring Signals hiring_pulse ~/.codeium/windsurf/mcp_config.json
- Cline Reqbeat Hiring Signals hiring_pulse ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Reqbeat Hiring Signals hiring_pulse ~/.gemini/settings.json
- Grok Reqbeat Hiring Signals hiring_pulse .mcp.json (in your project root)
- ChatGPT Reqbeat Hiring Signals hiring_pulse Settings → Connectors → Advanced → Developer mode
- Claude.ai Reqbeat Hiring Signals hiring_pulse Settings → Connectors → Add custom connector
- LangChain Reqbeat Hiring Signals hiring_pulse pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http hiring-signals https://mcp.reqbeat.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.