AutoApply automates job applications using a real Playwright browser. Save your profile once — name, email, phone, address, work authorization, demographics, salary — then point Claude at any job URL and it handles the rest. What it does: Opens the job application in a real Chromium browser Auto-fills all standard fields including React-Select dropdowns (Greenhouse, Lever, Ashby, Workday, LinkedIn Easy Apply) Returns unique/open-ended questions for Claude to answer with context about the role Takes screenshots after each step so you can review before submitting Remembers custom question answers (e.g. "Are you located in SF?" → Yes) so they auto-fill next time Quickstart: Call register to get an API key Call save_profile with your details Call open_job_application with any job URL Call fill_known_fields — Claude fills the form and surfaces any open questions Answer the open questions, review the screenshot, submit No browser extension or local setup required. Fully remote.

MCP readiness

B · 85/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (3513 ms); slow response -1.
Protocol revision	8/10	Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	13.55/15	28/31 probes succeeded over 30 days (90%).
Tool declaration	10/10	Lists 10 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (3513 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 78% of peers; This listing 85 · peer median 81
Latency: Faster than 53% of peers; This listing 305 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
Protocol revision −2 — Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/preetrajdeo/autoapply-mcp/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/preetrajdeo/autoapply-mcp/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://smithery.ai/servers/preetrajdeo/autoapply-mcp

Listed at (smithery)

https://smithery.ai/servers/preetrajdeo/autoapply-mcp