mcpbeat

Talent MCP Server

cv.d/talent
answering

Talent is answering right now. Last checked 11 min ago. It exposes 7 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
675 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add talent --transport http https://d.cv/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "talent": {
      "url": "https://d.cv/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.talent]
url = "https://d.cv/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "talent": {
      "url": "https://d.cv/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "talent": {
      "url": "https://d.cv/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

fetch
fetch
Fetch a single d.cv profile in full as markdown, by its id (the handle returned from search).
open
get_open_to_work
List candidates who are currently open to work, optionally filtered by skills. Best when the user wants people actively looking.
profile
get_profile
Read a single candidate profile in full as clean markdown, by handle.
save
save_search
Save a talent search to your d.cv account so you can re-run it later. Requires your d.cv API key.
search
search
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.)
shortlist
add_to_shortlist
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.
talent
search_talent
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.

Endpoints

URLTransportStateLatencyChecked
https://d.cv/mcp streamable-http answering 744 ms 11 min ago

Talent — questions

Answers built from our own checks of this server.

What can Talent do?
It exposes 7 tools, read directly from the server on our last check. Among them: add_to_shortlist, fetch, get_open_to_work, get_profile, save_search, search and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Talent working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 675 ms. The bar chart above shows every period we have measured.
How do I connect Talent?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Talent need an API key?
No. Talent completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Talent?
It answers our handshake in 675 ms on average, which is faster than 13% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.