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.

cv.json — open CV data

NPM · CVJSON-MCP · 2 COMPONENTS

Search people open to work and fetch their machine-readable cv.json, from any AI assistant.

0 this week 83 Trust /100

Last scanned (21 hours ago)

Scores higher than 73% of npm servers

Category CRM and Sales

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 82 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 663 tokens (~165/item across 4 items; 4 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 9 Nov 26 −1
    • Stability: pass → 0.90 functional
  • 3 Nov 26 0
    • Stability: 0.97 → pass security
  • 2 Nov 26 0
    • Stability: pass → 0.97 functional
  • 21 Oct 26 0
    • Stability: 0.97 → pass security
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 · Analysed npm/cvjson-mcp@1.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~616 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
fetch_cv ~94

Fetch a person's cv.json — their full machine-readable CV — by slug or livelink.cv URL. Returns structured JSON: basics, work, education, skills, languages, availability, ats, verification, i18n.

NameTypeReqDescription
slugstring–The slug, e.g. "ashley" (from livelink.cv/ashley).
urlstring–Full cv.json URL (alternative to slug).

No output schema declared.

No examples provided.

get_cvjson_schema ~34

Return the official cv.json JSON Schema (the format spec) — use it to understand or generate a compliant cv.json.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_open_to_work ~392

Search FreeCV's LIVE index of real people who are open to work — by skills, role/title, location, and recruiter facets (work type, employment type, visa sponsorship, languages, minimum experience). Returns lean candidate cards (name, current role @ company, location, top skills, languages, and the full availability preferences) plus each person's cv.json URL and portfolio URL — enough to shortlist WITHOUT a fetch_cv per candidate. Call fetch_cv on a result to read the complete structured CV. Only already-public profiles are indexed; contact details are never returned (reach candidates via their portfolio).

NameTypeReqDescription
employmentTypearray–Only candidates open to one of these employment types.
languagesarray–Languages the candidate must speak, e.g. ["German","Arabic"].
limitinteger–Max results per page (default 20).
locationstring–Country-aware location filter, e.g. "UK" (matches London/Manchester), "Berlin", "Gaza".
minYearsExpinteger–Minimum years of experience.
offsetinteger–Result offset for paging through a large shortlist (default 0). Use with `total` in the response.
querystring–Free-text query matched across name, title, skills and experience (e.g. "senior react developer").
skillsarray–Specific skills to match, e.g. ["React","TypeScript"].
sortstring–Ranking: best match (default), most recently updated, or most experienced.
sponsorshipboolean–Filter by visa-sponsorship need: false = does NOT need sponsorship, true = needs it. Candidates who never answered are excluded from this filter.
titlestring–Target role/title, e.g. "Product Designer".
workTypearray–Only candidates who OFFER one of these work arrangements.

No output schema declared.

No examples provided.

validate_cv ~96

Validate a cv.json document against the official cv.json schema. Provide the document (cvjson: object or JSON string) OR a slug/url to fetch and validate. Returns { valid, errors[] }.

NameTypeReqDescription
cvjson––The cv.json document to validate (object or JSON string).
slugstring–Fetch and validate this slug's live cv.json.
urlstring–Fetch and validate this cv.json URL.

No output schema declared.

No examples provided.

Install

How do I install the cv.json — open CV data MCP server?

cv.json — open CV data runs locally as an npm package, launched with npx -y cvjson-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · cvjson-mcp

# add to Claude Code
claude mcp add freecvorg-cvjson -- npx -y cvjson-mcp
Common questions

What is the cv.json — open CV data MCP server?

cv.json — open CV data is an MCP server listed in the public MCP registry as io.github.freecvorg/cvjson. Search people open to work and fetch their machine-readable cv.json, from any AI assistant. This page covers its npm package (cvjson-mcp).

Is the cv.json — open CV data MCP server safe to use?

cv.json — open CV data scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 cv.json — open CV data MCP server expose?

cv.json — open CV data exposes 4 tools: search_open_to_work, fetch_cv, validate_cv, get_cvjson_schema. Their descriptions and schemas cost roughly 616 tokens of context every time the server is loaded.

Is the cv.json — open CV data MCP server still maintained?

cv.json — open CV data 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 licence is the cv.json — open CV data MCP server under?

cv.json — open CV data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the cv.json — open CV data MCP server?

VerifyMCP ran 16 checks on cv.json — open CV data, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.