Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

JobsRadar

REMOTE · JOBSRADAR.AGENTTOOLWORKS.COM

Job search across Greenhouse, Lever, Ashby, SmartRecruiters, Personio and Pinpoint, deduplicated.

+3 this week 81 Trust /100

Last scanned (13 hours ago)

Scores higher than 86% of remote servers

Reachable. Last reached 23 Oct 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security71
Transport & Reachability100
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 518 tokens (~129/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 22 Oct 26 +1

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

  • 20 Oct 26 +1

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

  • 18 Oct 26 +1

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

  • 16 Oct 26 +1

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

  • 14 Oct 26 +1

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

  • 11 Oct 26 +1

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

  • 10 Oct 26 +1

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

  • 7 Oct 26 +1

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

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://jobsradar.agenttoolworks.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agenttoolworks.com CN=WE1,O=Google Trust Services,C=US 13 Oct 2026 11 Jan 2027 ECDSA 256 ECDSA-SHA256 82217d718bb7d4cb0e95276b93b8506c
SANs: agenttoolworks.com, jobsradar.agenttoolworks.com, *.jobsradar.agenttoolworks.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of jobsradar.agenttoolworks.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
agenttoolworks.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

Protected resource metadata

Retrieved No
Problem no_resource_metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jobsradar.agenttoolworks.com/mcp Verified 200
http (plaintext) http://jobsradar.agenttoolworks.com/mcp Inconclusive 405
MCP tools · 4 exposed · ~518 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_company_jobs ~171

Returns all public postings for one company. Give a tracked company name, or any board slug and we detect which applicant tracking system serves it (Greenhouse, Lever, Ashby, Workable, Personio, Pinpoint, SmartRecruiters). 'data_as_of' is when the board was fetched. A board past our page cap (SmartRecruiters, 1,000 postings) comes back with 'truncated' giving the full count. Costs 1 credit.

NameTypeReqDescription
companystringyesTracked company name, or a board slug like 'stripe'
providerstring–Skip detection when you already know the ATS. Workable refuses this hosted service (HTTP 429); its boards work through the JobsRadar Apify Actor
title_keywordsarray–Optional title filter

No output schema declared.

No examples provided.

get_usage ~30

Returns your current plan, remaining credit balance and call volume over the last 30 days. Free to call.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_supported_companies ~90

Returns the curated directory of companies whose public job boards are tracked, grouped by the applicant tracking system behind each one. Use it to pick names for search_jobs. A board slug is the company name lowercased with spaces removed; the few that differ are listed under 'slugs'. Light read: costs 0.2 credit.

NameTypeReqDescription
providerstring–Filter to one applicant tracking system

No output schema declared.

No examples provided.

search_jobs ~227

Searches open roles across many company job boards in a single call and returns one deduplicated, normalized list. Filter by title keywords, location, remote only, and posted-after date. Without a company list it searches the whole tracked directory. Boards are refreshed every 15 minutes; 'data_as_of' is when the oldest board in the answer was fetched. A board larger than we read in full is named in 'boards_truncated' with how many postings it has. Costs 1 credit.

NameTypeReqDescription
companiesarray–Restrict to these tracked companies; omit to search all of them
limitinteger–Max results, default 50
locationstring–Substring on the published location, e.g. 'London'
posted_afterstring–ISO date, e.g. '2026-07-01'. Undated postings are kept.
remote_onlyboolean–Keep only postings the board marks remote
title_keywordsarray–Match roles whose title contains any of these, e.g. ['data engineer','ml']

No output schema declared.

No examples provided.

Install

How do I install the JobsRadar MCP server?

JobsRadar is a hosted endpoint at https://jobsradar.agenttoolworks.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · jobsradar.agenttoolworks.com

# add to Claude Code
claude mcp add --transport http com-agenttoolworks-jobsradar 'https://jobsradar.agenttoolworks.com/mcp'
Common questions

What is the JobsRadar MCP server?

JobsRadar is an MCP server listed in the public MCP registry as com.agenttoolworks/jobsradar. Job search across Greenhouse, Lever, Ashby, SmartRecruiters, Personio and Pinpoint, deduplicated. This page covers its hosted endpoint (https://jobsradar.agenttoolworks.com/mcp).

Is the JobsRadar MCP server safe to use?

JobsRadar scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the JobsRadar MCP server expose?

JobsRadar exposes 4 tools: search_jobs, get_company_jobs, list_supported_companies, get_usage. Their descriptions and schemas cost roughly 518 tokens of context every time the server is loaded.

Does the JobsRadar MCP server require authentication?

Yes. JobsRadar asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the JobsRadar MCP server still maintained?

JobsRadar is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.