cv.json — open CV data MCP server
io.github.freecvorg/cvjsonfreecvorgstreamable-httpv1.1.1Scanned
Search people open to work and fetch their machine-readable cv.json, from any AI assistant.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the cv.json — open CV data MCP server can do
The cv.json — open CV data MCP server is published by the GitHub account freecvorg. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (fetch_cv); 2 tools can send data out of your system (fetch_cv and validate_cv).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
fetch_cvFetch a person's cv.json — their full machine-readable CV — by FreeCV slug or livelink.cv URL.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "fetch_cv" says "fetch": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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.
get_cvjson_schemaReturn the official cv.json JSON Schema (the format spec) — use it to understand or generate a compliant cv.json.No findings
Why it is in this group
- The name "get_cvjson_schema" says "get": a word for reading.
Description, as the server wrote it Return the official cv.json JSON Schema (the format spec) — use it to understand or generate a compliant cv.json.
search_open_to_workSearch 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, min…No findings
Why it is in this group
- The name "search_open_to_work" says "search": a word for reading.
Description, as the server wrote it 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).
validate_cvValidate a cv.json document against the official cv.json schema.Can send data outNo findings
Why it is in this group
- The name "validate_cv" says "validate": a word for reading.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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[] }.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http cvjson https://freecv.org/api/mcpclaude mcp add --transport http cvjson https://freecv.org/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__cvjson__search_open_to_work",
"mcp__cvjson__get_cvjson_schema"
],
"ask": [
"mcp__cvjson__fetch_cv",
"mcp__cvjson__validate_cv"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as cvjson. Review it before you use it.
Capability tags behind 2 rules
- mcp__cvjson__fetch_cv untrusted-input, outbound
- mcp__cvjson__validate_cv outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.freecvorg/cvjson/verify?hash=3b897ba4b29dadd0b76639f2e4a7d056750164ee921ca69b01737acf081011f0" | jq -e '.changed == false'Pinned hash 3b897ba4b29d, from Nov 19, 2026, 18:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.freecvorg/cvjson/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.freecvorg/cvjson)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:34 UTC.
cv.json — open CV data MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the cv.json — open CV data MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the cv.json — open CV data MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the cv.json — open CV data MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the cv.json — open CV data MCP server have?
- 4 tools: 4 read. search_open_to_work, fetch_cv, validate_cv and get_cvjson_schema.
Does the cv.json — open CV data MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the cv.json — open CV data MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): fetch_cv and validate_cv.
Has the cv.json — open CV data MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.