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 (5 hours ago)

Scores higher than 94% 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_access_grants_create ~105

Create a reasoned, revocable, audited access grant.

NameTypeReqDescription
artifact_classesarrayyes–
effective_atstring––
expires_atstring––
idempotency_keystring––
reasonstringyes–
request_idstring––
revocableboolean––
scopestringyes–
subject_person_idstringyes–
target_idstringyes–

No output schema declared.

No examples provided.

yardstick_access_grants_list ~45

List explicit access grants visible to the current principal.

NameTypeReqDescription
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_access_grants_read ~39

Read one explicit access grant by public id.

NameTypeReqDescription
access_grant_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_access_grants_revoke ~59

Revoke an explicit access grant with optional reason text.

NameTypeReqDescription
access_grant_idstringyes–
idempotency_keystring––
reasonstring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_application_interview_sessions_ensure ~76

Ensure an application interview session for an explicit round id.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
interview_plan_idstring––
request_idstring––
round_idstringyes–
round_titlestring––

No output schema declared.

No examples provided.

yardstick_application_interview_sessions_list ~36

List interview sessions for an application.

NameTypeReqDescription
application_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_admit_candidate ~54

Move one reviewed application to Candidates. Does not schedule interviews or send email.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_archive_bind ~70

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

NameTypeReqDescription
application_idstringyes–
bindingobjectyes–
idempotency_keystring––
reasonstring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_archive_preview ~57

Preview application archive approval requirements only; bind fields are rejected.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
reasonstring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_create ~63

Create a recruiter or agent-sourced application for an existing person and job posting.

NameTypeReqDescription
idempotency_keystring––
job_posting_idstringyes–
person_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_decide ~103

Decide on an application without a review task. Only the job's hiring manager may decide; anyone else gets application not found. Reason codes must be system codes or your organization's. Reject disqualifies the candidate.

NameTypeReqDescription
application_idstringyes–
decisionstringyes–
idempotency_keystring––
notestring––
reason_code_idsarray––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_email_decision_apply ~53

Apply an application status-change email decision with idempotency metadata.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_email_decision_preview ~58

Preview the candidate email decision for an application status change without mutating the application or drafts.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_list ~66

List application person + Job attachments visible to the current principal. Filter by --job-id to find candidates for a role.

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

No output schema declared.

No examples provided.

yardstick_applications_read ~38

Read one application person + Job attachment by public id.

NameTypeReqDescription
application_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_status_email_poc_bind ~122

Bind the fixed applications-owned status/email approval POC with explicit approval metadata and a matching idempotency key.

NameTypeReqDescription
application_idstringyes–
bindingobjectyes–
current_statusstringyes–
decisionstringyes–
email_typestringyes–
idempotency_keystring––
modestring––
personalization_instruction–––
request_idstring––
requested_sender_identity_id–––
target_statusstringyes–

No output schema declared.

No examples provided.

yardstick_applications_status_email_poc_preview ~115

Preview the fixed applications-owned Interviewing to Offer status/email approval POC without mutating status or email state.

NameTypeReqDescription
application_idstringyes–
current_statusstringyes–
decisionstringyes–
email_typestringyes–
idempotency_keystring––
modestring––
personalization_instruction–––
request_idstring––
requested_sender_identity_id–––
target_statusstringyes–

No output schema declared.

No examples provided.

yardstick_applications_transition_bind ~86

Bind an already-previewed application transition with explicit approval metadata and matching idempotency key.

NameTypeReqDescription
application_idstringyes–
bindingobjectyes–
employment_start_datestring––
idempotency_keystring––
reasonstring––
request_idstring––
statusstringyes–

No output schema declared.

No examples provided.

yardstick_applications_transition_direct ~96

Directly write a non-terminal application transition; approval-only statuses are rejected. Optionally target a configured stage by id with pipeline_stage_id (the resolved stage is reported back).

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
pipeline_stage_idstring––
reasonstring––
request_idstring––
statusstringyes–

No output schema declared.

No examples provided.

yardstick_applications_transition_preview ~108

