# Resume Risk Checker by HireGPS (remote · risk-checker.hiregps.app)

Checks job dates for short stays and gaps, and looks up HireGPS resume risks and CV language rules

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `risk-checker.hiregps.app`: 78/100 (this document), [markdown](https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker.md), [page](https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker)

## Channel facts

- Endpoint: `https://risk-checker.hiregps.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **Endpoint Security**: 83/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.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 414 tokens (~82/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Resume Risk Checker by HireGPS MCP server?

Resume Risk Checker by HireGPS is a hosted endpoint at https://risk-checker.hiregps.app/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 app-hiregps-resume-risk-checker 'https://risk-checker.hiregps.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-hiregps-resume-risk-checker": {
      "url": "https://risk-checker.hiregps.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-hiregps-resume-risk-checker": {
      "type": "http",
      "url": "https://risk-checker.hiregps.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-hiregps-resume-risk-checker]
url = "https://risk-checker.hiregps.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-hiregps-resume-risk-checker": {
      "type": "remote",
      "url": "https://risk-checker.hiregps.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-hiregps-resume-risk-checker --url 'https://risk-checker.hiregps.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-hiregps-resume-risk-checker:
    url: "https://risk-checker.hiregps.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-hiregps-resume-risk-checker": {
      "Transport": "http",
      "Url": "https://risk-checker.hiregps.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-hiregps-resume-risk-checker -t streamable-http -u 'https://risk-checker.hiregps.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-hiregps-resume-risk-checker": {
      "type": "http",
      "url": "https://risk-checker.hiregps.app/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-20 (score 78, +5)

- [security improvement] DNSSEC: fail → pass
- [security improvement] HSTS header: fail → pass
- [security] Tool “check_employment_timeline” rewrote its description, which is the text the model reads
- [security] Tool “explain_resume_risk” rewrote its description, which is the text the model reads
- [security] Tool “get_cv_language_rule” rewrote its description, which is the text the model reads
- [security] Tool “get_scoring_method” rewrote its description, which is the text the model reads
- [security] Tool “list_resume_risks” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 68 → 82

### 2026-11-18 (score 73, +1)

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

### 2026-11-17 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 72)

First indexed and scored.

## MCP tools (5)

### `list_resume_risks` (~52 tokens)

List resume risks

Lists the 40 named rules HireGPS checks on a CV, as published on hiregps.app: each rule's name, severity, scoring category and source page.
Example input: {} (no arguments)

Output parameters:

- `note` (string)
- `risks` (array)
- `source` (string)

### `explain_resume_risk` (~94 tokens)

Explain a resume risk

Returns the published explanation of one HireGPS resume risk, looked up by name. Risks with their own page on hiregps.app return that page's full text; the others return the rule's severity and scoring category from the rule catalog. Every answer includes the source page.
Example input: {"risk": "Employment Gap"}

Input parameters:

- `risk` (string, required): The risk name, for example Employment Gap or Chronic Short Tenure.

Output parameters:

- `category` (string)
- `closing` (string)
- `introduction` (string)
- `note` (string)
- `risk` (string)
- `rules` (array)
- `sections` (array)
- `severity` (string)
- `severity_note` (string)
- `source` (string)

### `get_cv_language_rule` (~70 tokens)

CV language rule by country

Returns which language employers in one country expect a CV in, with the evidence grade and sources, from the HireGPS CV language research published on hiregps.app (20 countries).
Example input: {"country": "Germany"}

Input parameters:

- `country` (string, required): The country name in English, for example Germany.

Output parameters:

- `closest` (string)
- `country` (string)
- `found` (boolean)
- `message` (string)
- `research_date` (string)
- `rule` (array)
- `source` (string)
- `sources` (array)

### `get_scoring_method` (~84 tokens)

Scoring category weights

Returns the starting weights of the eight scoring categories in the HireGPS model for one seniority level, or for all seven levels, as published on hiregps.app.
Example input: {"seniority": "Senior"}

Input parameters:

- `seniority`: Optional seniority level: Entry, Junior, Mid-Level, Senior, Manager, Director or Executive. Leave empty for all seven.

Output parameters:

- `levels` (array)
- `note` (string)
- `source` (string)

### `check_employment_timeline` (~114 tokens)

Check employment dates

Checks job start and end dates for repeated short stays and unexplained gaps between jobs, with the same rules a full HireGPS analysis uses. It reads dates only. Returns the risks found, each with its page on hiregps.app.
Example input: {"roles": [{"start": "2020-06", "end": "2021-02"}, {"start": "2022-01"}]}

Input parameters:

- `roles` (array, required): Jobs, each with a start and end date in YYYY-MM or YYYY form.

Output parameters:

- `gaps_between_jobs_months` (array)
- `job_lengths_months` (array)
- `jobs` (integer)
- `note` (string)
- `risks` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 78
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72

## Common questions

### What is the Resume Risk Checker by HireGPS MCP server?

Resume Risk Checker by HireGPS is an MCP server listed in the public MCP registry as app.hiregps/resume-risk-checker. Checks job dates for short stays and gaps, and looks up HireGPS resume risks and CV language rules. This page covers its hosted endpoint (https://risk-checker.hiregps.app/mcp).

### Is the Resume Risk Checker by HireGPS MCP server safe to use?

Resume Risk Checker by HireGPS 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 Resume Risk Checker by HireGPS MCP server expose?

Resume Risk Checker by HireGPS exposes 5 tools: list_resume_risks, explain_resume_risk, get_cv_language_rule, get_scoring_method, check_employment_timeline. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.

### Does the Resume Risk Checker by HireGPS MCP server require authentication?

No. We connected to Resume Risk Checker by HireGPS without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Resume Risk Checker by HireGPS MCP server still maintained?

Resume Risk Checker by HireGPS is still listed as active in the MCP registry. We last reached this channel on 21 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 Resume Risk Checker by HireGPS MCP server?

VerifyMCP ran 13 checks on Resume Risk Checker by HireGPS, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 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://risk-checker.hiregps.app/mcp
- Website: https://www.hiregps.app/connect#resume-risk-checker
- Changelog RSS feed: https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker.json
- HTML version of this page: https://verifymcp.io/servers/app-hiregps-resume-risk-checker/risk-checker
