Hiring Change Intelligence
REMOTE · S-HIRING.PIXHARVEST.COM · 2 COMPONENTS
Track public job boards: free snapshot, paid hiring-growth intel via x402 USDC.
Available components
Last scanned (34 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 10 Oct 2026.
Category CRM and Sales
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC not yet verified: we couldn't validate it against a resolver. View diagnostics → Unverified
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (2)
- HTTPS
- Transport
Checks we could not complete (9)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- DNSSEC in Endpoint SecurityDNSSEC not yet verified: we couldn't validate it against a resolver.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 18 Oct 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 17 Oct 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 16 Oct 26 −11
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Oct 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 −12
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- DNSSEC: fail → unverified ▼ security
- Stability: 0.30 → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 20 to 30. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 17. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 18 Oct 2026 · Probed https://s-hiring.pixharvest.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC inconclusive
Validation of s-hiring.pixharvest.com. — Inconclusive
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| s-hiring.pixharvest.com. | Error no A/AAAA/CNAME RRset answered for the name |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://s-hiring.pixharvest.com/mcp | Unreachable | ||
| http (plaintext) | http://s-hiring.pixharvest.com/mcp | HTTPS enforced |
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 →
hiring_batch_scan ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
No output schema declared.
No examples provided.
hiring_changes ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
No output schema declared.
No examples provided.
hiring_intel_report ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
No output schema declared.
No examples provided.
hiring_landscape ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| anchor | string | – | – |
| companies | array | yes | – |
No output schema declared.
No examples provided.
hiring_snapshot ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Hiring Change Intelligence MCP server?
Hiring Change Intelligence is a hosted endpoint at https://s-hiring.pixharvest.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 · s-hiring.pixharvest.com
claude mcp add --transport http contentforge-press-hiring-intel 'https://s-hiring.pixharvest.com/mcp'
What is the Hiring Change Intelligence MCP server?
Hiring Change Intelligence is an MCP server listed in the public MCP registry as io.github.contentforge-press/hiring-intel. Track public job boards: free snapshot, paid hiring-growth intel via x402 USDC. This page covers its hosted endpoint (https://s-hiring.pixharvest.com/mcp).
Is the Hiring Change Intelligence MCP server safe to use?
Hiring Change Intelligence scores 0 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 Hiring Change Intelligence MCP server expose?
Hiring Change Intelligence exposes 5 tools: hiring_snapshot, hiring_changes, hiring_intel_report, hiring_batch_scan, hiring_landscape. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.
Does the Hiring Change Intelligence MCP server require authentication?
Its publisher declares no required credentials for Hiring Change Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Hiring Change Intelligence MCP server still maintained?
Hiring Change Intelligence has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 10 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Hiring Change Intelligence MCP server?
VerifyMCP ran 2 checks on Hiring Change Intelligence, covering HTTPS and Transport. 9 items could not be completed, a gap on our side rather than a finding about Hiring Change Intelligence: TLS certificate, Authorization, HSTS header, DNSSEC and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.