Preview approval-required application transitions only; bind fields and direct-write targets are rejected. Optionally target a configured stage by id with pipeline_stage_id (status must match the stage's mapped status).

NameTypeReqDescription
application_idstringyes–
employment_start_datestring––
idempotency_keystring––
pipeline_stage_idstring––
reasonstring––
request_idstring––
statusstringyes–

No output schema declared.

No examples provided.

yardstick_applications_undo_candidate_admission ~84

Correct one accidental candidate admission using its current admission ID. No time limit; refused once candidate activity starts. Preserves history and excludes the corrected episode from admission reporting.

NameTypeReqDescription
application_idstringyes–
expected_admission_idstringyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_applications_update ~54

Update one application with schema-bound public API fields.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
request_idstring––
stagestring––

No output schema declared.

No examples provided.

yardstick_ats_imports_apply ~95

Apply an approved ATS import preview with a preview_hash matching the stored dry-run. Creates people/jobs/interview_plans(stub)/job_postings/applications with idempotent replay; never sends outreach, merges people, or deletes records.

NameTypeReqDescription
idempotency_keystring––
import_idstringyes–
preview_hashstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_ats_imports_dry_run ~131

Preview a structured-row ATS import of candidates, jobs, and applications (source_kind: csv). JSON rows only; no raw CSV/archive file reads, no application conversion side effects, and low-confidence stage/fuzzy matches require explicit apply decisions.

NameTypeReqDescription
applicationsarray––
candidatesarray––
idempotency_keystring––
jobsarray––
metadataobject––
request_idstring––
session_idstring––
source_kindstring––
source_label–––

No output schema declared.

No examples provided.

yardstick_ats_imports_read ~45

Read one ATS import dry-run/apply batch and its rows by public id.

NameTypeReqDescription
import_idstringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_audit_log_list ~48

List public Yardstick audit log entries visible to the current principal.

NameTypeReqDescription
limitinteger––
request_idstring––
starting_afterstring––

No output schema declared.

No examples provided.

yardstick_automation_rules_bulk ~146

Switch rules on, off or delete them. First use mode=preview with rule_ids or filter. Show the affected rules and skipped rules to the user and get explicit confirmation BEFORE applying. Then use mode=apply with only the exact rule_ids returned by preview; never reapply the filter. Pick a step rules are skipped when switching on. Warn that shared pipeline rules change for every job on that pipeline, including jobs outside the filter.

NameTypeReqDescription
actionstringyes–
filterobject––
idempotency_keystring––
modestringyes–
request_idstring––
rule_idsarray––

No output schema declared.

No examples provided.

yardstick_automation_rules_copy ~108

Copy one hiring process rule to job_ids, or one pipeline rule to pipeline_ids. Matches steps by name or kind and position, stages by name or mapped status. Unmatched copies start off and require Pick a step or Pick a stage. Copies are independent user rules.

NameTypeReqDescription
idempotency_keystring––
job_idsarray––
pipeline_idsarray––
request_idstring––
rule_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_rules_create ~167

Create a named workflow automation rule with stage or step triggers, job scope, delivery mode, timing and a typed action. Authoring executes no action.

NameTypeReqDescription
action–yes–
conditionobject––
delivery_modestring––
idempotency_keystring––
is_activeboolean––
job_id–––
job_posting_idsarray––
job_scopestring––
namestring––
needs_step_pickboolean––
pipeline_stage_id–––
pipeline_template_id–––
positioninteger––
request_idstring––
starter_key–––
timing–––
triggerstringyes–

No output schema declared.

No examples provided.

yardstick_automation_rules_delete ~56

Delete an automation rule. Plain delete (no approval preview→bind): rules are inert config, so deleting unfired config moves no candidates.

NameTypeReqDescription
request_idstring––
rule_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_rules_list ~118

List all job and pipeline rules. Filter by job_id (null for pipeline rules), department_id, pipeline_id, trigger, email or is_active. Job and department filters include inherited pipeline rules; pipeline filters also include hiring-step rules on jobs using that pipeline.

NameTypeReqDescription
department_idstring––
emailstring––
is_activeboolean––
job_idstring––
pipeline_idstring––
request_idstring––
triggerstring––

No output schema declared.

No examples provided.

yardstick_automation_rules_preview ~97

Dry-run preview: resolve the active rules + their resolved action params for a sample application entering/leaving a stage. INERT — mints no scheduling link, creates no task, sends no email; executes nothing.

NameTypeReqDescription
application_idstringyes–
idempotency_keystring––
pipeline_stage_idstringyes–
request_idstring––
triggerstringyes–

No output schema declared.

No examples provided.

yardstick_automation_rules_preview_rule ~64

Preview a saved workflow rule for a real application: recipients, sender, rendered email, scheduling links and missing prerequisites. Executes no action.

NameTypeReqDescription
application_idstringyes–
request_idstring––
rule_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_rules_read ~50

Read one automation rule by public id (its trigger, typed action, target stage, and is_active state).

NameTypeReqDescription
request_idstring––
rule_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_rules_update ~171

Edit a workflow automation rule's name, stage or step trigger, action, condition, job scope, delivery mode, timing or active state.

NameTypeReqDescription
action–––
conditionobject––
delivery_modestring––
idempotency_keystring––
is_activeboolean––
job_id–––
job_posting_idsarray––
job_scopestring––
namestring––
needs_step_pickboolean––
pipeline_stage_id–––
pipeline_template_id–––
position–––
request_idstring––
rule_idstringyes–
starter_key–––
timing–––
triggerstring––

No output schema declared.

No examples provided.

yardstick_automation_runs_list ~72

List workflow automation runs including public_state, reason, next_action, due_at and interview_session_id. Filter by application-id or rule-id. Read-only; runs are system-written.

NameTypeReqDescription
application_idstring––
request_idstring––
rule_idstring––

No output schema declared.

No examples provided.

yardstick_automation_runs_retry ~52

Try a workflow run again after fixing missing setup. Only clean refusals and active rules qualify; unknown outcomes are refused.

NameTypeReqDescription
request_idstring––
run_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_starters_apply ~80

Copy reviewed rules into a job using chosen matches; keep unmatched rules off and existing rules intact.

NameTypeReqDescription
idempotency_keystring––
job_idstringyes–
matchesobject––
request_idstring––
sourceobjectyes–
source_digeststring––

No output schema declared.

No examples provided.

yardstick_automation_starters_create ~55

Create a named organization starter from portable rule definitions.

NameTypeReqDescription
idempotency_keystring––
namestringyes–
request_idstring––
rulesarrayyes–

No output schema declared.

No examples provided.

yardstick_automation_starters_delete ~49

Delete an organization starter while keeping existing job copies.

NameTypeReqDescription
idempotency_keystring––
request_idstring––
starter_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_starters_list ~29

List your organization’s saved automation starters.

NameTypeReqDescription
request_idstring––

No output schema declared.

No examples provided.

yardstick_automation_starters_preview ~69

Preview copying a starter or job’s rules, including step and stage matches and unmatched rules.

NameTypeReqDescription
job_idstringyes–
matchesobject––
request_idstring––
sourceobjectyes–
source_digeststring––

No output schema declared.

No examples provided.

yardstick_automation_starters_rename ~57

Rename an organization starter without changing existing job copies.

NameTypeReqDescription
idempotency_keystring––
namestringyes–
request_idstring––
starter_idstringyes–

No output schema declared.

No examples provided.

yardstick_automation_starters_save_job ~59

Save a job’s automation rules as a named organization starter.

NameTypeReqDescription
idempotency_keystring––
job_idstringyes–
namestringyes–
request_idstring––

No output schema declared.

No examples provided.

yardstick_built_in_agents_configure_bind ~95

Bind an approved built-in-agent configure preview (same config plus approval metadata and a matching idempotency key). Writes only the built-in agent's declared settings keys and records one audit row.

NameTypeReqDescription
bindingobjectyes–
built_in_agent_idstringyes–
configobjectyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_built_in_agents_configure_preview ~98

Preview configuring a built-in agent (config is validated against the built-in agent's declared schema; enabled is a first-class key, so { enabled: false } is the off switch). Side-effect free; pass config via --body-json.

NameTypeReqDescription
built_in_agent_idstringyes–
configobjectyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_built_in_agents_enable_bind ~84

Bind an approved built-in-agent enable preview with explicit approval metadata and a matching idempotency key. Writes the built-in agent's declared settings home and records one audit row.

NameTypeReqDescription
bindingobjectyes–
built_in_agent_idstringyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_built_in_agents_enable_preview ~76

Preview enabling a built-in agent; returns the approval-required envelope stating exactly what starts happening (and what is never sent without you) plus binding fields. Side-effect free.

NameTypeReqDescription
built_in_agent_idstringyes–
idempotency_keystring––
request_idstring––

No output schema declared.

No examples provided.

yardstick_built_in_agents_list ~47

List the built-in-agent catalog with each built-in agent's current status, explicit defaults or disabled state, and latest work summary.

NameTypeReqDescription
request_idstring––

No output schema declared.

No examples provided.

yardstick_built_in_agents_read ~76

Read one built-in agent by catalog id (for example scorecard-chaser, nightly-screening, or interview-kit-prep): what it does, what it never does without you, current status, and latest work summary.

NameTypeReqDescription
built_in_agent_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.