Yardstick ATS
REMOTE · API.YARDSTICK.TEAM
Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.
Available components
Last scanned (8 hours ago)
Scores higher than 93% of remote servers
Reachable. Last reached 17 Oct 2026.
Category CRM and Sales
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability52
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 14932 tokens (~71/item across 209 items; 209 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 19 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 209 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 17 Oct 26 +1
- Tool “yardstick_applications_decide” rewrote its description, which is the text the model reads security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 0
- New tool “yardstick_applications_decide”, which the server declares destructive security
- New tool “yardstick_automation_rules_bulk”, which the server declares destructive security
- New tool “yardstick_automation_starters_delete”, which the server declares destructive security
- New tool “yardstick_automation_starters_rename”, which the server declares destructive security
- New tool “yardstick_email_templates_delete”, which the server declares destructive security
- New tool “yardstick_email_templates_reset”, which the server declares destructive security
- New tool “yardstick_tasks_respond”, which the server declares destructive security
- Tool “yardstick_applications_list” rewrote its description, which is the text the model reads security
- Tool “yardstick_automation_rules_delete” rewrote its description, which is the text the model reads security
- Tool “yardstick_automation_rules_list” rewrote its description, which is the text the model reads security
- Tool “yardstick_automation_rules_read” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_template_versions_list” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_list” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_preview” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_preview_customization” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_publish” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_read” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_rollback” rewrote its description, which is the text the model reads security
- Tool “yardstick_email_templates_validate” rewrote its description, which is the text the model reads security
- Server version: 0.6.10 → 0.6.11 functional
- New tool “yardstick_automation_rules_copy” functional
- New tool “yardstick_automation_starters_apply” functional
- New tool “yardstick_automation_starters_create” functional
- New tool “yardstick_automation_starters_list” functional
- New tool “yardstick_automation_starters_preview” functional
- New tool “yardstick_automation_starters_save_job” functional
- New tool “yardstick_email_templates_create” functional
- New tool “yardstick_email_templates_duplicate” functional
- New tool “yardstick_pipelines_assign_to_job_preview” functional
- “yardstick_applications_list” added an optional parameter “job_id” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “job_id” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “needs_step_pick” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “pipeline_template_id” cosmetic
- “yardstick_automation_rules_list” added an optional parameter “department_id” cosmetic
- “yardstick_automation_rules_list” added an optional parameter “email” cosmetic
- “yardstick_automation_rules_list” added an optional parameter “is_active” cosmetic
- “yardstick_automation_rules_list” added an optional parameter “job_id” cosmetic
- “yardstick_automation_rules_list” added an optional parameter “pipeline_id” cosmetic
- “yardstick_automation_rules_list” added an optional parameter “trigger” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “job_id” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “needs_step_pick” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “pipeline_template_id” cosmetic
- “yardstick_pipelines_assign_to_job” added an optional parameter “stage_mapping” cosmetic
- “yardstick_automation_rules_create” made “pipeline_stage_id” optional cosmetic
- Tool “yardstick_email_templates_list” changed its title: List candidate email templates → List candidate and internal emails cosmetic
- Tool “yardstick_email_templates_preview” changed its title: Preview a candidate email template with sample data → Preview an email with sample data cosmetic
- Tool “yardstick_email_templates_publish” changed its title: Publish a candidate email template version → Publish an email version cosmetic
- Tool “yardstick_email_templates_read” changed its title: Read a candidate email template → Read an email cosmetic
- Tool “yardstick_email_templates_rollback” changed its title: Roll a candidate email template back to an earlier version → Restore an earlier email version cosmetic
- Tool “yardstick_email_templates_validate” changed its title: Check a candidate email template for problems → Check an email for problems cosmetic
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
- New tool “yardstick_applications_admit_candidate”, which the server declares destructive security
- New tool “yardstick_applications_undo_candidate_admission”, which the server declares destructive security
- New tool “yardstick_automation_runs_retry”, which the server declares destructive security
- Tool “yardstick_automation_rules_create” rewrote its description, which is the text the model reads security
- Tool “yardstick_automation_rules_update” rewrote its description, which is the text the model reads security
- Tool “yardstick_automation_runs_list” rewrote its description, which is the text the model reads security
- Tool “yardstick_interview_sessions_interviewers_assign” rewrote its description, which is the text the model reads security
- Server version: 0.6.9 → 0.6.10 functional
- New tool “yardstick_automation_rules_preview_rule” functional
- New tool “yardstick_pipelines_clone” functional
- New tool “yardstick_talent_search” functional
- “yardstick_automation_rules_create” added an optional parameter “delivery_mode” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “job_posting_ids” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “job_scope” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “name” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “starter_key” cosmetic
- “yardstick_automation_rules_create” added an optional parameter “timing” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “delivery_mode” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “job_posting_ids” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “job_scope” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “name” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “pipeline_stage_id” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “starter_key” cosmetic
- “yardstick_automation_rules_update” added an optional parameter “timing” cosmetic
- “yardstick_interview_sessions_interviewers_assign” added an optional parameter “notify_interviewer” cosmetic
- 3 Oct 26 +1
- Server version: 0.6.7 → 0.6.9 functional
- New tool “yardstick_people_documents_download_url” functional
- New tool “yardstick_people_documents_list” functional
- 1 Oct 26 +1
- Tool “yardstick_people_list” rewrote its description, which is the text the model reads security
- “yardstick_people_list” added an optional parameter “email” cosmetic
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 17 Oct 2026 · Probed https://api.yardstick.team/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.yardstick.team | CN=YR2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | RSA 2048 | SHA256-RSA | 53c3c5f729ac27a08243494c7d60cc28158 |
| SANs: api.yardstick.team | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.yardstick.team. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| team. | present | 38380 | 8 | Verified |
| yardstick.team. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.yardstick.team/.well-known/oauth-protected-resource/mcp", scope="people:read applications:read jobs:read interview_plans:read tasks:read tasks:write people:write"
Bearer resource_metadata="https://api.yardstick.team/.well-known/oauth-protected-resource/mcp", scope="people:read applications:read jobs:read interview_plans:read tasks:read tasks:write people:write"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Protected resource metadata
| Document | https://api.yardstick.team/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://api.yardstick.team/mcp |
| Authorisation server | https://api.yardstick.team/api-agent-auth |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.yardstick.team/mcp | Verified | 200 | |
| http (plaintext) | http://api.yardstick.team/mcp | HTTPS enforced | 308 | https://api.yardstick.team/mcp |
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 →
yardstick_talent_pool_members_remove Remove a prospect from a talent pool ~48
Remove an active prospect membership from a Talent CRM pool.
| Name | Type | Req | Description |
|---|---|---|---|
| pool_id | string | yes | – |
| prospect_id | string | yes | – |
| request_id | string | – | – |
No output schema declared.
No examples provided.
yardstick_talent_pools_create Create a talent pool ~49
Create a Talent CRM pool.
| Name | Type | Req | Description |
|---|---|---|---|
| description | – | – | – |
| idempotency_key | string | – | – |
| name | string | yes | – |
| request_id | string | – | – |
No output schema declared.
No examples provided.
yardstick_talent_pools_list List talent pools ~66
List Talent CRM pools visible to the current principal. Archived pools are excluded unless include_archived is true.
| Name | Type | Req | Description |
|---|---|---|---|
| include_archived | boolean | – | – |
| limit | integer | – | – |
| request_id | string | – | – |
| starting_after | string | – | – |
No output schema declared.
No examples provided.
yardstick_talent_pools_read Read a talent pool ~38
Read one Talent CRM pool by public id.
| Name | Type | Req | Description |
|---|---|---|---|
| pool_id | string | yes | – |
| request_id | string | – | – |
No output schema declared.
No examples provided.
yardstick_talent_pools_update Update a talent pool ~71
Update bounded Talent CRM pool fields.
| Name | Type | Req | Description |
|---|---|---|---|
| archived | boolean | – | – |
| archived_reason | – | – | – |
| description | – | – | – |
| idempotency_key | string | – | – |
| name | string | – | – |
| pool_id | string | yes | – |
| request_id | string | – | – |
No output schema declared.
No examples provided.
yardstick_talent_search Search Talent ~79
Search all authorized recruiting records by literal keywords across names, notes, activities and current parsed résumés. All words must match; PhD punctuation is normalized.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| search | string | yes | – |
| surface | string | yes | – |
No output schema declared.
No examples provided.
yardstick_tasks_deep_link Get a link that opens a task in Yardstick ~43
Create a public task deep link for a caller-supplied task id.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | – | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
yardstick_tasks_list List tasks ~43
List Yardstick tasks visible to the current principal.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| request_id | string | – | – |
| starting_after | string | – | – |
No output schema declared.
No examples provided.
yardstick_tasks_respond Answer an assigned review task ~67
Answer an assigned application or scorecard review. Recruiter questions require a note.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | string | yes | – |
| idempotency_key | string | – | – |
| note | string | – | – |
| request_id | string | – | – |
| task_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Yardstick ATS MCP server?
Yardstick ATS is a hosted endpoint at https://api.yardstick.team/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 · api.yardstick.team
claude mcp add --transport http team-yardstick-yardstick 'https://api.yardstick.team/mcp'
What is the Yardstick ATS MCP server?
Yardstick ATS is an MCP server listed in the public MCP registry as team.yardstick/yardstick. Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards. This page covers its hosted endpoint (https://api.yardstick.team/mcp).
Is the Yardstick ATS MCP server safe to use?
Yardstick ATS scores 86 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 Yardstick ATS MCP server expose?
Yardstick ATS exposes 209 tools: yardstick_identity, yardstick_tasks_list, yardstick_tasks_respond, yardstick_tasks_deep_link, yardstick_people_list, and 204 more. Their descriptions and schemas cost roughly 14,932 tokens of context every time the server is loaded.
Does the Yardstick ATS MCP server require authentication?
Yes. Yardstick ATS asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Yardstick ATS MCP server still maintained?
Yardstick ATS is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.