Refine Job Search
REMOTE · MCP.GETREFINE.CO · SCANNED SEP 20
Job search management: applications, interviews, offers, recruiter email, and company openings.
Available components
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 Security81
- 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 answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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 supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 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
- Tool/resource definitions use about 4003 tokens (~67/item across 59 items; 55 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
- Stability check failed: schema churn in the 28 days we've observed: 30 tool removals, 6 breaking changes, 0 auth/transport breaks, 23 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Refine Job Search MCP server?
Refine Job Search is a hosted endpoint at https://mcp.getrefine.co/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 · mcp.getrefine.co
claude mcp add --transport http co-getrefine-refine 'https://mcp.getrefine.co/mcp'
{
"mcpServers": {
"co-getrefine-refine": {
"url": "https://mcp.getrefine.co/mcp"
}
}
} {
"servers": {
"co-getrefine-refine": {
"type": "http",
"url": "https://mcp.getrefine.co/mcp"
}
}
} [mcp_servers.co-getrefine-refine] url = "https://mcp.getrefine.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-getrefine-refine": {
"type": "remote",
"url": "https://mcp.getrefine.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-getrefine-refine --url 'https://mcp.getrefine.co/mcp' --transport streamable-http
mcp_servers:
co-getrefine-refine:
url: "https://mcp.getrefine.co/mcp" {
"McpServers": {
"co-getrefine-refine": {
"Transport": "http",
"Url": "https://mcp.getrefine.co/mcp"
}
}
} assistant mcp add co-getrefine-refine -t streamable-http -u 'https://mcp.getrefine.co/mcp'
{
"mcpServers": {
"co-getrefine-refine": {
"type": "http",
"url": "https://mcp.getrefine.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7.
- 27 Aug 26 0
- Server version: 0.5.1 → 0.5.2 functional
- 26 Aug 26 +2
- Stability: 0.07 → fail ▼ security
- Tool “interviews.add” was removed ▼ security
- Tool “interviews.delete” was removed ▼ security
- Tool “interviews.list” was removed ▼ security
- Tool “interviews.update” was removed ▼ security
- Tool “persona.remove_trait” was removed ▼ security
- Tool “recommendations.block” was removed ▼ security
- Tool “inbox.accept” was removed ▼ security
- Tool “inbox.status” was removed ▼ security
- Tool “jobs.update_notes” was removed ▼ security
- Tool “journey.update” was removed ▼ security
- Tool “notifications.list” was removed ▼ security
- Tool “notifications.read” was removed ▼ security
- Tool “notifications.read_all” was removed ▼ security
- Tool “offers.accept” was removed ▼ security
- Tool “offers.add_negotiation” was removed ▼ security
- Tool “offers.create” was removed ▼ security
- Tool “offers.decline” was removed ▼ security
- Tool “offers.delete” was removed ▼ security
- Tool “offers.delete_negotiation” was removed ▼ security
- Tool “offers.get” was removed ▼ security
- Tool “offers.update” was removed ▼ security
- Tool “persona.confirm_trait” was removed ▼ security
- Tool “persona.correct_trait” was removed ▼ security
- Tool “recommendations.dismiss” was removed ▼ security
- Tool “recommendations.feedback” was removed ▼ security
- Tool “recommendations.get” was removed ▼ security
- Tool “recommendations.list” was removed ▼ security
- Tool “recommendations.restore” was removed ▼ security
- Tool “recommendations.watch” was removed ▼ security
- Tool “signals.save_opening” was removed ▼ security
- First check of Injection markers: pass security
- First check of Judged manipulation: pass security
- New tool “inbox.apply_suggestion”, which the server declares destructive security
- New tool “jobs.interviews.delete”, which the server declares destructive security
- New tool “jobs.offer.accept”, which the server declares destructive security
- New tool “jobs.offer.decline”, which the server declares destructive security
- New tool “jobs.offer.delete”, which the server declares destructive security
- New tool “jobs.offer.delete_negotiation”, which the server declares destructive security
- Tool “inbox.acknowledge” rewrote its description, which is the text the model reads security
- Tool “inbox.undo” rewrote its description, which is the text the model reads security
- Tool “integrations.connect_google” rewrote its description, which is the text the model reads security
- Tool “jobs.archive” rewrote its description, which is the text the model reads security
- Tool “jobs.delete” rewrote its description, which is the text the model reads security
- Tool “jobs.refresh” rewrote its description, which is the text the model reads security
- Tool “jobs.update” no longer declares itself destructive security
- Tool “signals.update” no longer declares itself destructive security
- Tool “inbox.acknowledge” is now declared destructive security
- Schema quality: 59 → 67 ▼ functional
- “inbox.acknowledge” added a required parameter “confirmed”, so existing callers break ▼ functional
- “inbox.dismiss” added a required parameter “confirmed”, so existing callers break ▼ functional
- “inbox.undo” added a required parameter “confirmed”, so existing callers break ▼ functional
- “inbox.unsubscribe” added a required parameter “confirmed”, so existing callers break ▼ functional
- “jobs.delete” added a required parameter “confirmed”, so existing callers break ▼ functional
- “signals.untrack” added a required parameter “confirmed”, so existing callers break ▼ functional
- Schema quality: 78% → 100% ▲ functional
- First check of Destructive annotations: 100 functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.4.1 → 0.5.1 functional
- New tool “inbox.sync_status” functional
- New tool “jobs.interviews.add” functional
- New tool “jobs.interviews.update” functional
- New tool “jobs.offer.add_negotiation” functional
- New tool “jobs.offer.create” functional
- New tool “jobs.offer.update” functional
- New tool “signals.openings.list” functional
- New tool “signals.openings.mark_all_read” functional
- New tool “signals.openings.mark_read” functional
- New tool “signals.openings.save” functional
- New tool “signals.recommendations.block” functional
- New tool “signals.recommendations.dismiss” functional
- New tool “signals.recommendations.feedback” functional
- New tool “signals.recommendations.get” functional
- New tool “signals.recommendations.list” functional
- New tool “signals.recommendations.restore” functional
- New tool “signals.recommendations.watch” functional
- “inbox.list” added an optional parameter “limit” cosmetic
- “inbox.list” added an optional parameter “page” cosmetic
- “jobs.update” added an optional parameter “notes” cosmetic
- “signals.list_applied_jobs” added an optional parameter “limit” cosmetic
- “signals.list_applied_jobs” added an optional parameter “page” cosmetic
- “jobs.add” dropped the optional parameter “captured_at” cosmetic
- “jobs.add” dropped the optional parameter “journey_id” cosmetic
- “jobs.add” dropped the optional parameter “state” cosmetic
- “jobs.update” dropped the optional parameter “captured_at” cosmetic
- “jobs.update” dropped the optional parameter “journey_id” cosmetic
- “jobs.update” dropped the optional parameter “state” cosmetic
- 25 Aug 26 +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.
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 20 Sept 2026 · Probed https://mcp.getrefine.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getrefine.co | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 3db43164c218b627132c77f2c8a20f36 |
| SANs: getrefine.co, mcp.getrefine.co, *.mcp.getrefine.co | ||||||
| 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 mcp.getrefine.co. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| getrefine.co. | 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 | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.getrefine.co/.well-known/oauth-protected-resource", scope="openid read_user read_jobs write_jobs read_signals write_signals read_inbox write_inbox read_integrations write_integrations"
Bearer resource_metadata="https://mcp.getrefine.co/.well-known/oauth-protected-resource", scope="openid read_user read_jobs write_jobs read_signals write_signals read_inbox write_inbox read_integrations write_integrations"Protected resource metadata
| Document | https://mcp.getrefine.co/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.getrefine.co/mcp |
| Authorisation server | https://api.getrefine.co |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.getrefine.co/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.getrefine.co/mcp | Inconclusive | 401 |
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 →
signals.recommendations.watch ~34
Start tracking a recommended company (converts it into a signal)
| Name | Type | Req | Description |
|---|---|---|---|
| recommendation_id | string | yes | Recommendation id |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | – | – |
No examples provided.
signals.resume ~28
Resume tracking for a company
| Name | Type | Req | Description |
|---|---|---|---|
| signal_id | string | yes | Signal (tracked company) id |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | – | – |
No examples provided.
signals.track ~129
Start tracking a company for new job openings
| Name | Type | Req | Description |
|---|---|---|---|
| careers_url | string | yes | URL of the company careers page |
| company_name | string | yes | Name of the company |
| departments | array | – | Departments to filter by |
| exclude_keywords | array | – | Keywords to exclude |
| include_keywords | array | – | Keywords that must appear in the role |
| locations | array | – | Locations to filter by; use "remote" for remote roles |
| seniority_levels | array | – | Seniority levels to include |
| sync_frequency | string | – | How often Refine should refresh this company |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | – | – |
No examples provided.
signals.untrack ~77
Stop tracking a company and delete its signal. Confirm with the user first; they stop getting new openings from it. To stop notifications temporarily instead, use signals.pause.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | yes | Must be true after the user confirms they want to stop tracking the company |
| signal_id | string | yes | Signal (tracked company) id |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Human-readable confirmation of the action |
No examples provided.
signals.update ~115
Update filters on a tracked company
| Name | Type | Req | Description |
|---|---|---|---|
| departments | array | – | Departments to filter by |
| exclude_keywords | array | – | Keywords to exclude |
| include_keywords | array | – | Keywords that must appear in the role |
| locations | array | – | Locations to filter by; use "remote" for remote roles |
| seniority_levels | array | – | Seniority levels to include |
| signal_id | string | yes | Signal (tracked company) id |
| sync_frequency | string | – | How often Refine should refresh this company |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | – | – |
No examples provided.
What is the Refine Job Search MCP server?
Refine Job Search is an MCP server listed in the public MCP registry as co.getrefine/refine. Job search management: applications, interviews, offers, recruiter email, and company openings. This page covers its hosted endpoint (https://mcp.getrefine.co/mcp).
Is the Refine Job Search MCP server safe to use?
Refine Job Search scores 81 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 Refine Job Search MCP server expose?
Refine Job Search exposes 55 tools: jobs.list, jobs.get, jobs.add, jobs.update, jobs.delete, and 50 more. Their descriptions and schemas cost roughly 3,922 tokens of context every time the server is loaded.
Does the Refine Job Search MCP server require authentication?
Yes. Refine Job Search 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 Refine Job Search MCP server still maintained?
Refine Job Search 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.