cv.json — open CV data
REMOTE · FREECV.ORG · 2 COMPONENTS · SCANNED SEP 22
Search people open to work and fetch their machine-readable cv.json, from any AI assistant.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 690 tokens (~172/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 Management77
- Stability observed for 23 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 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the cv.json — open CV data MCP server?
cv.json — open CV data is a hosted endpoint at https://freecv.org/api/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 · freecv.org
claude mcp add --transport http freecvorg-cvjson 'https://freecv.org/api/mcp'
{
"mcpServers": {
"freecvorg-cvjson": {
"url": "https://freecv.org/api/mcp"
}
}
} {
"servers": {
"freecvorg-cvjson": {
"type": "http",
"url": "https://freecv.org/api/mcp"
}
}
} [mcp_servers.freecvorg-cvjson] url = "https://freecv.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"freecvorg-cvjson": {
"type": "remote",
"url": "https://freecv.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add freecvorg-cvjson --url 'https://freecv.org/api/mcp' --transport streamable-http
mcp_servers:
freecvorg-cvjson:
url: "https://freecv.org/api/mcp" {
"McpServers": {
"freecvorg-cvjson": {
"Transport": "http",
"Url": "https://freecv.org/api/mcp"
}
}
} assistant mcp add freecvorg-cvjson -t streamable-http -u 'https://freecv.org/api/mcp'
{
"mcpServers": {
"freecvorg-cvjson": {
"type": "http",
"url": "https://freecv.org/api/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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 22 Sept 2026 · Probed https://freecv.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=freecv.org | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b081a9d4d195746213ac8193e3daf4bb |
| SANs: freecv.org, *.freecv.org | ||||||
| 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 freecv.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| freecv.org. | absent | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://freecv.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://freecv.org/api/mcp | HTTPS enforced | 301 | https://freecv.org/api/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 →
fetch_cv ~96
Fetch a person's cv.json — their full machine-readable CV — by FreeCV slug or livelink.cv URL. Returns structured JSON: basics, work, education, skills, languages, availability, ats, verification, i18n.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | – | The slug, e.g. "ashley" (from livelink.cv/ashley). |
| url | string | – | 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).
| Name | Type | Req | Description |
|---|---|---|---|
| employmentType | array | – | Only candidates open to one of these employment types. |
| languages | array | – | Languages the candidate must speak, e.g. ["German","Arabic"]. |
| limit | integer | – | Max results per page (default 20). |
| location | string | – | Country-aware location filter, e.g. "UK" (matches London/Manchester), "Berlin", "Gaza". |
| minYearsExp | integer | – | Minimum years of experience. |
| offset | integer | – | Result offset for paging through a large shortlist (default 0). Use with `total` in the response. |
| query | string | – | Free-text query matched across name, title, skills and experience (e.g. "senior react developer"). |
| skills | array | – | Specific skills to match, e.g. ["React","TypeScript"]. |
| sort | string | – | Ranking: best match (default), most recently updated, or most experienced. |
| sponsorship | boolean | – | Filter by visa-sponsorship need: false = does NOT need sponsorship, true = needs it. Candidates who never answered are excluded from this filter. |
| title | string | – | Target role/title, e.g. "Product Designer". |
| workType | array | – | 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[] }.
| Name | Type | Req | Description |
|---|---|---|---|
| cvjson | – | – | The cv.json document to validate (object or JSON string). |
| slug | string | – | Fetch and validate this slug's live cv.json. |
| url | string | – | Fetch and validate this cv.json URL. |
No output schema declared.
No examples provided.
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 hosted endpoint (https://freecv.org/api/mcp).
Is the cv.json — open CV data MCP server safe to use?
cv.json — open CV data scores 74 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 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 618 tokens of context every time the server is loaded.
Does the cv.json — open CV data MCP server require authentication?
No. We connected to cv.json — open CV data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.