HiringCensus
REMOTE · HIRINGCENSUS.COM · SCANNED SEP 20
Is this company actually hiring, or is the board just still up? Real dates on 187,923 roles.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 756 tokens (~126/item across 6 items; 6 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 Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the HiringCensus MCP server?
HiringCensus is a hosted endpoint at https://hiringcensus.com/api/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 · hiringcensus.com
claude mcp add --transport http com-hiringcensus-hiring-census 'https://hiringcensus.com/api/mcp'
{
"mcpServers": {
"com-hiringcensus-hiring-census": {
"url": "https://hiringcensus.com/api/mcp"
}
}
} {
"servers": {
"com-hiringcensus-hiring-census": {
"type": "http",
"url": "https://hiringcensus.com/api/mcp"
}
}
} [mcp_servers.com-hiringcensus-hiring-census] url = "https://hiringcensus.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hiringcensus-hiring-census": {
"type": "remote",
"url": "https://hiringcensus.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-hiringcensus-hiring-census --url 'https://hiringcensus.com/api/mcp' --transport streamable-http
mcp_servers:
com-hiringcensus-hiring-census:
url: "https://hiringcensus.com/api/mcp" {
"McpServers": {
"com-hiringcensus-hiring-census": {
"Transport": "http",
"Url": "https://hiringcensus.com/api/mcp"
}
}
} assistant mcp add com-hiringcensus-hiring-census -t streamable-http -u 'https://hiringcensus.com/api/mcp'
{
"mcpServers": {
"com-hiringcensus-hiring-census": {
"type": "http",
"url": "https://hiringcensus.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 9 Sept 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.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 20 Sept 2026 · Probed https://hiringcensus.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hiringcensus.com | CN=WE1,O=Google Trust Services,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | eef81ff3cfa2655c1319874100a7db43 |
| SANs: hiringcensus.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 hiringcensus.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hiringcensus.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hiringcensus.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://hiringcensus.com/api/mcp | HTTPS enforced | 301 | https://hiringcensus.com/api/mcp |
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 →
check_company ~106
Ask whether a company is ACTUALLY hiring, not just whether it has jobs listed. Returns a verdict on the board -- actively_hiring, still_open, gone_quiet or likely_abandoned -- with the age of the newest posting, the median role age, and how many reqs have sat open over 90 days and over a year. This is the check that tells you whether an application or a sales approach is worth the time.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | Company name |
No output schema declared.
No examples provided.
find_fresh_boards ~72
Companies where EVERY currently open role was posted in the last 30 days -- no backlog of applicants ahead of you, and usually a team that just started hiring. For sales, a company that just opened its first roles in a function is one whose budget has recently moved.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
find_quiet_boards ~67
Companies still advertising open roles while having posted nothing new in over six months. Strong evidence of a board nobody tidied up after the hiring finished. Useful for striking dead accounts off a prospect list, or for avoiding applications that will never be read.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
hiring_stats ~66
Market-level hiring numbers measured this morning across every board we read: employers hiring, open roles, how many went up in the last 24 hours, how many have been open over 90 days and over a year, how many boards have gone quiet, and the most in-demand technologies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_jobs ~208
Search open job postings read directly from employers' own Greenhouse, Ashby and Lever boards. Unlike a job board, every result carries the employer's real publish date and age in days, so you can tell a role posted this morning from one that has been open two years.
| Name | Type | Req | Description |
|---|---|---|---|
| department | string | – | Function, e.g. 'Engineering', 'Sales' |
| limit | integer | – | Max results (default 25) |
| location | string | – | Any part of the location string, e.g. 'Berlin', 'California' |
| max_age_days | integer | – | Only roles posted within this many days |
| min_age_days | integer | – | Only roles OLDER than this many days -- use to hunt stale listings |
| query | string | – | Words in the job title, e.g. 'staff backend engineer' |
| remote | boolean | – | Only roles flagged remote |
| technology | string | – | Technology named in the posting, e.g. 'Python', 'Kubernetes' |
No output schema declared.
No examples provided.
whats_changed ~145
What actually MOVED, on a list of companies you name or across the whole record. Answers the question a person with a book of accounts has every morning: which of mine changed, and is anyone suddenly ramping? Returns NET movement, because a company that opened 342 roles and closed 317 is churning and one that opened 261 and closed 41 is hiring -- and flags a board whose VERDICT flipped, which is a budget unfreezing and the strongest signal in this data.
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | – | Company names to watch. Omit for the whole market. |
| days | integer | – | Window, default 7 |
| limit | integer | – | – |
No output schema declared.
No examples provided.
What is the HiringCensus MCP server?
HiringCensus is an MCP server listed in the public MCP registry as com.hiringcensus/hiring-census. Is this company actually hiring, or is the board just still up? Real dates on 187,923 roles. This page covers its hosted endpoint (https://hiringcensus.com/api/mcp).
Is the HiringCensus MCP server safe to use?
HiringCensus scores 72 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 HiringCensus MCP server expose?
HiringCensus exposes 6 tools: search_jobs, check_company, find_quiet_boards, find_fresh_boards, whats_changed, hiring_stats. Their descriptions and schemas cost roughly 664 tokens of context every time the server is loaded.
Does the HiringCensus MCP server require authentication?
No. We connected to HiringCensus without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HiringCensus MCP server still maintained?
HiringCensus is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.