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.
Available components
Last scanned (4 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CRM and Sales
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. How we score → Why this is hard to score →
Endpoint Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +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.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- 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 functional
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 60
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://homerun.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of homerun.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://homerun.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://homerun.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://homerun.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://homerun.usefulapi.io/mcp |
| Authorisation server | https://homerun.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://homerun.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/homerun/ |
| http (plaintext) | http://homerun.usefulapi.io/mcp | Inconclusive | 302 | http://homerun.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
homerun_add_note Add a note to an application ~152
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Application id. |
| note | string | yes | The note text, 1-2000 characters. |
No output schema declared.
No examples provided.
homerun_get_application Get application (candidate) ~158
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).
| Name | Type | Req | Description |
|---|---|---|---|
| include_answers | boolean | – | Also return the application-form questions and the candidate's answers. |
| job_application_id | string | yes | Application id, e.g. ap_D3kCkoClbG6n6KlqD0ob. |
No output schema declared.
No examples provided.
homerun_get_vacancy Get vacancy ~88
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).
| Name | Type | Req | Description |
|---|---|---|---|
| vacancy_id | string | yes | Vacancy id, e.g. job_SnhUsAg1QwTRFIRNUfM6. |
No output schema declared.
No examples provided.
homerun_list_application_tags List an application's tags ~94
The tags attached to one application. GET /job-applications/{job_application_id}/tags (scope job-application-tags:read).
| Name | Type | Req | Description |
|---|---|---|---|
| job_application_id | string | yes | 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). |
No output schema declared.
No examples provided.
homerun_list_applications List applications (candidates) ~275
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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]). |
No output schema declared.
No examples provided.
homerun_list_notes List application notes ~107
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).
| Name | Type | Req | Description |
|---|---|---|---|
| job_application_id | string | yes | 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). |
No output schema declared.
No examples provided.
homerun_list_tags List tags ~74
List the company's candidate tags (id + name). GET /tags (scope tags:read).
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1 (default 1). Pass the previous reply's next_page. |
| perPage | integer | – | Results per page, 1-100 (default 15). |
No output schema declared.
No examples provided.
homerun_list_vacancies List vacancies ~164
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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"]. |
No output schema declared.
No examples provided.
homerun_move_application_to_stage Move application to a stage ~140
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).
| Name | Type | Req | Description |
|---|---|---|---|
| job_application_id | string | yes | Application id. |
| stage_id | string | yes | Hiring stage id from the vacancy's stages (homerun_get_vacancy). |
No output schema declared.
No examples provided.
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.
remote · homerun.usefulapi.io
claude mcp add --transport http io-usefulapi-homerun 'https://homerun.usefulapi.io/mcp'
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.