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.

ApplySent

REMOTE · APPLYSENT.COM

Search jobs, preview each application and apply with your OK on Workday, Greenhouse, Ashby and more.

Available components

+3 this week 83 Trust /100

Last scanned (23 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 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 Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 3552 tokens (~101/item across 35 items; 35 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management15
  • Stability check failed: schema churn in the 9 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 13 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 36 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 11 to 15.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.

  • 15 Nov 26 +1
    • Stability: 0.07 → fail ▼ security
    • Tool “get_autopilot” was removed ▼ security
    • Tool “preview_autopilot” was removed ▼ security
    • Tool “set_autopilot” was removed ▼ security
    • Tool “update_autopilot_filters” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “set_job_feedback”, which the server declares destructive security
    • Tool “fetch” rewrote its description, which is the text the model reads security
    • Tool “get_account” rewrote its description, which is the text the model reads security
    • Tool “get_application” rewrote its description, which is the text the model reads security
    • Tool “get_application_review” rewrote its description, which is the text the model reads security
    • Tool “get_job_from_link” rewrote its description, which is the text the model reads security
    • Tool “get_profile_status” rewrote its description, which is the text the model reads security
    • Tool “get_thread” rewrote its description, which is the text the model reads security
    • Tool “queue_application_for_review” rewrote its description, which is the text the model reads security
    • Tool “answer_question” rewrote its description, which is the text the model reads security
    • Tool “apply_to_job” rewrote its description, which is the text the model reads security
    • Tool “list_pending_questions” rewrote its description, which is the text the model reads security
    • Tool “preview_application” rewrote its description, which is the text the model reads security
    • Tool “regenerate_tailored_resume” rewrote its description, which is the text the model reads security
    • Tool “search” rewrote its description, which is the text the model reads security
    • Tool “regenerate_tailored_resume” is now declared destructive security
    • Schema quality: 85 → 101 ▼ functional
    • Schema quality: 85 → 102 ▼ functional
    • Tool coverage: 66% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • Server version: 1.3.0 → 1.5.0 functional
    • Server version: 1.1.0 → 1.3.0 functional
    • New tool “get_application_board” functional
    • New tool “get_application_review” functional
    • New tool “get_metrics” functional
    • New tool “get_notification_settings” functional
    • New tool “list_blocked_companies” functional
    • New tool “list_notifications” functional
    • New tool “list_saved_jobs” functional
    • New tool “mark_notification_opened” functional
    • New tool “queue_application_for_review” functional
    • New tool “set_company_blocked” functional
    • New tool “set_job_saved” functional
    • New tool “update_notification_settings” functional
    • “answer_question” reworded the description of “idempotency_key” cosmetic
    • “apply_to_job” reworded the description of “idempotency_key” cosmetic
    • “approve_tailored_resume” reworded the description of “idempotency_key” cosmetic
    • “cancel_application” reworded the description of “idempotency_key” cosmetic
    • “get_application_board” reworded the description of “limit” cosmetic
    • “get_application_board” reworded the description of “offset” cosmetic
    • “get_job_from_link” reworded the description of “idempotency_key” cosmetic
    • “get_metrics” reworded the description of “days” cosmetic
    • “list_blocked_companies” reworded the description of “limit” cosmetic
    • “list_blocked_companies” reworded the description of “offset” cosmetic
    • “list_notifications” reworded the description of “limit” cosmetic
    • “list_notifications” reworded the description of “offset” cosmetic
    • “list_saved_jobs” reworded the description of “limit” cosmetic
    • “list_saved_jobs” reworded the description of “offset” cosmetic
    • “list_saved_jobs” reworded the description of “sort” cosmetic
    • “mark_notification_opened” reworded the description of “idempotency_key” cosmetic
    • “preview_tailored_resume” reworded the description of “idempotency_key” cosmetic
    • “queue_application_for_review” reworded the description of “idempotency_key” cosmetic
    • “regenerate_tailored_resume” reworded the description of “idempotency_key” cosmetic
    • “search_jobs” reworded the description of “salary_currency” cosmetic
    • “set_company_blocked” reworded the description of “idempotency_key” cosmetic
    • “set_job_feedback” reworded the description of “idempotency_key” cosmetic
    • “set_job_feedback” reworded the description of “signal” cosmetic
    • “set_job_saved” reworded the description of “idempotency_key” cosmetic
    • “update_notification_settings” reworded the description of “idempotency_key” cosmetic
    • “answer_question” reworded the description of “batch_id” cosmetic
    • “answer_question” reworded the description of “question_index” cosmetic
    • “fetch” reworded the description of “id” cosmetic
    • “search_jobs” reworded the description of “nationals_only” cosmetic
    • “get_jobs” reworded the description of “job_ids” cosmetic
    • “get_message” reworded the description of “message_id” cosmetic
    • “get_thread” reworded the description of “message_id” cosmetic
    • “list_applications” reworded the description of “limit” cosmetic
    • “list_applications” reworded the description of “offset” cosmetic
    • “list_applications” reworded the description of “started_by_this_client” cosmetic
    • “list_applications” reworded the description of “status” cosmetic
    • “list_inbox” reworded the description of “category” cosmetic
    • “list_inbox” reworded the description of “limit” cosmetic
    • “list_pending_questions” reworded the description of “limit” cosmetic
    • “list_pending_questions” reworded the description of “offset” cosmetic
    • “search_jobs” reworded the description of “city” cosmetic
    • “search_jobs” reworded the description of “include_applied” cosmetic
    • “search_jobs” reworded the description of “limit” cosmetic
    • “search_jobs” reworded the description of “min_salary” cosmetic
    • “search_jobs” reworded the description of “min_score” cosmetic
    • “search_jobs” reworded the description of “offset” cosmetic
    • “search_jobs” reworded the description of “seniority” cosmetic
    • “search_jobs” reworded the description of “sort” cosmetic
    • “search_jobs” reworded the description of “workplace” cosmetic
    • Tool “fetch” changed its title: Read a job (citations) → Fetch a job's text cosmetic
    • Tool “get_account” changed its title: Read plan and usage → Read application usage cosmetic
    • Tool “get_jobs” changed its title: Read several jobs → Read jobs cosmetic
    • Tool “regenerate_tailored_resume” changed its title: Tailor a résumé again → Regenerate tailored résumé cosmetic
    • Tool “search” changed its title: Search jobs (citations) → Search jobs cosmetic
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 +40
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 100 functional
    • First check of Tool coverage: 66 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 11 Nov 26 39

    First indexed and scored.

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 21 Nov 2026 · Probed https://applysent.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=applysent.com CN=YE2,O=Let's Encrypt,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA384 6beac1be4b8674929702069274cae3b027c
SANs: *.applysent.com, applysent.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of applysent.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
applysent.com. No DS 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://applysent.com/.well-known/oauth-protected-resource/api/mcp", scope="jobs:read jobs:write applications:read inbox:read settings:read settings:write apply profile:write"

Bearer resource_metadata="https://applysent.com/.well-known/oauth-protected-resource/api/mcp", scope="jobs:read jobs:write applications:read inbox:read settings:read settings:write apply profile:write"
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; connect-src 'self' https://*.ingest.sentry.io https://*.ingest.us.sentry.io https://*.ingest.de.sentry.io https://accounts.google.com https://static.cloudflareinsights.com https://cloudflareinsights.com; worker-src 'self' blob: data:; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; object-src 'none'; img-src 'self' data: blob: https://www.google.com https://*.gstatic.com https://cdn.brandfetch.io; script-src 'self' 'unsafe-inline' https://accounts.google.com https://static.cloudflareinsights.com; frame-src https://accounts.google.com; style-src 'self' 'unsafe-inline' https://accounts.google.com/gsi/style; font-src 'self' data:
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Protected resource metadata

Document https://applysent.com/.well-known/oauth-protected-resource/api/mcp
Retrieved Yes
Resource https://applysent.com/api/mcp
Authorisation server https://applysent.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://applysent.com/api/mcp Verified 200
http (plaintext) http://applysent.com/api/mcp HTTPS enforced 301 https://applysent.com/api/mcp
MCP tools · 35 exposed · ~3,457 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
answer_question ~150

Saves the given answer to one open question and applies it to every application asking it; those applications then continue. The answer is stored exactly as given, as the user's own words or the option they chose. Returns the applications answered and those now ready to continue. Sends nothing.

NameTypeReqDescription
answerstringyesThe user's own answer, or the exact option they picked.
batch_idintegeryesThe question group from list_pending_questions the question belongs to.
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
question_indexintegeryesWhich question of that group to answer, as list_pending_questions numbers it.
NameTypeReqDescription
answeredarrayyesThe applications the answer was applied to.
bankedinteger–How many reusable answers the answer was stored as.
profile_fieldstring|null–The profile field the answer was saved to, when it is a fact the profile keeps.
readyarrayyesThe applications left with nothing to ask, now ready to go on.

No examples provided.

apply_to_job ~174

Sends one real application to one job on the employer's site, only after the user said yes to this job in the conversation, and uses one application from the account's allowance. Requires the confirmation_token preview_application returned for this job. A job already applied to, or sent with an uncertain outcome, is never sent again. A posting held on an employer account that is connected now is woken and reported as applying (status queued, no hold, poll suggested) instead of returning the old hold.

NameTypeReqDescription
confirmation_tokenstringyesFrom preview_application for this job.
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
answer_batchesarray–The open question batches this application waits on.
answersarray–The answers this application sends.
apply_urlstring–The employer's posting URL.
companystring|null–The employer's name, when the ledger has it.
holdobject|null–What the employer waits on before this application can go on, when it waits on something ApplySent recognizes.
idstringyesThe job id of this application.
missing_prerequisitesarray–What still stops this application from being sent, in words.
not_sent_reasonstring|null–Why a failed application was not sent, when ApplySent refused it.
poll_after_secondsinteger|null–Seconds to wait before reading this application again; null when nothing will change by itself.
receiptobject|null–The employer's confirmation of this application, or null when none was recorded.
recorded_atstring|null–When the user started this application, ISO 8601.
retry_atstring|null–When ApplySent retries a blocked application, ISO 8601.
reviewobject–How far the review of this application has come.
review_reasonsarray–Why the application waits for the user's review.
stagestring|null–The hiring stage the employer's messages established (applied, interview, offer, rejected), when known.
statusstringyesThe application's ledger status, e.g. queued, submitted, uncertain or failed.
stepstringyesWhere the application stands in ApplySent's pipeline, e.g. preparing_application, needs_answer or sent.
suggested_next_toolstringyesThe tool that answers what this application needs next.
titlestring|null–The posting's title, when the ledger has it.
uncertainbooleanyesTrue when the send went out without a confirmed receipt; ApplySent never sends such a job again.
waitingstring|null–Set while the background worker is on this application right now.

No examples provided.

approve_tailored_resume ~105

Marks the previewed tailored résumé (by its resume_sha256) as the one to send with this job's application. Sends nothing.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
resume_sha256stringyesresume_sha256 from preview_tailored_resume.
NameTypeReqDescription
approvedbooleanyesTrue once the résumé is the one to send.
job_idstringyesThe job the résumé is approved for.
resume_sha256stringyesThe approved résumé's hash.

No examples provided.

cancel_application ~87

Stops an application whose send has not started; it can then never be sent and its open questions are withdrawn. Refused once sending started.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
answer_batchesarray–The open question batches this application waits on.
answersarray–The answers this application sends.
apply_urlstring–The employer's posting URL.
companystring|null–The employer's name, when the ledger has it.
holdobject|null–What the employer waits on before this application can go on, when it waits on something ApplySent recognizes.
idstringyesThe job id of this application.
missing_prerequisitesarray–What still stops this application from being sent, in words.
not_sent_reasonstring|null–Why a failed application was not sent, when ApplySent refused it.
poll_after_secondsinteger|null–Seconds to wait before reading this application again; null when nothing will change by itself.
receiptobject|null–The employer's confirmation of this application, or null when none was recorded.
recorded_atstring|null–When the user started this application, ISO 8601.
retry_atstring|null–When ApplySent retries a blocked application, ISO 8601.
reviewobject–How far the review of this application has come.
review_reasonsarray–Why the application waits for the user's review.
stagestring|null–The hiring stage the employer's messages established (applied, interview, offer, rejected), when known.
statusstringyesThe application's ledger status, e.g. queued, submitted, uncertain or failed.
stepstringyesWhere the application stands in ApplySent's pipeline, e.g. preparing_application, needs_answer or sent.
suggested_next_toolstringyesThe tool that answers what this application needs next.
titlestring|null–The posting's title, when the ledger has it.
uncertainbooleanyesTrue when the send went out without a confirmed receipt; ApplySent never sends such a job again.
waitingstring|null–Set while the background worker is on this application right now.

No examples provided.

fetch ~45

The full text of one job from search, with its posting URL and match details, for citing it. Reads only.

NameTypeReqDescription
idstringyesA job id from a search result.
NameTypeReqDescription
idstringyesThe job id.
metadataobject–The posting's facts beside its text.
textstringyesThe posting's full text.
titlestringyesThe posting's title and employer in one line.
urlstringyesThe employer's posting URL, for citing it.

No examples provided.

get_account ~34

How many applications the account has left and has sent today (or unlimited), and anything stopping applications from being sent. Reads only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
applicationsobjectyesThe allowance the sender counts against.
send_blockersarrayyesEverything that stops applications from being sent now, in words.

No examples provided.

get_application ~73

One application: status and step (blocked with its reason and retry_at while ApplySent waits to retry), receipt, the answers sent, any open questions, suggested_next_tool and poll_after_seconds. Reads only.

NameTypeReqDescription
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
answer_batchesarray–The open question batches this application waits on.
answersarray–The answers this application sends.
apply_urlstring–The employer's posting URL.
companystring|null–The employer's name, when the ledger has it.
holdobject|null–What the employer waits on before this application can go on, when it waits on something ApplySent recognizes.
idstringyesThe job id of this application.
missing_prerequisitesarray–What still stops this application from being sent, in words.
not_sent_reasonstring|null–Why a failed application was not sent, when ApplySent refused it.
poll_after_secondsinteger|null–Seconds to wait before reading this application again; null when nothing will change by itself.
receiptobject|null–The employer's confirmation of this application, or null when none was recorded.
recorded_atstring|null–When the user started this application, ISO 8601.
retry_atstring|null–When ApplySent retries a blocked application, ISO 8601.
reviewobject–How far the review of this application has come.
review_reasonsarray–Why the application waits for the user's review.
stagestring|null–The hiring stage the employer's messages established (applied, interview, offer, rejected), when known.
statusstringyesThe application's ledger status, e.g. queued, submitted, uncertain or failed.
stepstringyesWhere the application stands in ApplySent's pipeline, e.g. preparing_application, needs_answer or sent.
suggested_next_toolstringyesThe tool that answers what this application needs next.
titlestring|null–The posting's title, when the ledger has it.
uncertainbooleanyesTrue when the send went out without a confirmed receipt; ApplySent never sends such a job again.
waitingstring|null–Set while the background worker is on this application right now.

No examples provided.

get_application_board ~183

The Applications board under its filters: how many applications stand in each bucket, how many are being worked on now, and light rows of one bucket's page or of the first rows of every bucket, work running now first. Paging with offset needs bucket. Reads only.

NameTypeReqDescription
beforestring–Only applications recorded before this ISO date.
bucketstring–One bucket to page through; leave it out for the first rows of every bucket.
companystring–Only applications at this employer, matched without case.
limitinteger–Rows per bucket.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
qstring–Words to match in the job title or employer.
sincestring–Only applications recorded on or after this ISO date.
NameTypeReqDescription
bucketstring|nullyesThe column paged through, or null when every column's first rows came back.
countsobjectyesHow many applications stand in each board column, under the filters.
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
filtersobjectyesThe filters this page was read under.
offsetintegeryesThe offset this page starts at.
rowsarrayyesThe light rows of one column's page, or the first rows of every column.
workingintegeryesHow many applications are being worked on right now.

No examples provided.

get_application_receipt ~67

The employer's confirmation evidence for one application: the receipt, the answers sent, the proof files and the confirmation screenshot as an image when one was captured. Reads only.

NameTypeReqDescription
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
answers_sentarrayyesThe answers this application sends.
companystring–The employer's name.
job_idstringyesThe job id of this application.
proofarrayyesThe proof files the send left behind.
receiptobject|nullyesThe employer's confirmation of this application, or null when none was recorded.
screenshotstring–The name of the proof image also returned as an image part, when one was captured.
statusstringyesThe application's ledger status.
titlestring–The posting's title.
uncertainbooleanyesTrue when the send went out without a confirmed receipt.

No examples provided.

get_application_review ~142

Everything needed to review one application before it is sent: the packet revision and its approval, the documents (name, format, size, hash) and form answers it would send, open employer questions, every blocker in words, field errors and the public timeline. Use it when the user wants to check or fix an application that waits for review; use get_application for status alone and get_application_receipt for proof after sending. Pass job_id. Reads only: approving, answering and sending are done by answer_question, preview_application and apply_to_job.

NameTypeReqDescription
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
answersarrayyesThe answers this application sends.
blockersarrayyesEverything that stops this application from being sent, in words.
companystring–The employer's name.
digeststring|null–The current packet's hash, when one exists.
eventsarray–The public timeline steps, oldest first.
field_errorsobject–Form fields whose answers the review rejected, by field name.
job_idstringyesThe job id of this application.
packetobject|nullyesThe packet the application would send, or null when none was built.
questionsarrayyesThe open question batches this application waits on.
review_availablebooleanyesTrue when the application has a packet the user may review.
review_reasonsarray–Why the application waits for the user's review.
revisioninteger|null–The current packet revision, when one exists.
stagestring|null–The hiring stage the employer's messages established, when known.
statusstringyesThe application's ledger status.
stepstring|null–Where the application stands in ApplySent's pipeline.
titlestring–The posting's title.
uncertainbooleanyesTrue when the send went out without a confirmed receipt.

No examples provided.

get_job ~50

The full posting, the match assessment against the user, and any application status. Reads only.

NameTypeReqDescription
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
application_statusstring|null–The application's ledger status when the user applied to this job, else null.
apply_supportedboolean–Whether ApplySent can fill and submit this posting's form by itself.
apply_urlstring–The employer's posting URL, where the application is filled.
citystring|null–City the posting is in.
companystring–The employer's name.
countrystring|null–Country the posting is in, as the catalogue recorded it.
descriptionstringyesThe posting's text with whitespace collapsed, cut to the tool's length.
description_truncatedboolean–True when the posting's text was cut.
factsobject–Facts the catalogue derived from the posting; a key is absent when the catalogue established nothing for it.
idstringyesThe job id the other job tools take.
matchobjectyesThe assessment of this job against the user's résumé, targets and eligibility.
posted_atstring|null–When the posting went up, ISO 8601 in UTC, when the catalogue knows it.
providerstring–The employer's hiring system the posting came from, e.g. workday, greenhouse or ashby.
salaryobject|null–The pay the posting states, or null when it states none.
savedboolean–Whether the user saved this job.
titlestring–The posting's title as the employer states it.

No examples provided.

get_job_from_link ~98

Reads the posting at an employer or job-board link and returns the full posting text, the match assessment against the user and the job id, keeping it in the user's saved jobs. Fetches the employer's page; applies to nothing.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
urlstringyesThe posting URL the user shared.
NameTypeReqDescription
application_statusstring|null–The application's ledger status when the user applied to this job, else null.
apply_supportedboolean–Whether ApplySent can fill and submit this posting's form by itself.
apply_urlstring–The employer's posting URL, where the application is filled.
citystring|null–City the posting is in.
companystring–The employer's name.
countrystring|null–Country the posting is in, as the catalogue recorded it.
descriptionstringyesThe posting's text with whitespace collapsed, cut to the tool's length.
description_truncatedboolean–True when the posting's text was cut.
factsobject–Facts the catalogue derived from the posting; a key is absent when the catalogue established nothing for it.
idstringyesThe job id the other job tools take.
matchobjectyesThe assessment of this job against the user's résumé, targets and eligibility.
posted_atstring|null–When the posting went up, ISO 8601 in UTC, when the catalogue knows it.
providerstring–The employer's hiring system the posting came from, e.g. workday, greenhouse or ashby.
salaryobject|null–The pay the posting states, or null when it states none.
savedboolean–Whether the user saved this job.
titlestring–The posting's title as the employer states it.

No examples provided.

get_jobs ~63

Up to 20 postings by id with their match assessments, descriptions shortened; ids not found come back in missing. Reads only.

NameTypeReqDescription
job_idsarrayyesJob ids from search_jobs, get_job_from_link or list_applications; a repeated id is read once.
NameTypeReqDescription
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
jobsarrayyesThe requested postings that are in this account, in the order asked.
missingarrayyesThe requested ids this account does not hold.

No examples provided.

get_message ~40

One email from the application inbox with its text and the application it belongs to. Reads only.

NameTypeReqDescription
message_id–yesA message id from list_inbox.
NameTypeReqDescription
applicationobject|null–The application this email belongs to, or null when it belongs to none.
bodystringyesThe email's text, cut to the tool's length.
body_truncatedboolean–True when the email's text was cut.
categorystring–What the email is, as classified: interview, rejection, assessment, offer, recruiter, verification, application_confirmation or unknown.
idintegeryesThe message id get_message and get_thread take.
received_atstring–When the email arrived, ISO 8601.
senderstring–The sender's address.
subjectstring–The email's subject as received.

No examples provided.

get_metrics ~64

Receipt-confirmed application metrics for a window of UTC days: confirmations, their daily and rolling 30-day counts, and the rolling interview rate; internal AI spend is left out. Reads only.

NameTypeReqDescription
daysinteger–How many UTC days back to count, ending today.
NameTypeReqDescription
confirmed_countintegeryesApplications confirmed by a receipt inside the window.
confirmed_per_daynumber–Confirmed applications per day across the window.
daily_confirmedobject–Confirmed applications by UTC date inside the window.
daysintegeryesHow many UTC days back the window counts.
receipts_by_kindobject–Confirmations by receipt kind.
receipts_by_providerobject–Confirmations by hiring system.
rolling_30d_confirmedinteger–Applications confirmed in the last 30 days.
rolling_30d_interview_ratenumber|null–Interviews per confirmed application over those 30 days, or null when nothing was confirmed.
rolling_30d_interviewsinteger–Applications that reached interview or offer in the last 30 days.
uncertain_countintegeryesApplications sent without a confirmed receipt, account-wide now.

No examples provided.

get_notification_settings ~31

The user's push categories and email and Telegram notification preferences, as the app and site show them. Reads only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
notificationsobjectyesThe email and Telegram notification preferences.
pushobjectyesThe push categories, as the app and site show them.

No examples provided.

get_profile_status ~42

What the user's ApplySent profile still needs before applications can go out, and how many employer questions wait. Reports what is missing, not the values. Reads only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
missingarrayyesWhat the profile still needs, in words.
pending_questionsinteger–How many employer questions wait on the user.
readybooleanyesTrue when the profile has everything an application needs.
tailor_resumeboolean–Whether the user asked for a résumé tailored to each job.
targetsobject–What the user targets, as the profile records it.

No examples provided.

get_thread ~77

The conversation around one email: every email of the same application, or of the same sender and subject when it belongs to none, oldest first. Each message gives its id, sender, subject, received time, category and the application it belongs to, without bodies. Reads only.

NameTypeReqDescription
message_id–yesA message id from list_inbox.
NameTypeReqDescription
messagesarrayyesEvery email of the conversation, oldest first, without bodies.

No examples provided.

list_applications ~148

The user's applications, newest first, with status and the employer's receipt when sent. status needs_you keeps those waiting on the user, uncertain those sent without a confirmed receipt (never sent again); started_by_this_client keeps those this assistant started. Reads only.

NameTypeReqDescription
limitinteger–How many applications to return.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
started_by_this_clientboolean–Only applications this assistant started; leave it out for every application.
statusstring–Which applications to list: every one, those waiting on the user, or those sent without a confirmed receipt.
NameTypeReqDescription
applicationsarrayyesThe page of applications, newest first.
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
morebooleanyesTrue when later pages hold more applications.
offsetintegeryesThe offset this page starts at.

No examples provided.

list_blocked_companies ~74

The employers the user excluded from matches, by name, with when each was excluded; a page at a time. Reads only.

NameTypeReqDescription
limitinteger–How many companies to return.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
NameTypeReqDescription
companiesarrayyesThe page of excluded employers, by name.
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
morebooleanyesTrue when later pages hold more employers.
offsetintegeryesThe offset this page starts at.
totalintegeryesHow many employers the user excluded.

No examples provided.

list_inbox ~81

Employer emails in the user's application inbox, newest first, classified (interview, rejection, verification, assessment...) and linked to the application they belong to. Reads only; nothing is sent.

NameTypeReqDescription
categorystring–Only emails the classifier put in this category; leave it out for every category.
limitinteger–How many emails to return.
NameTypeReqDescription
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
messagesarrayyesThe page of employer emails, newest first.

No examples provided.

list_notifications ~70

The user's notification feed, newest first, a page at a time, with coverage saying what was left out. Reads only.

NameTypeReqDescription
limitinteger–How many notifications to return.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
NameTypeReqDescription
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
morebooleanyesTrue when later pages hold more notifications.
notificationsarrayyesThe page of notifications, newest first.
offsetintegeryesThe offset this page starts at.

No examples provided.

list_pending_questions ~100

Questions employers asked that only the user can answer; the applications asking them wait. Each is asked once and its answer is reused for every application asking it. Each group gives its batch_id, the application, its questions and how many applications ask each. Reads only.

NameTypeReqDescription
limitinteger–How many question groups to return.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
NameTypeReqDescription
applications_waitinginteger–How many applications wait on those answers.
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
groupsarrayyesThe page of question groups, widest reach first.
totalintegeryesHow many question groups wait on the user.

No examples provided.

list_saved_jobs ~94

The jobs the user saved, with each one's match assessment, best match first or newest first, a page at a time. Reads only.

NameTypeReqDescription
limitinteger–How many saved jobs to return.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
sortstring–Order of the page: best match first, or newest first.
NameTypeReqDescription
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
jobsarrayyesThe page of saved jobs, best match first or newest first as asked.
morebooleanyesTrue when later pages hold more saved jobs.
offsetintegeryesThe offset this page starts at.
totalintegeryesHow many jobs the user saved.

No examples provided.

mark_notification_opened ~66

Records the first opening of a notification. Repeating it changes nothing.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
notification_idintegeryesA notification id from list_notifications.
NameTypeReqDescription
idintegeryesThe notification that was opened.
openedbooleanyesTrue once the opening is recorded; a repeat leaves it true.

No examples provided.

preview_application ~91

Shows what applying to one job would send and use, and returns a single-use confirmation_token for apply_to_job. The user must review this preview and say yes in the conversation before apply_to_job; the token works for this job and this connection only and expires after 10 minutes. Sends nothing.

NameTypeReqDescription
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
confirmation_tokenstringyesThe single-use token apply_to_job takes for this job.
expires_inintegeryesHow many seconds the token stays valid.
jobobjectyesThe job the application would go to.
matchobject–The assessment of the job against the user.
resumestring–Which résumé the application would attach, in words.
sendsstring–What ApplySent would fill and submit, in words.
uses_applicationsinteger–How many applications this send draws from the allowance.

No examples provided.

preview_tailored_resume ~104

The résumé tailored to one job, as the PDF an application would attach, with what changed against the saved résumé. Made once with an AI model from facts already in the résumé, then reused; nothing is sent.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
approvedbooleanyesWhether this résumé is the one approved to send with the application.
changesobject–What changed against the saved résumé.
companystring–The employer's name.
job_idstringyesThe job id the résumé is tailored to.
notesarray–What the tailoring did and left out, as it reported it.
resume_sha256stringyesThe tailored PDF's hash; approve_tailored_resume takes it.
titlestring–The posting's title.

No examples provided.

queue_application_for_review ~107

Prepares one application for the user to review and approve in ApplySent; it is sent only after the user approves it there. Sends nothing. Refuses if a send is already in progress or the posting has already been sent.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
answer_batchesarray–The open question batches this application waits on.
answersarray–The answers this application sends.
apply_urlstring–The employer's posting URL.
companystring|null–The employer's name, when the ledger has it.
holdobject|null–What the employer waits on before this application can go on, when it waits on something ApplySent recognizes.
idstringyesThe job id of this application.
missing_prerequisitesarray–What still stops this application from being sent, in words.
not_sent_reasonstring|null–Why a failed application was not sent, when ApplySent refused it.
poll_after_secondsinteger|null–Seconds to wait before reading this application again; null when nothing will change by itself.
receiptobject|null–The employer's confirmation of this application, or null when none was recorded.
recorded_atstring|null–When the user started this application, ISO 8601.
retry_atstring|null–When ApplySent retries a blocked application, ISO 8601.
reviewobject–How far the review of this application has come.
review_reasonsarray–Why the application waits for the user's review.
stagestring|null–The hiring stage the employer's messages established (applied, interview, offer, rejected), when known.
statusstringyesThe application's ledger status, e.g. queued, submitted, uncertain or failed.
stepstringyesWhere the application stands in ApplySent's pipeline, e.g. preparing_application, needs_answer or sent.
suggested_next_toolstringyesThe tool that answers what this application needs next.
titlestring|null–The posting's title, when the ledger has it.
uncertainbooleanyesTrue when the send went out without a confirmed receipt; ApplySent never sends such a job again.
waitingstring|null–Set while the background worker is on this application right now.

No examples provided.

regenerate_tailored_resume ~106

Discards the job's tailored résumé and its approval, then tailors it again with an AI model from the saved résumé, and returns the new résumé with what changed. Refused once the application was sent or is sending.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
NameTypeReqDescription
approvedbooleanyesWhether this résumé is the one approved to send with the application.
changesobject–What changed against the saved résumé.
companystring–The employer's name.
job_idstringyesThe job id the résumé is tailored to.
notesarray–What the tailoring did and left out, as it reported it.
resume_sha256stringyesThe tailored PDF's hash; approve_tailored_resume takes it.
titlestring–The posting's title.

No examples provided.

search ~65

The same matching search as search_jobs, best match first, as citable results: each job's id, its title and employer, and the employer's posting URL; fetch reads one in full. Reads only.

NameTypeReqDescription
querystringyesWords in the title, employer or description.
NameTypeReqDescription
resultsarrayyesThe matching jobs as citable results, best match first.

No examples provided.

search_jobs ~426

Search the jobs that match the user's résumé and filters, best match first, a page at a time. Leaves out jobs already applied to unless include_applied is true, and postings open only to nationals unless the profile lists a nationality or nationals_only says otherwise. Reads only.

NameTypeReqDescription
citystring–City the posting is in, e.g. "Dubai" or "London".
countrystring–Country name or ISO code, e.g. "US", "United Kingdom", "AE".
employment_typestring–e.g. full_time, part_time, contract.
include_appliedboolean–Include jobs already applied to; they are left out otherwise.
limitinteger–How many jobs to return.
min_salarynumber–Only jobs stating pay of at least this; a job with no stated salary is left out.
min_scoreinteger–Only jobs the résumé matches at least this well; leave it out for no floor.
nationals_onlystring–Whether postings open only to a country's nationals are left out, included, or the only ones kept; leaving it out excludes them unless the profile lists a nationality.
offsetinteger–Rows to skip for the next page: the previous page's coverage names the offset to pass.
posted_sincestring–ISO date; only jobs posted on or after it. Jobs with no known posting date are left out.
querystring–Words in the title, employer or description.
salary_currencystring–ISO code of the currency the stated pay must be in: with min_salary the floor is read in that currency, on its own it keeps the jobs that state pay in it.
senioritystring–Seniority as postings state it, e.g. "senior", "junior", "lead".
sortstring–Order of the page: best match first, or newest posting first.
workplacestring–Where the work is done; leave it out for any.
NameTypeReqDescription
coverageobjectyesWhat this page covers, so the assistant can say honestly what it read.
jobsarrayyesThe page of matching jobs, best match first or newest first as asked.
morebooleanyesTrue when later pages hold more jobs.
offsetintegeryesThe offset this page starts at.
totalintegeryesHow many jobs the filters match in all.

No examples provided.

set_company_blocked ~92

Excludes one employer from the user's matches, or removes its exclusion, and returns the full list of excluded employers.

NameTypeReqDescription
blockedbooleanyestrue excludes the company from matches, false restores it.
companystringyesThe employer name as postings state it.
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
NameTypeReqDescription
blockedbooleanyesTrue when the employer is now excluded, false when it was restored.
changedbooleanyesTrue when this call changed the list, false when it already stood that way.
companiesarrayyesEvery employer the user excludes now.
companystringyesThe employer name the exclusion was recorded for.

No examples provided.

set_job_feedback ~118

Skips a job or restores a skipped job. Skipping cancels a swipe only if it has not yet been queued; it does not cancel an already queued application.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
signalstringyesWhether the user is not interested in this job, or wants an earlier skip taken back.
NameTypeReqDescription
job_idstringyesThe job the feedback was recorded for.
signalstringyesThe signal stored: not_interested, or undo once the skip was taken back.
skippedbooleanyesTrue while the job is skipped.

No examples provided.

set_job_saved ~97

Saves one job to the user's saved jobs, or removes it, and returns the job with its match assessment.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
job_idstringyesA job id from search_jobs, get_job_from_link or list_applications.
savedbooleanyestrue saves the job, false removes it.
NameTypeReqDescription
apply_supportedboolean–Whether ApplySent can fill and submit this posting's form by itself.
apply_urlstring–The employer's posting URL, where the application is filled.
citystring|null–City the posting is in.
companystring–The employer's name.
countrystring|null–Country the posting is in, as the catalogue recorded it.
excerptstring–The start of the posting's text, plain, for a list row.
idstringyesThe job id the other job tools take.
matchobjectyesThe assessment of this job against the user's résumé, targets and eligibility.
posted_atstring|null–When the posting went up, ISO 8601 in UTC, when the catalogue knows it.
providerstring–The employer's hiring system the posting came from, e.g. workday, greenhouse or ashby.
salaryobject|null–The pay the posting states, or null when it states none.
savedboolean–Whether the user saved this job.
titlestring–The posting's title as the employer states it.

No examples provided.

update_notification_settings ~93

Changes only the given notification preferences and returns the saved settings.

NameTypeReqDescription
idempotency_keystring–Repeating a call with the same key and arguments returns its first result instead of acting again.
notificationsobject–Email and Telegram preferences to change; leave any out to keep it as it is.
pushobject–Push categories to change; leave any out to keep it as it is.
NameTypeReqDescription
notificationsobjectyesThe email and Telegram notification preferences.
pushobjectyesThe push categories, as the app and site show them.

No examples provided.

Install

How do I install the ApplySent MCP server?

ApplySent is a hosted endpoint at https://applysent.com/api/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 · applysent.com

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

What is the ApplySent MCP server?

ApplySent is an MCP server listed in the public MCP registry as com.applysent/applysent. Search jobs, preview each application and apply with your OK on Workday, Greenhouse, Ashby and more. This page covers its hosted endpoint (https://applysent.com/api/mcp).

Is the ApplySent MCP server safe to use?

ApplySent scores 83 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 ApplySent MCP server expose?

ApplySent exposes 35 tools: search_jobs, list_saved_jobs, set_job_saved, set_job_feedback, list_blocked_companies, and 30 more. Their descriptions and schemas cost roughly 3,457 tokens of context every time the server is loaded.

Does the ApplySent MCP server require authentication?

Yes. ApplySent 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 ApplySent MCP server still maintained?

ApplySent is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ApplySent MCP server?

VerifyMCP ran 13 checks on ApplySent, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.