Home / MCP registry index / io.usefulapi/talenthr

TalentHR MCP by usefulapi

io.usefulapi/talenthr in the official MCP registry. Endpoint https://talenthr.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read employees, leave, recruiting and reports; book or decide leave and add applicant notes.

We read its 29 tools on 2026-11-01. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http talenthr https://talenthr.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "talenthr": {
      "url": "https://talenthr.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"talenthr","type":"http","url":"https://talenthr.usefulapi.io/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

talenthr_list_employees talenthr_get_directory_filters talenthr_get_employee talenthr_get_employee_job talenthr_get_organization_chart talenthr_list_departments talenthr_list_divisions talenthr_list_locations talenthr_list_job_titles talenthr_list_time_off_types talenthr_list_employee_time_off_requests talenthr_get_employee_time_off_budgets talenthr_get_calendar talenthr_list_holidays talenthr_list_benefits talenthr_get_employee_benefits talenthr_list_assets talenthr_get_employee_assets talenthr_list_job_positions talenthr_list_job_position_applicants talenthr_list_applicants talenthr_get_applicant talenthr_get_headcount_report talenthr_get_hires_leaves_report talenthr_get_time_off_report talenthr_list_time_tracking_entries talenthr_create_time_off_request talenthr_reply_time_off_request talenthr_create_applicant_note

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-01): c66ebbeb33eee24a. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-usefulapi-talenthr/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-talenthr)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.