# HireHouse Jobs (remote · hirehouse.xyz)

Search, compare and inspect live public job listings on HireHouse, then apply on the portal.

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

> **Recent critical change**: TLS certificate (2026-11-03). See the changelog below before you install this server.

## Components

- remote · `hirehouse.xyz`: 78/100 (this document), [markdown](https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse.md), [page](https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse)

## Channel facts

- Endpoint: `https://hirehouse.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.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-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 510 tokens (~102/item across 5 items; 4 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 63/100
  - Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the HireHouse Jobs MCP server?

HireHouse Jobs is a hosted endpoint at https://hirehouse.xyz/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 aadarshvelu-hirehouse-mcp 'https://hirehouse.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "aadarshvelu-hirehouse-mcp": {
      "url": "https://hirehouse.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "aadarshvelu-hirehouse-mcp": {
      "type": "http",
      "url": "https://hirehouse.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.aadarshvelu-hirehouse-mcp]
url = "https://hirehouse.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "aadarshvelu-hirehouse-mcp": {
      "type": "remote",
      "url": "https://hirehouse.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add aadarshvelu-hirehouse-mcp --url 'https://hirehouse.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  aadarshvelu-hirehouse-mcp:
    url: "https://hirehouse.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "aadarshvelu-hirehouse-mcp": {
      "Transport": "http",
      "Url": "https://hirehouse.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add aadarshvelu-hirehouse-mcp -t streamable-http -u 'https://hirehouse.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "aadarshvelu-hirehouse-mcp": {
      "type": "http",
      "url": "https://hirehouse.xyz/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-11-04 (score 78, +1)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: fail → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.60
- [functional improvement] Score status: failed → scored

### 2026-11-03 (score 77, 0)

- [critical regression] TLS certificate: pass → fail
- [critical regression] Score status: scored → failed
- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.53 → unverified
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 77, +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-10-30 (score 76, +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-10-28 (score 75, +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-10-26 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 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.

### 2026-10-24 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 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.

## MCP tools (4)

### `search_jobs` (~194 tokens)

Search HireHouse jobs

Search currently active, reviewed, publicly listed Hirehouse roles. Every word in `query` must match the role's title, company, location or description. If nothing matches, related roles are returned instead with match: "related". Supports location, work mode, compensation, featured, recency, and sort filters. Results are public listings only.

Input parameters:

- `featuredOnly` (boolean): Whether to return only featured public roles
- `hasPayRange` (boolean): Whether the role must have an advertised pay range
- `location` (string): City, country, or location text from the public listing
- `page` (integer)
- `postedWithinDays` (integer): Only roles published within this many days
- `query` (string): Words from the role title, skills, company, or location, e.g. "backend engineer dubai"
- `sort` (string)
- `workMode` (string)

### `compare_jobs` (~51 tokens)

Compare HireHouse jobs

Compare two to five public HireHouse roles side by side by job ID. Returns public listing data, a description excerpt per role, and each role's HireHouse application URL.

Input parameters:

- `jobIds` (array, required)

### `get_job` (~33 tokens)

Get a HireHouse job

Get the public details, full description and Hirehouse portal application URL for one job.

Input parameters:

- `jobId` (string, required)

### `show_jobs` (~49 tokens)

Show HireHouse job cards

Display one to ten public HireHouse roles, by job ID, as interactive job cards. Each card links to that role's application page on the HireHouse portal.

Input parameters:

- `jobIds` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 77
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 75
- 2026-10-27: 74
- 2026-10-26: 74
- 2026-10-25: 73
- 2026-10-24: 73
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 71
- 2026-10-20: 71
- 2026-10-19: 71
- 2026-10-18: 70
- 2026-10-17: 70

## Common questions

### What is the HireHouse Jobs MCP server?

HireHouse Jobs is an MCP server listed in the public MCP registry as io.github.aadarshvelu/hirehouse-mcp. Search, compare and inspect live public job listings on HireHouse, then apply on the portal. This page covers its hosted endpoint (https://hirehouse.xyz/mcp).

### Is the HireHouse Jobs MCP server safe to use?

HireHouse Jobs scores 78 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 HireHouse Jobs MCP server expose?

HireHouse Jobs exposes 4 tools: search_jobs, compare_jobs, get_job, show_jobs. Their descriptions and schemas cost roughly 327 tokens of context every time the server is loaded.

### Does the HireHouse Jobs MCP server require authentication?

No. We connected to HireHouse Jobs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HireHouse Jobs MCP server still maintained?

HireHouse Jobs is still listed as active in the MCP registry. We last reached this channel on 5 November 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 HireHouse Jobs MCP server?

VerifyMCP ran 14 checks on HireHouse Jobs, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. 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.

## Links

- Remote endpoint: https://hirehouse.xyz/mcp
- Repository: https://github.com/aadarshvelu/hirehouse-mcp
- Website: https://hirehouse.xyz/mcp
- Changelog RSS feed: https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse.xml
- Changelog JSON feed: https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse.json
- HTML version of this page: https://verifymcp.io/servers/aadarshvelu-hirehouse-mcp/hirehouse