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.d/talent

REMOTE · D.CV · SCANNED SEP 24

Talent discovery for AI. Search and read agent-readable candidate profiles; cite by URL.

Available components

0 this week 79 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 579 tokens (~82/item across 7 items; 7 tools + 0 resources), lean.Pass
  • 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 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the cv.d/talent MCP server?

cv.d/talent is a hosted endpoint at https://d.cv/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 · d.cv

# add to Claude Code
claude mcp add --transport http cv-d-talent 'https://d.cv/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "cv-d-talent": {
      "url": "https://d.cv/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "cv-d-talent": {
      "type": "http",
      "url": "https://d.cv/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.cv-d-talent]
url = "https://d.cv/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cv-d-talent": {
      "type": "remote",
      "url": "https://d.cv/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cv-d-talent --url 'https://d.cv/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  cv-d-talent:
    url: "https://d.cv/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "cv-d-talent": {
      "Transport": "http",
      "Url": "https://d.cv/mcp"
    }
  }
}
# add to Vellum
assistant mcp add cv-d-talent -t streamable-http -u 'https://d.cv/mcp'
// mcp.json
{
  "mcpServers": {
    "cv-d-talent": {
      "type": "http",
      "url": "https://d.cv/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 26 Aug 26 79
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    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 24 Sept 2026 · Probed https://d.cv/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=d.cv CN=WE1,O=Google Trust Services,C=US 31 Aug 2026 29 Nov 2026 ECDSA 256 ECDSA-SHA256 7f30fe647a553e5d13a614967e8f6676
SANs: d.cv, *.d.cv
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 d.cv. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cv. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://d.cv/mcp Verified 200
http (plaintext) http://d.cv/mcp HTTPS enforced 301 https://d.cv/mcp
MCP tools · 7 exposed · ~499 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
add_to_shortlist ~86

Add a candidate to one of your d.cv shortlists (creates the shortlist if it does not exist). Requires your d.cv API key. Use after search_talent when the user wants to save someone.

NameTypeReqDescription
handlestringyesThe candidate handle to add, e.g. "kukuh"
shortliststringShortlist name. Defaults to "From AI".

No output schema declared.

No examples provided.

fetch ~47

Fetch a single d.cv profile in full as markdown, by its id (the handle returned from search).

NameTypeReqDescription
idstringyesThe profile id / handle, e.g. "kukuh"

No output schema declared.

No examples provided.

get_open_to_work ~65

List candidates who are currently open to work, optionally filtered by skills. Best when the user wants people actively looking.

NameTypeReqDescription
limitnumberMax results, 1-50 (default 25)
skillsstringOptional skills/role to filter by

No output schema declared.

No examples provided.

get_profile ~39

Read a single candidate profile in full as clean markdown, by handle.

NameTypeReqDescription
handlestringyesThe profile handle, e.g. "kukuh"

No output schema declared.

No examples provided.

save_search ~75

Save a talent search to your d.cv account so you can re-run it later. Requires your d.cv API key.

NameTypeReqDescription
namestringA name for the saved search
open_to_workbooleanWhether the search is limited to open-to-work
querystringyesThe search text to save

No output schema declared.

No examples provided.

search ~73

Search d.cv talent profiles by free-text query (name, role, skills, location). Returns lightweight results with an id, title, and url. Use fetch to read one in full. (Standard connector search tool.)

NameTypeReqDescription
querystringyesWhat to look for, e.g. "senior react engineer in berlin"

No output schema declared.

No examples provided.

search_talent ~114

Find published candidate profiles on d.cv by keyword, skill, role, location, and availability. Returns structured candidates with handle, url, headline, skills, and open-to-work status.

NameTypeReqDescription
limitnumberMax results, 1-50 (default 25)
open_to_workbooleanIf true, only return candidates open to work
querystringKeywords across name, headline, location, and skills
skillsstringAlias of query; specific skills to match

No output schema declared.

No examples provided.

Common questions

What is the cv.d/talent MCP server?

cv.d/talent is an MCP server listed in the public MCP registry as cv.d/talent. Talent discovery for AI. Search and read agent-readable candidate profiles; cite by URL. This page covers its hosted endpoint (https://d.cv/mcp).

Is the cv.d/talent MCP server safe to use?

cv.d/talent scores 79 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.d/talent MCP server expose?

cv.d/talent exposes 7 tools: search, fetch, search_talent, get_open_to_work, get_profile, and 2 more. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.

Does the cv.d/talent MCP server require authentication?

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

Is the cv.d/talent MCP server still maintained?

cv.d/talent is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.