# Homerun MCP by usefulapi (remote · homerun.usefulapi.io)

Read Homerun vacancies, applications, notes and tags; move an application to a stage or add a note.

- Trust score: 64/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `homerun.usefulapi.io`: 64/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-homerun/homerun.md), [page](https://verifymcp.io/servers/io-usefulapi-homerun/homerun)

## Channel facts

- Endpoint: `https://homerun.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1455 tokens (~161/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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 Homerun MCP by usefulapi server?

Homerun MCP by usefulapi is a hosted endpoint at https://homerun.usefulapi.io/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 io-usefulapi-homerun 'https://homerun.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-homerun": {
      "url": "https://homerun.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-homerun": {
      "type": "http",
      "url": "https://homerun.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-homerun]
url = "https://homerun.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-homerun": {
      "type": "remote",
      "url": "https://homerun.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-homerun --url 'https://homerun.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-homerun:
    url: "https://homerun.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-homerun": {
      "Transport": "http",
      "Url": "https://homerun.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-homerun -t streamable-http -u 'https://homerun.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-homerun": {
      "type": "http",
      "url": "https://homerun.usefulapi.io/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-10-16 (score 64, +1)

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

### 2026-10-14 (score 63, +2)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “prompts” capability
- [functional] First check of Schema quality: 100
- [functional] New prompt “getting_started”
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-13 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 60)

First indexed and scored.

## MCP tools (9)

### `homerun_list_vacancies` (~164 tokens)

List vacancies

List job vacancies (draft, private, public, ...) with title, status, type, location type and expiry. Optionally include location, department, hiring stages (their ids are what homerun_move_application_to_stage needs), salary indication and the candidate count. GET /vacancies (scope vacancies:read).

Input parameters:

- `include` (array): Extra data to include. Use stages to see the hiring stage ids.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perPage` (integer): Results per page, 1-100 (default 15).
- `status` (array): Only vacancies in these statuses, e.g. ["public","private"] or ["draft"].

### `homerun_get_vacancy` (~88 tokens)

Get vacancy

One vacancy by id with description, location, department, hiring stages (id + name), salary indication, candidate count and the public job and application-form URLs. GET /vacancies/{vacancy_id} (scope vacancies:read).

Input parameters:

- `vacancy_id` (string, required): Vacancy id, e.g. job_SnhUsAg1QwTRFIRNUfM6.

### `homerun_list_applications` (~275 tokens)

List applications (candidates)

List job applications, newest page first as the API orders them. Each item has name, e-mail, vacancy id, current stage (id + name), rating, created/hired dates and disqualified flag. Personal data: no phone number, date of birth, photo or files are returned here; ask for one application with homerun_get_application. Filter by vacancy, stage name or disqualified state and page through; do not use it to export all candidates. GET /job-applications (scope job-applications:read).

Input parameters:

- `disqualified` (boolean): true = only disqualified, false = only not disqualified.
- `hired_after` (string): Only applicants hired after this date, yyyy-mm-dd.
- `include_sources` (boolean): Also return the sources (e.g. Homerun Career Page, Indeed) of each application.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perPage` (integer): Results per page, 1-100 (default 15).
- `stage` (string): Only applications in the hiring stage with this name (stage names belong to a vacancy, so combine with vacancy_id).
- `vacancy_id` (array): Only applications of these vacancy ids (filter[vacancy_id]).

### `homerun_get_application` (~158 tokens)

Get application (candidate)

One job application in full: contact details (name, e-mail, phone, city, country), links, experience/education, current stage, rating, sources and file names (notes: use homerun_list_notes). Date of birth, photo URL and file download links are never returned. Optionally include the answers to the application-form questions. Personal data: fetch only the candidate you need. GET /job-applications/{job_application_id} (scope job-applications:read).

Input parameters:

- `include_answers` (boolean): Also return the application-form questions and the candidate's answers.
- `job_application_id` (string, required): Application id, e.g. ap_D3kCkoClbG6n6KlqD0ob.

### `homerun_list_notes` (~107 tokens)

List application notes

List the notes on one application: id, author display name, text, sensitive flag and timestamps. GET /job-applications/{job_application_id}/notes (scope job-application-notes:read).

Input parameters:

- `job_application_id` (string, required): Application id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perPage` (integer): Results per page, 1-100 (default 15).

### `homerun_list_tags` (~74 tokens)

List tags

List the company's candidate tags (id + name). GET /tags (scope tags:read).

Input parameters:

- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perPage` (integer): Results per page, 1-100 (default 15).

### `homerun_list_application_tags` (~94 tokens)

List an application's tags

The tags attached to one application. GET /job-applications/{job_application_id}/tags (scope job-application-tags:read).

Input parameters:

- `job_application_id` (string, required): Application id.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `perPage` (integer): Results per page, 1-100 (default 15).

### `homerun_move_application_to_stage` (~140 tokens)

Move application to a stage

WRITE: move ONE application to another hiring stage of its vacancy (PATCH with only the stage id; nothing else on the application changes). Get stage ids from homerun_get_vacancy. Homerun's own automations for that stage may run (for example automatic e-mails configured in Homerun); this tool sends no e-mail itself and does not reject or delete anyone. PATCH /job-applications/{job_application_id} (scope job-applications:write).

Input parameters:

- `job_application_id` (string, required): Application id.
- `stage_id` (string, required): Hiring stage id from the vacancy's stages (homerun_get_vacancy).

### `homerun_add_note` (~152 tokens)

Add a note to an application

WRITE: add ONE note (1-2000 characters) to one application. It becomes visible to the hiring team in Homerun and cannot be removed with this server. display_name is free text shown as the author. Nothing is sent to the candidate. POST /job-applications/{job_application_id}/notes (scope job-application-notes:write).

Input parameters:

- `display_name` (string): Author name shown on the note (default "AI assistant").
- `is_sensitive` (boolean): Mark the note as sensitive (restricts who can read it in Homerun).
- `job_application_id` (string, required): Application id.
- `note` (string, required): The note text, 1-2000 characters.

## Diagnostics

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

## Score history

- 2026-10-17: 64
- 2026-10-16: 64
- 2026-10-15: 63
- 2026-10-14: 63
- 2026-10-13: 61
- 2026-10-12: 60

## Common questions

### What is the Homerun MCP by usefulapi server?

Homerun MCP by usefulapi is listed in the public MCP registry as io.usefulapi/homerun. Read Homerun vacancies, applications, notes and tags; move an application to a stage or add a note. This page covers its hosted endpoint (https://homerun.usefulapi.io/mcp).

### Is the Homerun MCP by usefulapi server safe to use?

Homerun MCP by usefulapi scores 64 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 Homerun MCP by usefulapi server expose?

Homerun MCP by usefulapi exposes 9 tools: homerun_list_vacancies, homerun_get_vacancy, homerun_list_applications, homerun_get_application, homerun_list_notes, and 4 more. Their descriptions and schemas cost roughly 1,252 tokens of context every time the server is loaded.

### Does the Homerun MCP by usefulapi server require authentication?

Yes. Homerun MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Homerun MCP by usefulapi server still maintained?

Homerun MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 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://homerun.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/homerun/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-homerun/homerun.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-homerun/homerun.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-homerun/homerun