Skip to main content
Glama

Server Details

CareerProof MCP gives AI agents direct access to a professional-grade career and workforce intelligence platform. Two namespaces: atlas_* for HR/TA teams (candidate evaluation, batch shortlisting, competency scoring, interview generation, JD analysis, custom eval frameworks, research reports) and ceevee_* for professionals (CV optimization, career positioning, salary intelligence, market reports). Backed by RAG knowledge from 50+ premium research sources (McKinsey, BCG, HBR, Gartner, WEF)

Ownership verified
Status
Unhealthy
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.9/5.0
Disambiguation4/5

Most tools have distinct purposes with clear descriptions, but the large number of similar analysis tools (atlas_start_gem_analysis, atlas_start_fit_match, atlas_start_fit_rank, etc.) could cause some confusion for an agent.

Naming Consistency3/5

Tools follow a verb_noun pattern with prefixes 'atlas_' and 'ceevee_', but inconsistencies exist such as 'start' vs 'create' vs 'get', and two tools break the pattern (careerproof_task_status, careerproof_task_result).

Tool Count2/5

With 71 tools, the server is severely over-scoped. Many tools for polling and listing could be combined, and the high count overwhelms the user and agent.

Completeness4/5

The tool surface is extensive and covers core workflows for hiring and CV optimization, though some CRUD operations (e.g., delete candidate or JD) are missing.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 6 tool updates
    • Addedatlas_download_reformatted_cv
    • Addedatlas_get_cv_template
    • Changedatlas_get_jd_fit_results3 fields changed
      • addedInput schema / properties / batch_id
        Added value: +{
        +  "description": "Scope results to a specific batch (from atlas_start_jd_fit_batch). Strongly recommended whenever you have a batch_id available — eliminates duplicates from historical runs.",
        +  "type": "number"
        +}
      • addedInput schema / properties / include_all
        Added value: +{
        +  "description": "If true, return every historical JD-FIT analysis for this context (may include duplicates per candidate). Default false. Use only when user explicitly asks for full history.",
        +  "type": "boolean"
        +}
      • addedInput schema / properties / sort_by
        Added value: +{
        +  "description": "Sort order. Default: score_desc.",
        +  "enum": [
        +    "score_desc",
        +    "score_asc"
        +  ],
        +  "type": "string"
        +}
    • Addedatlas_list_cv_templates
    • Addedatlas_reformat_cv
    • Changedcareerproof_task_result1 field changed
      • addedInput schema / properties / batch_id
        Added value: +{
        +  "description": "For result_type='jd_fit_batch': scope results to a specific batch (from atlas_start_jd_fit_batch). Strongly recommended — eliminates duplicates from historical runs in the same context.",
        +  "type": "number"
        +}
  2. 67 tool updates
    • First observedatlas_add_custom_eval_text_artifact
    • First observedatlas_advisor_chat
    • First observedatlas_chat
    • First observedatlas_clear_custom_eval_rubric_overrides
    • First observedatlas_create_context
    • First observedatlas_create_custom_eval_model
    • First observedatlas_create_jd
    • First observedatlas_delete_custom_eval_model
    • First observedatlas_download_report
    • First observedatlas_fit_match_enhanced
    • First observedatlas_generate_interview
    • First observedatlas_get_analysis
    • First observedatlas_get_analytics
    • First observedatlas_get_batch_gem_results
    • First observedatlas_get_batch_gem_status
    • First observedatlas_get_candidate
    • First observedatlas_get_custom_eval_batch_results
    • First observedatlas_get_custom_eval_batch_status
    • First observedatlas_get_custom_eval_model
    • First observedatlas_get_custom_eval_rubric
    • First observedatlas_get_dialogue_results
    • First observedatlas_get_jd_fit_batch_status
    • First observedatlas_get_jd_fit_results
    • First observedatlas_get_report
    • First observedatlas_infer_custom_eval_rubric
    • First observedatlas_interview_followup
    • First observedatlas_list_analyses
    • First observedatlas_list_candidates
    • First observedatlas_list_contexts
    • First observedatlas_list_custom_eval_artifacts
    • First observedatlas_list_custom_eval_models
    • First observedatlas_list_jds
    • First observedatlas_list_report_types
    • First observedatlas_list_reports
    • First observedatlas_set_custom_eval_rubric_overrides
    • First observedatlas_start_batch_gem
    • First observedatlas_start_custom_eval_batch
    • First observedatlas_start_custom_eval_inference
    • First observedatlas_start_dialogue_assessment
    • First observedatlas_start_fit_match
    • First observedatlas_start_fit_rank
    • First observedatlas_start_gem_analysis
    • First observedatlas_start_jd_analysis
    • First observedatlas_start_jd_fit_batch
    • First observedatlas_start_report
    • First observedatlas_update_context
    • First observedatlas_update_custom_eval_model
    • First observedatlas_upload_candidate
    • First observedatlas_upload_custom_eval_artifact
    • First observedcareerproof_task_result
    • First observedcareerproof_task_status
    • First observedceevee_analyze_positioning
    • First observedceevee_chat
    • First observedceevee_confirm_lens
    • First observedceevee_download_report
    • First observedceevee_explain_change
    • First observedceevee_full_review
    • First observedceevee_generate_report
    • First observedceevee_get_opportunities
    • First observedceevee_get_positioning_session
    • First observedceevee_get_report
    • First observedceevee_get_version
    • First observedceevee_list_positioning_sessions
    • First observedceevee_list_report_types
    • First observedceevee_list_reports
    • First observedceevee_list_versions
    • First observedceevee_upload_cv

