mcp-registry/com.hiringcensus/hiring-census · v1.0.0
As of 2026-10-26 18:41 UTC, the Hiringcensus Hiring Census MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 14 minutes.
Is this company actually hiring, or is the board just still up? Real dates on 187,923 roles.
Point your MCP client at this streamable-http endpoint: https://hiringcensus.com/api/mcp
6 of 6 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.hiringcensus%2Fhiring-census/fixes
{
"name": "check_company",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"company"
],
"properties": {
"company": {
"type": "string",
"description": "Company name"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_fresh_boards",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "find_quiet_boards",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {
"limit": {
"type": "integer"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.hiringcensus/hiring-census"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.hiringcensus/hiring-census"}) over MCP.
search_jobs ~304 tokenswhats_changed ~210 tokenscheck_company ~155 tokensfind_quiet_boards ~109 tokensfind_fresh_boards ~108 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.hiringcensus%2Fhiring-census?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.hiringcensus%2Fhiring-census?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hiringcensus%2Fhiring-census.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.hiringcensus%2Fhiring-census.svg :target: https://glimind.com/server/mcp-registry%2Fcom.hiringcensus%2Fhiring-census?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ee27386867d00494…, first seen 2026-10-17, included at leaf 3194 of 74,800. Version history · verify what your client received.
Compare: most reliable data servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 18:41 UTC, the Hiringcensus Hiring Census MCP server is up with a Glimind reliability score of 87/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 14 minutes.
Hiringcensus Hiring Census MCP server advertises 6 tools, including check_company, find_fresh_boards, find_quiet_boards, hiring_stats, search_jobs.
Point your MCP client at this streamable-http endpoint: https://hiringcensus.com/api/mcp
Glimind scanned all 6 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.