https://resumeoptimizerpro.com/api/mcp ↗
Resume Optimizer Pro is resume building and optimization software that enhances job applications through comprehensive analysis features. The system evaluates resumes against job descriptions to identify qualification strengths and gaps. Resume Optimizer Pro includes AI job matching analysis that presents results in understandable terms, resume streamlining capabilities for improved readability, targeted cover letter generation, and an AI resume builder that creates documents through simple question-answering. The software streamlines multi-page resumes for better clarity while maintaining ATS compatibility. Resume Optimizer Pro offers personalization options to make resumes feel authentic and includes an auto-optimization feature that intelligently fills skill gaps. The system provides detailed matching analyses that highlight strengths, partial matches, and missing qualifications to help users create optimized resumes for each role they apply for.
Resume Optimizer Pro is a remote MCP server published at resumeoptimizerpro.com. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 447 ms, placing it among the faster endpoints. It offers a narrow, focused set of 4 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
create_cover_letter — Description is cut off mid-sentence, missing critical API key requirement detailsparse_resume — API key requirement is mentioned but not clearly marked as mandatoryoptimize_resume — No explicit error handling or input validation constraints mentionedRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/resumeoptimizerpro-resume-optimizer-pro)<a href="https://mcpmetrics.io/servers/resumeoptimizerpro-resume-optimizer-pro"><img src="https://mcpmetrics.io/badge/resumeoptimizerpro/resume-optimizer-pro/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 15:07:20 | Legacy | 400 | 482 | 200 | 576 | 2025-11-25 |
| 2026-09-11 13:13:33 | Legacy | 400 | 436 | 200 | 447 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 435 | 200 | 417 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 460 | 200 | 435 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 445 | 200 | 448 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 449 | 401 | 438 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.