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.

Yardstick ATS

REMOTE · API.YARDSTICK.TEAM

Manage hiring in Yardstick's ATS: jobs, candidates, applications, interviews, and scorecards.

+4 this week 86 Trust /100

Last scanned (6 hours ago)

Scores higher than 93% of remote servers

Reachable. Last reached 17 Oct 2026.

Category CRM and Sales

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 Security97
Transport & Reachability100
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
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.

  • 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
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 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
MCP tools · 209 exposed · ~14,932 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
yardstick_interview_plan_drafts_confirm_outcomes ~65

Confirm draft interview-plan outcomes before generating later stages.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_delete_anchors ~85

Delete behavioral-anchor entries for draft items by item id. Optional source_stage {stage: questions_and_directions, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_delete_competencies ~106

Delete draft competencies by id. Prunes each deleted competency's behavioral anchors in the same write and reports the pruned ids; the stage must keep at least one competency. Optional source_stage {stage: competencies, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_delete_questions ~83

Delete questions from one draft round by question id. Optional source_stage {stage: questions_and_directions, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_delete_rounds ~108

Delete draft interview rounds by id. Prunes each deleted round's questions and directions in the same write and reports the pruned ids; the sequence must keep at least one round. Optional source_stage {stage: interview_sequence, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_delete_skills ~87

Delete draft job skills by id; the stage must keep at least one skill. Optional source_stage {stage: skills, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_generate_anchors ~81

Generate scorecard behavioral anchors (levels 1-4) for each draft competency, or one competency when competency_id is supplied.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_generate_competencies ~65

Generate draft interview-plan competencies from confirmed outcomes.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_generate_outcomes ~87

Generate draft interview-plan outcomes from explicit role context, or pass accepted_outcomes to store caller-written outcomes verbatim with no AI generation (the deterministic draft bootstrap).

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobject––

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_generate_questions_directions ~78

Generate interview questions and interviewer/candidate directions for each draft round, or one round when round_id is supplied.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_generate_rounds ~64

Generate draft interview-plan rounds from confirmed skills.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_generate_skills ~64

Generate draft interview-plan skills from confirmed competencies.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_list ~89

List interview-plan drafts, newest first. Optional job_id narrows the list to one job and takes a job_ public display id. Use this to find an ipd_ draft id again after an interrupted builder session.

NameTypeReqDescription
job_idstring––
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_read ~88

Read one interview-plan draft in full: every stage checkpoint (outcomes, competencies, job skills, interview sequence, questions and directions), stage_versions for source_stage preconditions, status, and source metadata. Question ids are always present (question_N fallback), so edits can target them directly.

NameTypeReqDescription
draft_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_update_anchors ~113

Upsert behavioral anchors for draft items, keyed by item id with levels 1-4 — deterministic, no AI generation. Requires competencies; anchors keyed to unknown item ids are rejected by id. Optional source_stage {stage: questions_and_directions, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_update_competencies ~106

Replace draft competencies by id and/or reorder them with order (a complete permutation of resulting ids) — deterministic, no AI generation. Updating in place keeps the item id. Optional source_stage {stage: competencies, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_update_questions ~119

Replace one draft round's questions by id and/or reorder them with order (a complete permutation of that round's resulting question ids) — deterministic, no AI generation. Read the draft first: stored questions expose stable question_N ids. Optional source_stage {stage: questions_and_directions, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_update_round_directions ~105

Set one draft round's interviewer and/or candidate directions exactly as written — deterministic, no AI generation. Provide at least one of the two direction fields. Optional source_stage {stage: questions_and_directions, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_update_rounds ~120

Replace draft interview rounds by id and/or reorder them with order (a complete permutation of resulting ids) — deterministic, no AI generation. A round updated in place keeps its id, so its questions and directions are preserved (not pruned). Optional source_stage {stage: interview_sequence, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_update_skills ~98

Replace draft job skills by id and/or reorder them with order (a complete permutation of resulting ids) — deterministic, no AI generation. Optional source_stage {stage: skills, version} returns 409 when stale.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plan_drafts_validate ~52

Validate an interview-plan draft without publishing it.

NameTypeReqDescription
actionstringyes–
inputobjectyes–
request_idstring––
resourceobjectyes–

No output schema declared.

No examples provided.

yardstick_interview_plans_archive ~72

Archive one interview plan. Already-archived plans succeed without a write. A plan still attached to a job is refused — detach it from the job first.

NameTypeReqDescription
idempotency_keystring––
interview_plan_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_plans_list ~87

List published interview plans, newest first. Optional job_id narrows the list to one job and takes a job_ public display id. Use this to find an interview plan id when you only hold a job id.

NameTypeReqDescription
job_idstring––
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_interview_plans_modify_active_bind ~81

Bind an already-previewed interview-plan active modification with explicit approval metadata and matching idempotency key.

NameTypeReqDescription
actionstringyes–
bindingobjectyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobject––

No output schema declared.

No examples provided.

yardstick_interview_plans_modify_active_preview ~69

Preview interview-plan active-modification approval requirements only; bind fields are rejected.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobject––

No output schema declared.

No examples provided.

yardstick_interview_plans_publish_bind ~79

Bind an already-previewed interview-plan publish with explicit approval metadata and matching idempotency key.

NameTypeReqDescription
actionstringyes–
bindingobjectyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobject––

No output schema declared.

No examples provided.

yardstick_interview_plans_publish_preview ~66

Preview interview-plan publish approval requirements only; bind fields are rejected.

NameTypeReqDescription
actionstringyes–
idempotency_keystring––
inputobjectyes–
request_idstring––
resourceobject––

No output schema declared.

No examples provided.

yardstick_interview_plans_read ~38

Read one interview plan by public id.

NameTypeReqDescription
interview_plan_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_plans_unarchive ~78

Restore one archived interview plan. Plans that are already live succeed without a write. If the plan's job has since acquired another live plan, the restore is refused and names that plan.

NameTypeReqDescription
idempotency_keystring––
interview_plan_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_available_interviewers_list ~69

List organization members who can be assigned as interviewers, newest membership first. Use this to pick a usr_ public display id before assigning an interviewer.

NameTypeReqDescription
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_cancel ~71

Cancel a scheduled interview session, releasing the provider booking and invalidating its scheduling links.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
reasonstring––
request_idstring––
skip_providerboolean––

No output schema declared.

No examples provided.

yardstick_interview_sessions_complete ~57

Complete an interview session for an explicit interviewer.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
interviewer_user_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_interviewers_assign ~94

Assign an interviewer to an interview session. Email notification is attempted by default; set notify_interviewer to false to opt out. The response reports the safe interviewer_email outcome.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
interviewer_user_idstringyes–
notify_interviewerboolean––
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_interviewers_list ~41

List interviewers assigned to an interview session.

NameTypeReqDescription
interview_session_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_interviewers_unassign ~61

Unassign an interviewer from an interview session.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
interviewer_user_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_read ~37

Read one interview session by public id.

NameTypeReqDescription
interview_session_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_readiness ~36

Read interview-session scheduling readiness.

NameTypeReqDescription
interview_session_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_scheduling_link_generate ~51

Generate a scheduling link for an interview session.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_scorecard_submit ~83

Submit an interview-session scorecard with explicit ratings.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
interviewer_user_idstringyes–
overall_notesstring––
overall_ratinginteger––
ratingsarrayyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_interview_sessions_start ~57

Start an interview session for an explicit interviewer.

NameTypeReqDescription
idempotency_keystring––
interview_session_idstringyes–
interviewer_user_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_job_postings_archive_bind ~68

Bind an already-previewed job-posting archive with explicit approval metadata and matching idempotency key.

NameTypeReqDescription
bindingobjectyes–
idempotency_keystring––
job_posting_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_job_postings_archive_preview ~55

Preview job-posting archive approval requirements only; bind fields are rejected.

NameTypeReqDescription
idempotency_keystring––
job_posting_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_job_postings_create ~202

Create a draft job posting through the public Yardstick API.

NameTypeReqDescription
custom_questionsarray––
departmentstring––
descriptionstring––
idempotency_keystring––
interview_plan_idstringyesPublished interview plan id (ipd_...) returned by `interview-plans publish` — not an interview-plan draft id. The plan must already be attached to a Job via `jobs attach-artifact`.
locationstring––
location_countrystring–Assigned ISO 3166-1 alpha-2 country code.
location_typestring––
request_idstring––
requirementsstring––
salary_currencystring––
salary_displayboolean––
salary_maxinteger––
salary_mininteger––
slugstringyes–
titlestringyes–

No output schema declared.

No examples provided.

yardstick_job_postings_list ~44

List job postings visible to the current principal.

NameTypeReqDescription
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_job_postings_publish_bind ~68

Bind an already-previewed job-posting publish with explicit approval metadata and matching idempotency key.

NameTypeReqDescription
bindingobjectyes–
idempotency_keystring––
job_posting_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_job_postings_publish_preview ~55

Preview job-posting publish approval requirements only; bind fields are rejected.

NameTypeReqDescription
idempotency_keystring––
job_posting_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_job_postings_read ~38

Read one job posting by public id.

NameTypeReqDescription
job_posting_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_job_postings_update ~197

Update a job posting with schema-bound public API fields.

NameTypeReqDescription
custom_questionsarray––
department–––
description–––
idempotency_keystring––
interview_plan_idstring–Published interview plan id (ipd_...) returned by `interview-plans publish` — not an interview-plan draft id. The plan must already be attached to a Job via `jobs attach-artifact`.
job_posting_idstringyes–
location–––
location_country––Assigned ISO 3166-1 alpha-2 country code.
location_typestring––
request_idstring––
requirements–––
salary_currencystring––
salary_displayboolean––
salary_max–––
salary_min–––
slugstring––
titlestring––

No output schema declared.

No examples provided.

yardstick_job_postings_validate ~40

Validate a draft job posting without mutating it.

NameTypeReqDescription
job_posting_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_jobs_archive ~55

Archive one Job row only; linked job postings, applications, and interview plans are not mutated.

NameTypeReqDescription
idempotency_keystring––
job_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http team-yardstick-yardstick 'https://api.yardstick.team/mcp'
Common questions

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.