Home / MCP registry index / team.yardstick/yardstick
Yardstick ATS
team.yardstick/yardstick in the official MCP registry.
Endpoint https://api.yardstick.team/mcp. Source: github.com/yardstickinc/yardstick-mcp.
The registry describes it as: Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.
On 2026-10-31 we read its 200 tools, but part of what it advertised was cut before our rules saw it: a description or schema past the size we read, more tools than we read, or a tool list split across pages. Nothing in the part we read matched, but the rest was not checked: this is not a clean result.
Tools it advertises
yardstick_slack_status yardstick_notifications_get yardstick_notifications_set yardstick_notifications_reset yardstick_notifications_org_defaults_get yardstick_notifications_org_defaults_set yardstick_offers_list yardstick_offers_read yardstick_offers_timeline yardstick_offers_create yardstick_offers_update yardstick_offers_submit_for_approval yardstick_offers_approval_review yardstick_offers_send_status yardstick_offers_status yardstick_offers_signed_copy yardstick_offers_open_revision yardstick_offers_cancel_revision yardstick_offers_verification_policy_read yardstick_offers_verification_policy_update yardstick_offers_lifecycle_policy_read yardstick_offers_lifecycle_policy_update yardstick_offers_countersignature_read yardstick_offers_countersignature_update yardstick_offers_library_documents_list yardstick_offers_library_documents_create yardstick_offers_library_documents_read yardstick_offers_library_documents_update_draft yardstick_offers_library_documents_publish yardstick_offers_library_documents_copy yardstick_offers_library_documents_archive yardstick_offers_library_packets_list yardstick_offers_library_packets_create yardstick_offers_library_packets_update yardstick_offers_library_packets_archive yardstick_offers_library_packets_reorder yardstick_offers_documents_list yardstick_offers_documents_add yardstick_offers_documents_remove yardstick_offers_documents_reorder yardstick_offers_documents_edit yardstick_offers_answers_update yardstick_offers_documents_change_packet yardstick_offers_signed_files_list yardstick_offers_signed_files_download yardstick_offers_approval_preview yardstick_offers_send_preview yardstick_offers_rescind_preview yardstick_offers_approval_bind yardstick_offers_send_bind yardstick_offers_rescind_bind yardstick_identity yardstick_tasks_list yardstick_tasks_respond yardstick_tasks_deep_link yardstick_people_list yardstick_people_read yardstick_people_documents_list yardstick_people_documents_download_url yardstick_people_create and 140 more
Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.
Run this server? Show the check in your README
The badge reflects the latest read: 
[](https://lazaretto.dev/mcp-registry/team-yardstick-yardstick)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. How tool poisoning works. What we found across the registry. Check another server.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.