Frequently Asked Questions

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Connectors

  • # **RChilli MCP Hub** RChilli MCP Hub is a production-grade MCP server that exposes RChilli's full HR data intelligence platform as 17 AI-callable tools across 4 categories. Built on 15+ years of HR data intelligence, it is trusted by ATS vendors, HR technology platforms, staffing agencies, and enterprise recruiting teams worldwide. Every tool is read-only and returns a consistent, structured JSON response — no raw exceptions, no inconsistent formats. <br> --- <br> # **Tools — 17 Total** userkey and subuserid are injected automatically from your Bearer token — you never need to pass them manually. <br> --- <br> # **🔍 Resume & Job Description Parsing — 3 tools** <br> > ### **`extract_resume_data`** > > Extracts and converts resumes, CVs, and candidate documents into structured, searchable profiles with contact details, skills, experience, education, certifications, and taxonomy-enriched data for ATS, HCM, and AI recruiting workflows. When used on a careers page or application form, the same extraction call auto-fills every application field in under 10 seconds — documented to increase candidate conversion by up to 194%. Supports 40+ languages with English-normalized output for global intake, and runs in batch mode to process legacy databases or migration backlogs overnight at scale. Also supports resume reprocessing — re-running previously extracted resumes through the latest extraction logic and taxonomy version to bring older records up to current data quality, without requiring a new document from the candidate. Distinct from bulk import (first-time extraction of a new batch) and from talent data refresh (re-enrichment from a newer submitted resume). <br> > ### **`extract_resume_data_from_url`** > > Accepts a direct URL to a PDF, DOCX, or RTF file and returns the same normalized JSON profile as the Resume Data Extraction tool. Ideal for pipeline automation where resumes are stored in cloud storage, S3, or email attachments. Also supports the same auto-fill, multilingual, and batch-processing capabilities as the core extraction tool for URL-based intake sources. <br> > ### **`extract_job_data`** > > Extracts and converts job descriptions into structured hiring data including job title, required skills, preferred skills, responsibilities, experience, education, and taxonomy-normalized role requirements for recruitment automation and candidate matching. <br> --- <br> # **🧠 Skills & Job Taxonomy — 4 tools** <br> > ### **`lookup_skill`** > > Returns authoritative detail for a known skill including description, all aliases, related skills, proficiency levels, and O*NET/ESCO mappings. Use when you need the complete record rather than a ranked search. <br> > ### **`lookup_job_profile`** > > Returns authoritative detail for a known job profile including canonical title, SOC/O*NET code, job family, typical required and preferred skills, salary bands, and work context. <br> > ### **`autocomplete_skill`** > > Accepts a partial skill string (min 2 chars) and returns up to 10 ranked autocomplete suggestions with canonical names and categories. Prevents free-text entry errors and keeps skill data clean at point of entry. <br> > ### **`autocomplete_job_profile`** > > Accepts a partial job title string and returns ranked autocomplete suggestions with canonical titles and job families. Ensures job titles map to taxonomy profiles from the moment a recruiter starts typing. <br> --- <br> # **🛡️ Redaction, Documents & Utilities — 7 tools** <br> > ### **`redact_resume`** > > Redacts personally identifiable information from candidate profiles to support anonymized review, bias-aware screening, compliance workflows, and audit logs. Configurable redaction scope. Idempotent. <br> > ### **`reformat_resume_with_template`** > > RChilli's Resume Reformatting tool accepts any structured candidate profile and applies one of six branded templates (TM001–TM006) to produce a consistently formatted output document in PDF, DOCX, RTF, or HTML — ensuring every candidate is presented in a standardized, professional layout regardless of how their original resume was structured. Designed for staffing firms, recruitment agencies, and enterprise HR teams who need to control candidate presentation at scale, it eliminates manual reformatting effort and enforces brand consistency across all submissions. <br> > ### **`convert_document_format`** > > Accepts a document as base64 or URL and converts between PDF, DOCX, RTF, HTML, and plain text. Preserves formatting fidelity. Useful as a pre-processing step before data extraction on non-standard file types. <br> > ### **`tag_entities`** > > RChilli's Named Entity Recognition tool takes already-extracted HR text and annotates it by wrapping each recognized entity in a structured XML-style label inline — returning output such as `<job_title>Senior Data Engineer</job_title>`, `<skill>Python</skill>`, `<city>Austin</city>`, `<degree>Bachelor of Science</degree>`, and `<organization>Google</organization>` — covering 10+ HR-specific entity types including person name, state, country, date, and year. Unlike data extraction tools that produce separate field lists, tag_entities preserves the full original text structure with entities labeled in place, making the output immediately consumable by ATS field-mapping pipelines, candidate profile builders, and content annotation workflows without any offset calculation or post-processing. <br> > ### **`extract_contacts`** > > Identifies and structures names, emails, phone numbers, LinkedIn URLs, and addresses with field-level confidence scores from candidate records, emails, or documents. Safe for GDPR/CCPA workflows. <br> > ### **`geolocate`** > > Converts partial or informal location text into structured city, state, country, ISO codes, latitude, and longitude. Enables radius-based candidate and job search and supports workforce planning analytics. <br> > ### **`classify_job_zone`** > > RChilli's Job Zone Classification tool reads the job profile from a resume or job description and returns its O/*NET Job Zone — one of five standardized levels ranging from Zone 1 (little or no preparation required) through Zone 2 (some preparation), Zone 3 (medium preparation), Zone 4 (considerable preparation), to Zone 5 (extensive preparation required) — based on the education, experience, and training criteria defined by O/*NET. The returned Job Zone level enables downstream workflows such as candidate-to-role fit filtering, compensation benchmarking, over/under-qualification flagging, and job architecture standardization without any manual O/*NET lookup. <br> --- <br> # **🎯 Search & Matching — 3 tools** <br> > ### **`score_resume_against_jd`** > > Accepts one resume and one Job Description (no index required) and returns an overall match score, dimension scores, skill gap list, and natural-language explanation. Bias-controlled and audit-ready. <br> > ### **`find_matches_in_index`** > > Accepts a resume or Job Description as input and returns the top-N most similar documents from the indexed corpus ranked by semantic similarity. No index setup required for the input document. <br> > ### **`search_indexed_documents`** > > Accepts a query string and returns ranked document references from the tenant's pre-populated index. Supports Boolean and semantic search modes. Requires documents to be indexed before use.

  • Query professional profiles, search candidates, and get AI-powered summaries and job fit analysis.

  • Generate tailored, ATS-optimized resume PDFs and cover letters from a job description, over MCP.

  • AI job search MCP — fact-checked jobs, application tracker, alerts. ChatGPT, Claude, Cursor.

Related MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables LLM clients to analyse job postings, tailor resumes from an evidence-labelled profile, validate every claim against that profile, and track applications, all through deterministic MCP tools.
    Apache 2.0
  • A
    license
    A
    quality
    D
    maintenance
    Manage Job using MCP: Manage Job, Candidates, Resumes, Salaries all within this one MCP tools It can solve problems like: You have 50 resumes to screen. Your AI assistant can reason about candidates, but it can't: Read PDFs/DOCX — The AI can't open binary files Extract structured data — Copy-pasting loses formatting, metrics, and context Compare at scale — No consistent scoring across candida
    24
    72
    1
    MIT
  • A
    license
    B
    quality
    D
    maintenance
    Provides access to 47 AI-powered career tools for resume building, job tracking, ATS optimization, and interview coaching. It enables users to manage their job search, research companies, and negotiate salaries directly through an MCP-compatible AI assistant.
    55
    13
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI clients to serve as a personal career analyst by searching, matching, and explaining job recommendations, managing job applications, and syncing public job boards through standardized MCP tools.
    MIT
Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources