Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Nothing to run from here
Hiring Change Intelligence is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
6
downloads a day
local
or remote
227
downloads in 30d
What it does
Track public job boards: free snapshot, paid hiring-growth intel via x402 USDC.
Quickstart
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with npx -y hiring-change-intelligence and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Publishernot claimed
CPAll 4 servers
contentforge-press4 servers
4 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This package runs as a local HTTP server (Streamable HTTP), not over stdio, so a client cannot start it as a process. Start it in a terminal with npx -y hiring-change-intelligence and keep it running, then add the address it listens on to your client as a remote server; that address is not recorded here, so there is no entry to copy.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
FREE. Current job openings / who is hiring at one company right now, with teams (departments), locations, remote and employment type. Use for "what jobs is X hiring for", open roles, talent demand, headcount signals. Sources Greenhouse/Lever/Ashby. Target: gh:<h>, lever:<h>, ashby:<h> or bare company handle.
No parameter schema on file.
PAID ($0.05 USDC on Base via x402). Hiring change detection vs history: newly opened roles, roles removed/closed (layoff or hiring freeze signal), team and location changes. Use for "did X just start/stop hiring", new job postings, recruiting trends, expansion or downsizing alerts.
No parameter schema on file.
PAID ($0.50 USDC on Base via x402). Highest-value workforce-intelligence report: hiring growth rate, which teams are scaling, geographic footprint, headcount estimate and executive takeaways for investors/recruiters/sales. Use to gauge if a company is expanding, for account research, competitive talent analysis, sourcing priorities.
No parameter schema on file.
PAID ($0.03 USDC per company via x402, max 50). Track hiring across a whole portfolio or target-account list in one call; per-company counts of new openings and closures. Use for recruitment agency monitoring, VC portfolio talent tracking, sales prospecting signals, sector hiring trends.
No parameter schema on file.
PAID ($5 USDC on Base via x402, up to 10 companies). Strategic hiring landscape: ranks an anchor company against peers by hiring volume and growth, shows which competitor is scaling fastest, team/geography shifts and talent-war signals. Use for competitive intelligence, market mapping, employer benchmarking.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Hiring Change Intelligence or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 1.0.0 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest00023bddc652f4103febc4fba72e5b7842c8ced48aea2d003bcd9bf14bb57dcf
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest00023bddc652f410
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.0. Pin a release below and the command asks for exactly that one.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Hiring Change Intelligence can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.