Skills/npm/unified-ats-jobs-mcp

unified-ats-jobs-mcp@1.0.13

VERIFIED· startup only

Publisher claims: "Unified 5-in-1 B2B ATS job scraper & signal MCP: Greenhouse, Workday, Ashby, Lever, SmartRecruiters." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher revclamp · publishing for 19 daysInstalls 0Last detonated 11 h ago
$claude mcp add unified-ats-jobs-mcp -- npx -y @revclamp/unified-ats-jobs-mcp
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
APIFY_TOKENConfiguration, not credentials: ACTOR_MAX_TOTAL_CHARGE_USD, ACTOR_MEMORY_MBYTES, ACTOR_RUN_ID, ACTOR_START_FEE_USD, APIFY_ACTOR_RUN_ID, APIFY_INPUT_PATH, APIFY_MEMORY_MBYTES
Where it talks to
revclamp.com (its own)Also ashbyhq.com, greenhouse.io, apify.com, lever.co, smartrecruiters.com, githubusercontent.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names ashbyhq.com, greenhouse.io, apify.com, lever.co, smartrecruiters.com, githubusercontent.com as well as its own vendor. The guard injects APIFY_TOKEN only into requests to revclamp.com (and its subdomains) and refuses the rest.

$vet-skills run --secrets APIFY_TOKEN=revclamp.com -- npx -y @revclamp/unified-ats-jobs-mcp

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 and scored it 91/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
20sclaimedstartup only: exited (0) before answering · "effectiveMarginMultiplier": 0, "marginPositive": false } }
20sprocessscript backend runs setup only
20sprocessno install scripts to re-run

Static findings

MEDIUM
File type combined with upload actionsrc/apify_actor.mjs:307 · File type combined with upload action — agent may exfiltrate local data filesfor (const candidateName of [`${inputKey}.json`, inputKey]) {Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

No other findings across 11,573 lines in 21 files.

Cost to the agent

Instructions loaded
≈99 tok
1 file · 21 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for @revclamp/unified-ats-jobs-mcp@1.0.13 as of 10 h ago. This is the package itself, not its dependencies.