Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CareerHolo

REMOTE · CAREERHOLO.COM

Find open tech jobs from companies' own job boards, match your skills, and see typical pay.

Available components

+3 this week 77 Trust /100

Last scanned (15 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1130 tokens (~161/item across 7 items; 7 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 Management37
  • Stability observed for 11 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 189 → 161 ▲ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “fetch” functional
    • New tool “search” functional
  • 16 Nov 26 +1

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

  • 14 Nov 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.

  • 12 Nov 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.

  • 11 Nov 26 +1
    • Tool “match_my_skills” rewrote its description, which is the text the model reads security
    • Tool coverage: 92% → 100% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • “company_jobs” reworded the description of “page” cosmetic
    • “search_jobs” reworded the description of “page” cosmetic
  • 10 Nov 26 71

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://careerholo.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=careerholo.com CN=YE2,O=Let's Encrypt,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA384 59eecaefa073ebfc1694b9fd3f3c3174eb6
SANs: *.careerholo.com, careerholo.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of careerholo.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
careerholo.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=86400
content-security-policy default-src 'self'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; style-src 'self' 'nonce-tOHObi7tZEbPXgvQF8_y6g'; font-src 'self'; script-src 'self' 'nonce-tOHObi7tZEbPXgvQF8_y6g' https://www.googletagmanager.com; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-ancestors 'none';
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://careerholo.com/mcp Verified 200
http (plaintext) http://careerholo.com/mcp HTTPS enforced 301 https://careerholo.com/mcp
MCP tools · 7 exposed · ~967 tokens

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 →

Tool Tokens
company_jobs ~73

One employer's open tech jobs, 20 a page, with how many it has open, the skills it hires for and its median stated pay.

NameTypeReqDescription
companystringyese.g. "Stripe"
pageinteger–Which page of results: 20 jobs a page, up to page 50

No output schema declared.

No examples provided.

fetch ~66

One job by the id search gives, as a document: the employer, place, level, pay and skills, then the posting (in full where the source allows, else an excerpt), its page and where to apply.

NameTypeReqDescription
idstringyesThe job's id, from search

No output schema declared.

No examples provided.

get_job ~61

One job's details by the id search_jobs gives: whether it is still open, the description (in full where the source allows, else an excerpt), skills, pay, work type and the links.

NameTypeReqDescription
job_idintegeryesThe job's id

No output schema declared.

No examples provided.

match_my_skills ~206

Rank open tech jobs by how well they fit a person's skills, the way CareerHolo's resume match does: a match percentage for each job, the skills they have and miss, and which skill to learn next for more jobs. Takes skills only, not a name, email or resume text. Nothing sent is stored.

NameTypeReqDescription
citystring–A city in that country, e.g. "Berlin"
countrystring–Where the person works from, e.g. "Germany": jobs there and remote jobs open to it
levelstring–The person's level
rolesarray–Kinds of job wanted; jobs next to them count too
skillsarrayyesThe person's skills, e.g. ["Python", "Django", "PostgreSQL", "AWS"]
visa_sponsorshipboolean–Only jobs that sponsor a visa
work_typestring–Only this way of working

No output schema declared.

No examples provided.

salary_for ~154

The median and typical range of stated pay for a tech role in a place, from open postings, in US dollars a year. Roles: Software, Backend, Frontend, Full Stack, Data, DevOps, Site Reliability, Machine Learning, Mobile, iOS, Android and Security Engineer, Data Scientist, Data Analyst, Product Manager, Engineering Manager, Technical Program Manager, UX Designer, UI Designer, Solutions Architect. Places: Remote, United States, UK, Germany, Netherlands, Canada, India, San Francisco, New York, London, Berlin, Amsterdam, Toronto, Bangalore.

NameTypeReqDescription
placestringyese.g. "Germany" or "Remote"
rolestringyese.g. "Backend Engineer"

No output schema declared.

No examples provided.

search ~82

Search open tech jobs with one line of words, e.g. "senior remote rust jobs in Europe" or "data engineer in Berlin with visa sponsorship". Returns up to 20 jobs, each with an id for fetch, a title naming the employer, place and stated pay, and its CareerHolo page.

NameTypeReqDescription
querystringyesWhat jobs to find

No output schema declared.

No examples provided.

search_jobs ~325

Search open tech jobs by keywords, place, skills, level, work type, visa sponsorship, pay and posting date. Returns 20 jobs a page, newest first, or the best title matches first when there are keywords. Each job has `url` (its CareerHolo page) and `apply_url` (the company's own page).

NameTypeReqDescription
companystring–One employer, e.g. "Stripe"
levelstring–Seniority: junior includes interns, senior includes leads
locationstring–A city, state or country, e.g. "Berlin", "Texas", "Canada", or "Remote"
min_salary_usdinteger–Stated pay of at least this, US dollars a year
pageinteger–Which page of results: 20 jobs a page, up to page 50
posted_withinstring–First seen within this many days
querystring–Keywords: a role, skill or company, e.g. "data engineer" or "rust"
remote_fromstring–Remote jobs open to people in this region
salary_statedboolean–Only jobs that state their pay
skillsarray–Skills every job must ask for, e.g. ["Python", "AWS"]
sortstring–Default: best title matches first when there are keywords
visa_sponsorshipboolean–Only jobs that say they sponsor a visa
work_typestring–How the job is worked

No output schema declared.

No examples provided.

Install

How do I install the CareerHolo MCP server?

CareerHolo is a hosted endpoint at https://careerholo.com/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 · careerholo.com

# add to Claude Code
claude mcp add --transport http amisini-careerholo 'https://careerholo.com/mcp'
Common questions

What is the CareerHolo MCP server?

CareerHolo is an MCP server listed in the public MCP registry as io.github.amisini/careerholo. Find open tech jobs from companies' own job boards, match your skills, and see typical pay. This page covers its hosted endpoint (https://careerholo.com/mcp).

Is the CareerHolo MCP server safe to use?

CareerHolo scores 77 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 CareerHolo MCP server expose?

CareerHolo exposes 7 tools: search_jobs, get_job, match_my_skills, salary_for, company_jobs, and 2 more. Their descriptions and schemas cost roughly 967 tokens of context every time the server is loaded.

Does the CareerHolo MCP server require authentication?

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

Is the CareerHolo MCP server still maintained?

CareerHolo 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 CareerHolo MCP server?

VerifyMCP ran 13 checks on CareerHolo, 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.