# HiringCensus (remote · hiringcensus.com)

Is this company actually hiring, or is the board just still up? Real dates on 187,923 roles.

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `hiringcensus.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-hiringcensus-hiring-census/api-mcp.md), [page](https://verifymcp.io/servers/com-hiringcensus-hiring-census/api-mcp)

## Channel facts

- Endpoint: `https://hiringcensus.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 79% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-hiringcensus-hiring-census 'https://hiringcensus.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hiringcensus-hiring-census": {
      "url": "https://hiringcensus.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hiringcensus-hiring-census": {
      "type": "http",
      "url": "https://hiringcensus.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hiringcensus-hiring-census]
url = "https://hiringcensus.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hiringcensus-hiring-census": {
      "type": "remote",
      "url": "https://hiringcensus.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hiringcensus-hiring-census --url 'https://hiringcensus.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hiringcensus-hiring-census:
    url: "https://hiringcensus.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hiringcensus-hiring-census": {
      "Transport": "http",
      "Url": "https://hiringcensus.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hiringcensus-hiring-census -t streamable-http -u 'https://hiringcensus.com/api/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 72, +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.

### 2026-09-17 (score 71, +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.

### 2026-09-15 (score 70, +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.

### 2026-09-13 (score 69, +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.

### 2026-09-11 (score 68, +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.

### 2026-09-10 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-09-09 (score 67, +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.

### 2026-09-06 (score 66, +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.

## MCP tools (6)

### `search_jobs` (~208 tokens)

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.

Input parameters:

- `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'

### `check_company` (~106 tokens)

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.

Input parameters:

- `company` (string, required): Company name

### `find_quiet_boards` (~67 tokens)

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.

Input parameters:

- `limit` (integer)

### `find_fresh_boards` (~72 tokens)

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.

Input parameters:

- `limit` (integer)

### `whats_changed` (~145 tokens)

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.

Input parameters:

- `companies` (array): Company names to watch. Omit for the whole market.
- `days` (integer): Window, default 7
- `limit` (integer)

### `hiring_stats` (~66 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hiringcensus-hiring-census/api-mcp#diagnostics

## Score history

- 2026-09-20: 72
- 2026-09-19: 72
- 2026-09-18: 71
- 2026-09-17: 71
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 69
- 2026-09-13: 69
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 67
- 2026-09-09: 67
- 2026-09-08: 66
- 2026-09-07: 66
- 2026-09-06: 66
- 2026-09-05: 65
- 2026-09-04: 65
- 2026-09-03: 64
- 2026-09-02: 64
- 2026-09-01: 63
- 2026-08-31: 63
- 2026-08-30: 62
- 2026-08-29: 63

## Common questions

### 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.

## Links

- Remote endpoint: https://hiringcensus.com/api/mcp
- Website: https://hiringcensus.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-hiringcensus-hiring-census/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hiringcensus-hiring-census/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-hiringcensus-hiring-census/api-mcp