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 (7 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_jobs_attach_artifact ~97

Link an existing interview plan, job posting, or application to a Job. Idempotent when already linked to the same Job; conflicts when linked elsewhere. Requires jobs:write and the artifact's own write scope.

NameTypeReqDescription
artifact_idstringyes–
artifact_typestringyes–
idempotency_keystring––
job_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_jobs_close ~55

Close 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.

yardstick_jobs_create ~94

Create an internal Job container without mutating job postings, applications, or interview plans.

NameTypeReqDescription
departmentstring––
department_id–––
descriptionstring––
idempotency_keystring––
locationstring––
location_typestring––
request_idstring––
statusstring––
titlestringyes–

No output schema declared.

No examples provided.

yardstick_jobs_detach_artifact ~85

Clear the link between an artifact and a Job. Idempotent when already unlinked. Requires jobs:write and the artifact's own write scope.

NameTypeReqDescription
artifact_idstringyes–
artifact_typestringyes–
idempotency_keystring––
job_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_jobs_list ~52

List internal Job containers visible to the current principal.

NameTypeReqDescription
include_archivedboolean––
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_jobs_prospect_matches ~62

List deterministic Talent CRM prospect matches for one Job. Read-only; includes evidence, caveats, and blocked lifecycle states without outreach, conversion, import, or AI ranking.

NameTypeReqDescription
job_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_jobs_read ~35

Read one internal Job container by public id.

NameTypeReqDescription
job_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_jobs_update ~89

Update one internal Job container with schema-bound public API fields.

NameTypeReqDescription
department–––
department_id–––
description–––
idempotency_keystring––
job_idstringyes–
location–––
location_type–––
request_idstring––
statusstring––
titlestring––

No output schema declared.

No examples provided.

yardstick_opportunities_deep_link ~40

Create a public deep link for an opportunity workflow view.

NameTypeReqDescription
opportunity_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_opportunities_list ~46

List read-only opportunity workflow views visible to the current principal.

NameTypeReqDescription
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_opportunities_next_action ~41

Read the next action state for an opportunity without mutating it.

NameTypeReqDescription
opportunity_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_opportunities_read ~38

Read one read-only opportunity workflow view by public id.

NameTypeReqDescription
opportunity_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_people_create ~82

Create a person through the public Yardstick API.

NameTypeReqDescription
emailstring––
idempotency_keystring––
linkedin_urlstring––
namestring––
notesstring––
phonestring––
request_idstring––
resume_urlstring––

No output schema declared.

No examples provided.

yardstick_people_documents_download_url ~79

Mint a signed download URL for one person document. Read-only. The URL expires in 5 minutes and is a bearer link: do not log or share it. Takes per_ and pdoc_ display ids.

NameTypeReqDescription
document_idstringyes–
person_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_people_documents_list ~75

List the documents attached to a person (resumes and other files). Archived documents are excluded unless include_archived is true. Takes a per_ display id and returns pdoc_ display ids.

NameTypeReqDescription
include_archivedboolean––
person_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_people_list ~62

List people visible to the current principal. Pass email to find the exact person behind a candidate_email_conflict.

NameTypeReqDescription
emailstring––
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_people_read ~33

Read one person by public id.

NameTypeReqDescription
person_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_people_update ~82

Update one person with schema-bound public API fields.

NameTypeReqDescription
emailstring––
idempotency_keystring––
linkedin_url–––
namestring––
notes–––
person_idstringyes–
phone–––
request_idstring––
resume_url–––

No output schema declared.

No examples provided.

yardstick_pipelines_assign_to_job ~86

Assign a pipeline to a job (jobs.pipeline_template_id) or clear it with pipeline_id: null. Pipeline validated by org; job resolved by org+mode.

NameTypeReqDescription
idempotency_keystring––
job_idstringyes–
pipeline_id–yes–
request_idstring––
stage_mappingobject––

No output schema declared.

No examples provided.

yardstick_pipelines_assign_to_job_preview ~60

Preview the job's stages in use, candidate counts and suggested same-name mapping before changing its pipeline. Makes no changes.

NameTypeReqDescription
job_idstringyes–
pipeline_id–yes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_pipelines_clone ~88

Clone a pipeline and its stages. Set copy_rules to copy its workflow rules too (requires automation_rules:write). Returns rules_copied.

NameTypeReqDescription
copy_rulesboolean––
idempotency_keystring––
namestringyes–
pipeline_idstringyes–
request_idstring––
slugstringyes–

No output schema declared.

No examples provided.

yardstick_pipelines_create ~76

Create a custom pipeline template with optional inline stages. Does not affect the org default pipeline or candidate tracking.

NameTypeReqDescription
description–––
idempotency_keystring––
namestringyes–
request_idstring––
slugstringyes–
stagesarray––

No output schema declared.

No examples provided.

yardstick_pipelines_list ~38

List the organization's pipeline templates with their ordered stages. Canonical default stages are flagged canonical_locked.

NameTypeReqDescription
request_idstring––

No output schema declared.

No examples provided.

yardstick_pipelines_read ~39

Read one pipeline template and its ordered stages by public id.

NameTypeReqDescription
pipeline_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_pipelines_reorder_stages ~71

Reorder all stages of a pipeline by supplying the complete stage id order. Constraint-safe; allowed for canonical stages.

NameTypeReqDescription
idempotency_keystring––
pipeline_idstringyes–
request_idstring––
stage_idsarrayyes–

No output schema declared.

No examples provided.

yardstick_pipelines_stages_create ~103

Append (or insert at a position) a stage to a pipeline with a kind and optional approval scope.

NameTypeReqDescription
approval_scope–––
idempotency_keystring––
is_terminalboolean––
namestringyes–
pipeline_idstringyes–
positioninteger––
request_idstring––
slugstringyes–
stage_kindstringyes–

No output schema declared.

No examples provided.

yardstick_pipelines_stages_delete_bind ~79

Bind an approved pipeline-stage delete with explicit approval metadata and a matching idempotency key. Refuses while candidates remain.

NameTypeReqDescription
bindingobjectyes–
idempotency_keystring––
pipeline_idstringyes–
request_idstring––
stage_idstringyes–

No output schema declared.

No examples provided.

yardstick_pipelines_stages_delete_preview ~70

Preview deleting a pipeline stage; returns the candidate-count impact and binding fields. Canonical default stages are rejected.

NameTypeReqDescription
idempotency_keystring––
pipeline_idstringyes–
request_idstring––
stage_idstringyes–

No output schema declared.

No examples provided.

yardstick_pipelines_stages_update ~118

Edit a pipeline stage. Canonical default stages allow display-name change only; slug/stage_kind/approval_scope/is_terminal are locked.

NameTypeReqDescription
approval_scope–––
idempotency_keystring––
is_activeboolean––
is_terminalboolean––
namestring––
pipeline_idstringyes–
request_idstring––
slugstring––
stage_idstringyes–
stage_kindstring––

No output schema declared.

No examples provided.

yardstick_pipelines_update ~71

Rename, re-describe, or toggle active for one pipeline template.

NameTypeReqDescription
description–––
idempotency_keystring––
is_activeboolean––
namestring––
pipeline_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_prospect_activities_create ~84

Create a bounded internal prospect activity note or touchpoint.

NameTypeReqDescription
activity_typestring––
body–––
idempotency_keystring––
metadataobject––
occurred_atstring––
prospect_idstringyes–
request_idstring––
source_label–––

No output schema declared.

No examples provided.

yardstick_prospect_activities_list ~54

List bounded activity records for one Talent CRM prospect.

NameTypeReqDescription
limitinteger––
prospect_idstringyes–
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_prospect_imports_apply ~72

Apply an approved Prospect CRM import preview with preview_hash and explicit row decisions for advisory matches.

NameTypeReqDescription
decisionsarray––
idempotency_keystring––
import_idstringyes–
preview_hashstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_prospect_imports_dry_run ~86

Preview a structured-row Prospect CRM import. JSON rows only; no raw CSV/resume file reads, outreach, application conversion, source ranking, or silent person merge.

NameTypeReqDescription
idempotency_keystring––
metadataobject––
request_idstring––
rowsarrayyes–
source_label–––

No output schema declared.

No examples provided.

yardstick_prospect_imports_read ~43

Read one Prospect CRM import dry-run/apply batch by public id.

NameTypeReqDescription
import_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_prospects_convert_bind ~84

Bind an approved prospect conversion preview with explicit approval metadata and matching idempotency key.

NameTypeReqDescription
bindingobjectyes–
idempotency_keystring––
job_posting_idstringyes–
note–––
prospect_idstringyes–
request_idstring––
source_label–––

No output schema declared.

No examples provided.

yardstick_prospects_convert_preview ~82

Preview conversion of one Prospect into one canonical Application; bind fields are rejected and no outreach/import/merge occurs.

NameTypeReqDescription
idempotency_keystring––
job_posting_idstringyes–
note–––
prospect_idstringyes–
request_idstring––
source_label–––

No output schema declared.

No examples provided.

yardstick_prospects_create ~84

Create Talent CRM prospect relationship state for an existing person.

NameTypeReqDescription
idempotency_keystring––
last_contacted_atstring|null––
last_reviewed_atstring|null––
owner_user_id–––
person_idstringyes–
request_idstring––
source_label–––

No output schema declared.

No examples provided.

yardstick_prospects_list ~55

List active Talent CRM prospects visible to the current principal.

NameTypeReqDescription
limitinteger––
owner_user_idstring––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_prospects_outreach_create_draft ~95

Create a pending review prospect outreach email draft. Sending stays on email draft send and requires communications:send.

NameTypeReqDescription
body–––
idempotency_keystring––
job_posting_id–––
outreach_intent_key–––
personalization_instruction–––
prospect_idstringyes–
request_idstring––
subject–––

No output schema declared.

No examples provided.

yardstick_prospects_outreach_preview ~96

Preview a one-off prospect outreach draft without creating a draft, sending email, enrolling a sequence, or creating an application.

NameTypeReqDescription
body–––
idempotency_keystring––
job_posting_id–––
outreach_intent_key–––
personalization_instruction–––
prospect_idstringyes–
request_idstring––
subject–––

No output schema declared.

No examples provided.

yardstick_prospects_read ~37

Read one Talent CRM prospect by public id.

NameTypeReqDescription
prospect_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_prospects_update ~114

Update bounded Talent CRM prospect relationship fields.

NameTypeReqDescription
archived_reason–––
idempotency_keystring––
last_contacted_atstring|null––
last_reviewed_atstring|null––
next_follow_up_atstring|null––
next_follow_up_note–––
owner_user_id–––
prospect_idstringyes–
relationship_statusstring––
request_idstring––
source_label–––

No output schema declared.

No examples provided.

yardstick_reporting_search ~142

Search redacted recruiting reporting summaries through the public reporting API.

NameTypeReqDescription
job_idstring––
job_posting_idstring––
limitinteger––
minimum_sample_sizeinteger––
query_familystringyes–
request_idstring––
role_labelstring––
score_bandstring––
source_labelstring––
stagesstring––
stale_daysinteger––
starting_afterstring––
statusesstring––
window_endstringyes–
window_startstringyes–

No output schema declared.

No examples provided.

yardstick_source_links_create ~104

Create an opaque source/referral link for a published job posting. Raw source_token is returned only in the create response; reads return token_hint, and active token-bearing links also return public_url.

NameTypeReqDescription
description–––
expires_at–––
idempotency_keystring––
job_posting_idstringyes–
referrer_name–––
request_idstring––
source_labelstringyes–

No output schema declared.

No examples provided.

yardstick_source_links_disable ~58

Disable a source/referral link so its public URL no longer stamps attribution.

NameTypeReqDescription
idempotency_keystring––
reason–––
request_idstring––
source_link_idstringyes–

No output schema declared.

No examples provided.

yardstick_source_links_list ~67

List source/referral attribution links without raw token material or source quality ranking.

NameTypeReqDescription
include_disabledboolean––
job_posting_idstring––
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_source_links_read ~43

Read one source/referral attribution link by public id without raw token material.

NameTypeReqDescription
request_idstring––
source_link_idstringyes–

No output schema declared.

No examples provided.

yardstick_talent_pool_members_add ~57

Add an existing prospect to a Talent CRM pool.

NameTypeReqDescription
idempotency_keystring––
pool_idstringyes–
prospect_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_talent_pool_members_list ~54

List active prospect memberships for one Talent CRM pool.

NameTypeReqDescription
limitinteger––
pool_idstringyes–
request_idstring––
starting_afterstring––

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.