Name: HopeHire
Author: hopehire

HopeHire MCP

Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.

Tool-list grade A Remote · Streamable HTTP API key 167 tools v1.0.0

No reviews yet by hopehire The publisher’s own endpoint — this marketplace is not in the path

90/100

tool-list score

167

tools declared

remote

at its publisher

—

calls last 7d

What it does

Tailor resumes, score ATS fit, find hiring leads, and send cold outreach, from your agent.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http hopehire-mcp https://hopehire.in/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

# 2 — ask your agent for something these tools do
#   get_notifications_api_notifications_get, mark_all_notifications_as_read_api_notifications_read_all_post, mark_notification_as_read_api_notifications__notification_id__read_patch and 164 more

It needs AUTHORIZATION (Bearer token for your HopeHire account, created in Settings > Agents at hopehire.in): this sends it in the Authorization header from your environment, so export it first — its endpoint answers 401 without it.

HopeHire costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

hopehire1 server

1 category

All 1 server

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.

Claude Codedeclared by this listing

This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads AUTHORIZATION (Bearer token for your HopeHire account, created in Settings > Agents at hopehire.in) from your environment each time it connects and sends it in the Authorization header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx AUTHORIZATION … and open a new terminal (Windows).

claude mcp add --scope user --transport http hopehire-mcp https://hopehire.in/mcp --header 'Authorization: Bearer ${AUTHORIZATION}'

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: Authorization header — Bearer token for your HopeHire account, created in Settings > Agents at hopehire.in. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.

What you approve

167 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Get Notifications Fetch notifications for the current user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ {} ] ``

Parameter	Type	Required	Notes
is_read	boolean	no	—
limit	integer	no	—

Mark All Notifications As Read Mark every unread notification as read (not just the page the client loaded). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Mark Notification As Read Mark a notification as read. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
notification_id	string	yes	—

Delete Notification Delete a notification. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
notification_id	string	yes	—

Get Ats Score Return the most recently calculated ATS score for the user's resume. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Refresh Ats Score Recalculate the ATS score from the current resume and persist it. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Resume Ai Chat Stream an AI response that helps the user interactively improve their resume. Body: user_id (str) — authenticated user's ID message (str) — latest user message conversation_history (list) — [{role: "user"|"assistant", content: str}] ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Mark Improvement Suggestions Invalid Replace improvement suggestions with the provided valid_suggestions list. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—
valid_suggestions	array	yes	—

Generate Yaml Version Generate YAML version and RenderCV PDF for existing resume ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Apply Suggestions Apply improvement suggestions to YAML and regenerate PDF ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Yaml Suggestions Generate YAML-based improvement suggestions ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Generate Complete Resume Generate a complete, enhanced resume with additional relevant content using AI. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—
resume_text	string	yes	—

Render Raw Yaml Hot-reload: Generate PDF from raw YAML content ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

List Themes ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Apply Resume Theme Switch the design theme in a YAML document. Pure transform: no render, no save. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Save Resume Yaml Save raw YAML content to the user's resume. YAML is treated as the source of truth: the structured resume fields (personalInfo, experience, education, projects, skills, certifications) are parsed from the YAML and written back to the database so that every other part of the application (resume overview, AI chat, job matching …) always reflects the latest YAML edits. ### Respons

No parameter schema on file.

Create Resume From Linkedin Create a resume from LinkedIn profile URL using Apify API. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

No parameter schema on file.

Get Rendercv Pdf Get RenderCV PDF download URL for the user's resume. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Get Rendercv Pdf Download Return a presigned URL with Content-Disposition: attachment so the browser downloads the resume PDF instead of opening it inline. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Test Pdf Generation Test PDF generation to debug PDF issues. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Debug Pdf Get debugging information about a PDF file. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
file_path	string	yes	—

Download Resume Download the user's resume. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
s3Path	string	yes	—

Public Resume Resume link embedded in cold emails: no login, but only links we signed will open. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
s3Path	string	yes	—
sig	string	yes	—

Show Resume Show the resume via redirect to presigned S3 URL. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
s3Path	string	yes	—

Get Resume Get the user's resume. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	no	—

Upload Resume Upload and process a resume file. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
file	string	no	—
user_id	string	no	—

Update Resume Manual Update a user's resume manually and trigger PDF generation. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
id	string	yes	—
userId	string	yes	—
personalInfo	object	yes	—
experience	array	yes	—
education	array	yes	—
projects	array	no	—
skills	array	yes	—
certifications	array	no	—
achievements	array	no	—
positionsOfResponsibility	array	no	—
extracurriculars	array	no	—
languages	array	no	—
createdAt	string	yes	—
updatedAt	string	yes	—
fileName	string	no	—
fileSize	integer	no	—
fileType	string	no	—
s3Path	string	no	—
jobPreferences	object	no	—
improvementSuggestions	array	no	—

Delete Resume Delete the user's resume and cleanup associated resources. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	no	—
s3Path	string	no	—

Set Cold Email Resume Source Set which resume file cold outreach should use: the originally uploaded file ("uploaded", the default) or HopeHire's RenderCV-generated PDF ("generated"). A lightweight sibling to the full manual-edit PUT above — this only flips one field and doesn't trigger PDF/YAML regeneration. ### Responses: 200: Successful Response (Success Response) Content-Type: applicati

No parameter schema on file.

Get Preferences Get the user's job preferences Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	no	—

Create Preferences Create the user's job preferences Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
id	string	no	—
userId	string	no	—
locations	array	no	—
locationTypes	array	no	—
targetRoles	array	no	—
techStack	array	no	—
targetCompanies	array	no	—
industries	array	no	—
jobTypes	array	no	—
experienceLevels	array	no	—
functionAreas	array	no	—
specializations	array	no	—
graduationYear	integer	no	—
expectedCtc	string	no	—
isFresher	boolean	no	—
updatedAt	string	no	—

Update Preferences Update the user's job preferences Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
id	string	no	—
userId	string	no	—
locations	array	no	—
locationTypes	array	no	—
targetRoles	array	no	—
techStack	array	no	—
targetCompanies	array	no	—
industries	array	no	—
jobTypes	array	no	—
experienceLevels	array	no	—
functionAreas	array	no	—
specializations	array	no	—
graduationYear	integer	no	—
expectedCtc	string	no	—
isFresher	boolean	no	—
updatedAt	string	no	—

Delete Preferences Delete the user's job preferences Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	no	—

Start Job Matching Start an asynchronous job matching process Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	no	User ID to match jobs for
resume_id	string	no	Resume ID to use for matching
use_preferences	boolean	no	Whether to filter jobs by user preferences first

Get Filtered Jobs Get filtered job matches for a user Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	no	User ID to get matches for
resume_id	string	no	Resume ID to get matches for
location	string	no	Filter by location
location_type	string	no	Filter by location type (remote, onsite, hybrid)
job_type	string	no	Filter by job type
experience_level	string	no	Filter by experience level
min_salary	number	no	Filter by minimum salary
keywords	array	no	Filter by keywords
min_match_score	number	no	Filter by minimum match score
limit	integer	no	Maximum number of results to return
offset	integer	no	Number of results to skip
sort_by	string	no	Field to sort by
sort_order	string	no	Sort order (asc or desc)

Clear Job Matches Clear all job matches for a user Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	no	User ID to clear matches for

Start Conversation Start a new conversation using the shared auto-apply service logic. ### Responses: 201: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
job_id	string	yes	Related job ID
user_id	string	yes	User ID initiating the conversation
resume_id	string	no	Resume ID if available
user_profile	object	no	User profile (optional, for backward compatibility)

Start auto-apply process Launches an automated job application process that finds contacts, generates personalized messages, and sends emails with resume attachments. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "task_id": "Task Id", "status": "AutoApplyStatus" } ``

Parameter	Type	Required	Notes
job_id	string	yes	ID of the job to apply for
user_id	string	yes	ID of the user applying for the job
user_profile	object	yes	User profile information for job application

Get all auto-apply tasks for a user Get all auto-apply tasks for a given user. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	no	ID of the user to fetch tasks for

Check auto-apply status Retrieves the current status and results of an auto-apply task. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "task_id": "Task Id", "status": "AutoApplyStatus" } ``

Parameter	Type	Required	Notes
task_id	string	yes	Auto-apply task ID returned from the start endpoint

Get Auto Apply Status By Task Id Get status of an auto-apply task by task_id (conversationId). Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "task_id": "Task Id", "status": "AutoApplyStatus" } ``

Parameter	Type	Required	Notes
task_id	string	yes	Auto-apply task ID

Start Conversation Start a new email conversation. ### Responses: 201: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
contact_email	string	yes	Email address of the contact
contact_name	string	no	Name of the contact
subject_line	string	yes	Subject line for the conversation
intent	string	yes	Primary intent of the conversation
job_id	string	no	Related job ID if applicable
initial_body	string	no	Optional initial message body
context_data	object	no	Additional context data

Get Conversations Get all conversations for the authenticated user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json [ { "id": "Id", "contact_email": "Contact Email", "status": "ConversationStatus", "intent": "ConversationIntent", "subject_line": "Subject Line", "message_count": 1, "last_up

Parameter	Type	Required	Notes
skip	integer	no	—
limit	integer	no	—

Get Conversation Details Get details of a specific conversation. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "id": "Id", "contact_email": "Contact Email", "status": "ConversationStatus", "intent": "ConversationIntent", "subject_line": "Subject Line", "message_count": 1, "last_updated": "2023-01-01T0

Parameter	Type	Required	Notes
conversation_id	string	yes	ID of the conversation to get

Pause Conversation Pause an ongoing conversation to stop automatic follow-ups. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
conversation_id	string	yes	ID of the conversation to pause

Resume Conversation Resume a paused conversation. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
conversation_id	string	yes	ID of the conversation to resume

Send Manual Message Send a manual message in the conversation, overriding the AI. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
conversation_id	string	yes	ID of the conversation
message_content	string	yes	Content of the manual message to send

Resolve Protocol Resolve a human-intervention protocol by sending a manual reply and marking the associated notification as read. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
conversation_id	string	yes	ID of the conversation
message_content	string	yes	Content of the manual message to send
notification_id	string	yes	ID of the notification to mark as read

Get System Stats Get overall system statistics ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "workers": [ {} ], "total_active_users": 1, "system_status": "System Status" } ``

No parameter schema on file.

Get Active Users Get list of active users with email monitoring enabled ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ {} ] ``

Parameter	Type	Required	Notes
skip	integer	no	Number of users to skip
limit	integer	no	Maximum number of users to return

Enable User Monitoring Enable email monitoring for a specific user ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Disable User Monitoring Disable email monitoring for a specific user ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Update User Monitoring Config Update email monitoring configuration for a user ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	User ID
email_monitoring_enabled	boolean	no	Enable/disable email monitoring
monitoring_frequency	integer	no	Monitoring frequency in seconds
priority	string	no	Priority level (low, normal, high)

Trigger User Discovery Manually trigger user discovery process ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get User Monitoring Status Get monitoring status for a specific user ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Get Email Analytics Report Get email analytics report for a user over a specific duration. Duration options: - 7d: Last 7 days - 30d: Last 30 days - 90d: Last 90 days - 1y: Last year - all: All time ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—
duration	string	yes	—

Get Email Analytics Summary Get a quick summary of email analytics for the last 30 days. This is a lightweight endpoint for dashboard widgets. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Get User Memory Get user memory by user ID ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	yes	—

Create User Memory Create new user memory ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	yes	—
job_preferences	object	no	—
compensation	object	no	—
notice_period	object	no	—
screening_profile	object	no	—
career_context	object	no	—
communication_preferences	object	no	—
auto_apply_preferences	object	no	—
safety_guardrails	object	no	—
ai_context_notes	string	no	—

Update User Memory Update existing user memory ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	yes	—
job_preferences	object	no	—
compensation	object	no	—
notice_period	object	no	—
screening_profile	object	no	—
career_context	object	no	—
communication_preferences	object	no	—
auto_apply_preferences	object	no	—
safety_guardrails	object	no	—
ai_context_notes	string	no	—

Delete User Memory Delete (deactivate) user memory ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	yes	—

Get User Memory History Get user memory history (all versions) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true, "total": 1, "page": 1, "limit": 1 } ``

Parameter	Type	Required	Notes
user_id	string	yes	—
page	integer	no	Page number
limit	integer	no	Items per page

Add Ai Interaction Context Add AI interaction context to user memory ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	yes	—

Update Remembered Field Answer Edit one remembered application-field answer from the memory-bank UI. Same durable store the extension writes to (interaction_history, keyed by normalized label) - this just lets the user correct it directly instead of waiting to be asked the question again on some future form. ### Responses: 200: Successful Response (Success Response) Content-Type: applicatio

Parameter	Type	Required	Notes
user_id	string	yes	—
label	string	yes	—
value	string	yes	—

Delete Remembered Field Answer Forgets one remembered application-field answer (memory-bank UI delete action). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
user_id	string	yes	—
normalized_label	string	yes	The entry's normalized_label, as returned in interaction_history

Apply Memory Suggestion Apply a specific memory update suggested by the AI. Body: { user_id, suggestion } ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

User Memory Ai Chat ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Available Senders Get all available email senders (admin only — exposes other senders' PII and quotas) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

No parameter schema on file.

Get Least Used Sender Get the least used email sender for load balancing, considering company contact history (admin only) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
company_id	string	no	Company ID to consider for contact history
company_name	string	no	Company name to consider for contact history

Get Fallback Sender Get a fallback email sender, excluding the specified user (admin only) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
exclude_user_id	string	no	User ID to exclude from selection

Send Email Via Pool Send an email using the email sender pool (admin only) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
to	string	yes	—
subject	string	yes	—
message_text	string	yes	—
sender_user_id	string	no	—
s3_attachment_key	string	no	—
attachment_filename	string	no	—
thread_id	string	no	—
in_reply_to	string	no	—
references	string	no	—

Get My Footer Get the footer for the currently authenticated user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Update My Footer Update the footer for the currently authenticated user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
name	string	no	—
email	string	no	—
phone	string	no	—
linkedin	string	no	—
github	string	no	—
portfolio	string	no	—
title	string	no	—
company	string	no	—
location	string	no	—
project_links	array	no	—

Get Email Footer Get email footer for a user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Update Email Footer Update email footer for a user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—
name	string	no	—
email	string	no	—
phone	string	no	—
linkedin	string	no	—
github	string	no	—
portfolio	string	no	—
title	string	no	—
company	string	no	—
location	string	no	—
project_links	array	no	—

Get Formatted Footer Get formatted footer string for a user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Generate Footer From Resume Generate email footer from user's resume data. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Get User Config Get configuration for a specific user ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Update User Config Update configuration for a specific user ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Reset User Config Reset user configuration to defaults ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Get Campaign Config Get configuration for a specific campaign ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
campaign_id	string	yes	—

Update Campaign Config Update configuration for a specific campaign ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
campaign_id	string	yes	—

Reset Campaign Config Reset campaign configuration to defaults ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
campaign_id	string	yes	—

Get Effective Config Get effective configuration combining user and campaign settings ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—
campaign_id	string	no	—

Get Default Config Get default configuration values ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get All User Configs Get all user configurations (admin only) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get All Campaign Configs Get all campaign configurations (admin only) ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Available Leads Return leads for the authenticated user, filtered by outreach status. status=fresh — leads not yet contacted (default); AI-ranked status=queued — leads the user has queued for outreach status=contacted — leads the user has already emailed ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
limit	integer	no	—
offset	integer	no	—
email_only	boolean	no	Only return leads with a known email address
min_quality	number	no	—
status	string	no	fresh \| queued \| contacted

Get All Leads Admin Admin view: return all leads regardless of outreach status. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
limit	integer	no	—
offset	integer	no	—
email_only	boolean	no	—
min_quality	number	no	—

Get Lead Stats Return summary statistics for the lead database. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

List Accounts List all LinkedIn scraper accounts in the pool (passwords masked). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Add Account Add a LinkedIn scraper account to the pool. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
email	string	yes	—
password	string	yes	—
proxy	string	no	—
assigned_queries	array	no	—
max_requests_per_day	integer	no	—

Update Account Status Update the status of a LinkedIn account (active / cooldown / banned). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
account_id	string	yes	—
status	string	yes	—

List Scrape Runs List recent scrape run records for audit / dashboard (admin only: they hold platform-wide queries and volumes). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
limit	integer	no	—

Get Lead Outreach History Return the outreach thread for this lead for the current user. Returns a chronological list of events: - type=sent — initial cold email - type=follow_up — follow-up email - type=reply — recruiter reply ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
lead_id	string	yes	—

Get Lead Fetch a single lead by its ID. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
lead_id	string	yes	—

Update Outreach Status Update the current user's outreach status for a given lead. Use this after sending a cold email so the lead is marked as contacted. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
lead_id	string	yes	—
status	string	yes	—
cold_email_id	string	no	—
notes	string	no	—

Send Outreach From Lead Generate and send a cold outreach email directly from a LinkedIn lead. Flow: 1. Fetch the lead — must have an email address. 2. Load the authenticated user's resume/profile from MongoDB. 3. Call send_and_track_cold_email() to generate (or use custom_message) and send the email via the user's connected Gmail. 4. Record the outreach status on the lead (status='

Parameter	Type	Required	Notes
lead_id	string	yes	—
job_link	string	no	Optional job URL to include in the email
custom_message	string	no	Override the LLM-generated email body

Generate Linkedin Message Generate a short LinkedIn outreach message (≤280 chars) personalised to this lead. The frontend copies it to clipboard and opens the recruiter's LinkedIn profile so the user can paste-and-send in one step. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
lead_id	string	yes	—

Bulk Send Outreach Send outreach emails to multiple leads in one call. Each lead must have an email address. Leads without emails are skipped. Returns per-lead results so the frontend can show success/fail per contact. Rate-limited to 20 leads per request to protect Gmail sending quotas. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
lead_ids	array	yes	List of lead IDs to contact

Trigger Scrape Manually kick off a LinkedIn scrape run. Admin only: each run spends metered Apify credits and accepts arbitrary search queries. Strategy (tried in order): 1. Publish to the linkedin_scrape_queue via RabbitMQ (if running). 2. If RabbitMQ is unavailable or times out, run the scrape directly as a FastAPI BackgroundTask so this endpoint always returns fast. ### Responses:

Parameter	Type	Required	Notes
queries	array	no	—
max_posts_per_query	integer	no	—

Apify Webhook Receives push notifications from Apify when a scraper run completes. No authentication required (Apify calls this endpoint). Apify includes a secret token in the URL for verification in production. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

List Templates Return the user's email templates, generating them if none exist yet. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ { "id": "Id", "name": "Name", "subject": "Subject", "body": "Body", "usage_count": 1, "reply_count": 1, "reply_rate": 1.0 } ] ``

No parameter schema on file.

Update Template Edit a template's subject, body, or name. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "id": "Id", "name": "Name", "subject": "Subject", "body": "Body", "usage_count": 1, "reply_count": 1, "reply_rate": 1.0 } ``

Parameter	Type	Required	Notes
template_id	string	yes	—
subject	string	no	—
body	string	no	—
name	string	no	—

Regenerate Templates Delete all existing templates and generate a fresh one via AI. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ { "id": "Id", "name": "Name", "subject": "Subject", "body": "Body", "usage_count": 1, "reply_count": 1, "reply_rate": 1.0 } ] ``

No parameter schema on file.

Get Tools Schema Returns the JSON schema for all available tools. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
use_composio	boolean	no	Whether to include Composio tools

Execute Tool Executes a tool by name with provided arguments. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Connection Url Get the authorization URL for a specific Composio app. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
app_name	string	yes	—

Disconnect App Revoke the user's Composio connection for a specific app. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
app_name	string	yes	—

List Connections List all active connections for the user in Composio. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Integration Status Get the connection status for key integrations across all providers. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get User Credits Return the current user's credit balance, referral code, and total referrals. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Referral Code Return the user's referral code, generating one if it doesn't exist yet. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Claim Referral Code Claim a referral code. Awards 10 credits to both the claimer and the referrer. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
referral_code	string	yes	—

Get Outreach Queue Get pending outreach queue items for the current user. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ {} ] ``

No parameter schema on file.

Approve Outreach Item Approve a queue item and send the cold email. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
item_id	string	yes	—

Dismiss Outreach Item Dismiss an outreach queue item. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
item_id	string	yes	—

Get Autopilot Settings ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "daily_outreach_enabled": true, "outreach_timezone": "Outreach Timezone", "daily_outreach_batch_size": 1, "credit_balance": 1, "autopilot_enabled": true, "outreach_paused": true } ``

No parameter schema on file.

Update Daily Outreach Settings ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "daily_outreach_enabled": true, "outreach_timezone": "Outreach Timezone", "daily_outreach_batch_size": 1, "credit_balance": 1, "autopilot_enabled": true, "outreach_paused": true } ``

Parameter	Type	Required	Notes
daily_outreach_enabled	boolean	yes	—
outreach_timezone	string	no	—
daily_outreach_batch_size	integer	no	—

Resume Outreach Endpoint User-initiated: clear the bounce circuit breaker's paused state. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "daily_outreach_enabled": true, "outreach_timezone": "Outreach Timezone", "daily_outreach_batch_size": 1, "credit_balance": 1, "autopilot_enabled": true, "outreach_paus

No parameter schema on file.

Update Legacy Autopilot Settings Legacy job-board autopilot — not available when daily outreach is enabled. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "autopilot_enabled": true, "autopilot_min_match_score": 1.0 } ``

Parameter	Type	Required	Notes
autopilot_enabled	boolean	yes	—
autopilot_min_match_score	number	yes	—

Get Active Outreach Batch ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Get Outreach Batch ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
batch_id	string	yes	—

Create Outreach Batch ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
batch_type	string	yes	linkedin_leads \| outreach_queue
item_ids	array	no	Explicit IDs to process; otherwise auto-select from fresh/pending items
limit	integer	no	—
min_quality	number	no	—

Cancel Outreach Batch ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
batch_id	string	yes	—

Get Pending Auto Replies List pending auto-replies the user can still cancel. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ {} ] ``

No parameter schema on file.

Cancel Pending Auto Reply Cancel a pending auto-reply before it fires. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
reply_id	string	yes	—

Create Application Track a newly-submitted job application (called by the extension after a user submits). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "user_id": "User Id", "company_name": "Company Name", "job_title": "Job Title", "job_url": "Job Url", "platform": "Platform", "status": "ApplicationSta

Parameter	Type	Required	Notes
company_name	string	yes	—
job_title	string	yes	—
job_url	string	yes	—
platform	string	no	—

List Applications List the current user's tracked applications, most recent first. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json [ { "user_id": "User Id", "company_name": "Company Name", "job_title": "Job Title", "job_url": "Job Url", "platform": "Platform", "status": "ApplicationStatus",

Parameter	Type	Required	Notes
limit	integer	no	—
offset	integer	no	—

Update Application Status Manually update an application's status (e.g. marking Interview/Offer/Rejected). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "user_id": "User Id", "company_name": "Company Name", "job_title": "Job Title", "job_url": "Job Url", "platform": "Platform", "status": "ApplicationSta

Parameter	Type	Required	Notes
application_id	string	yes	—
status	string	yes	—

Answer Fields AI fallback for job-application form fields the extension's coded/heuristic fill pass could not confidently answer. Batched per application (not per field) to control latency and cost. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "answers": [ { "field_id": "Field Id", "confidence":

Parameter	Type	Required	Notes
job_context	object	yes	—
fields	array	yes	—

Agent Step Tier 4: one step of an agentic fallback loop for pages where tiers 1-3 (coded adapters, universal field matcher, batched AI field-answering) found nothing to work with. The extension sends a snapshot of every visible interactive element on the page; this returns exactly one action to take next. Never raises on a bad/failed model response - degrades to "blocked" so the client loop just

Parameter	Type	Required	Notes
job_context	object	yes	—
elements	array	yes	—
history	array	no	—
step	integer	yes	—

Remember Field Answer Durable, cross-device, cross-site memory of one field answer the extension learned - either a confirmed AI answer or a user's correction, fired on every blur/selection of a field the extension filled. Grounds future /answer-fields calls (see get_remembered_field_answers above) so the same question doesn't need asking again on the next application, anywhere. Requires extensio

Parameter	Type	Required	Notes
label	string	yes	—
value	string	yes	—

Tailor Resume Generates a one-off resume PDF reworded toward a specific job description, for the extension to swap into a file-upload field before submitting that one application. Never persisted to the user's profile/canonical resume. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "pdf_base64": "Pdf Base64", "f

Parameter	Type	Required	Notes
job_description	string	yes	—

Match Score Ad-hoc resume<->job-description match score for a posting the extension is looking at, which isn't (and doesn't need to be) a job stored in the DB. Uses the pure heuristic matcher (no embeddings/DB lookups needed). ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "match_score": 1.0, "summary": "Summary

Parameter	Type	Required	Notes
job_description	string	yes	—

Get Extension Settings ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "recruiter_comms_consent": true, "field_memory_consent": true, "credit_balance": 1 } ``

No parameter schema on file.

Update Extension Settings ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "recruiter_comms_consent": true, "field_memory_consent": true, "credit_balance": 1 } ``

Parameter	Type	Required	Notes
recruiter_comms_consent	boolean	no	—
field_memory_consent	boolean	no	—

Extension Apply Orchestrator called by the extension right after a user submits a job application: tracks the application, then immediately attempts the same credit-gated cold-outreach send the daily cron would eventually do, triggered on-demand instead. Outreach is best-effort: if there is no known contact for the company or the user is out of credits, the application is still tracked and the re

Parameter	Type	Required	Notes
company_name	string	yes	—
job_title	string	yes	—
job_url	string	yes	—
job_description	string	no	—
platform	string	no	—

Send Product Update Broadcast Manually trigger a one-off product-update broadcast to all subscribed users. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
subject	string	yes	—
html_body	string	yes	—

Unsubscribe Public link clicked from a newsletter email - no auth, verified by HMAC signature. ### Responses: 200: Successful Response (Success Response) Content-Type: text/html Example Response: ``json "string" ``

Parameter	Type	Required	Notes
uid	string	yes	—
sig	string	yes	—

Submit Feedback ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
action_type	string	yes	—
feedback_text	string	no	—

List Keys ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

Create Key Create a new API key. The raw key is only ever returned here -- store it now. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
name	string	yes	—

Delete Key ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
key_id	string	yes	—

Invite Info Public (pre-login) details for the join page. Unknown, used and expired all look the same. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
token	string	yes	—

My Org ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

My Org Summary ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

No parameter schema on file.

My Students ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
cohort_id	string	no	—
q	string	no	—
limit	integer	no	—
skip	integer	no	—

Remove Student ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—

Create Invites ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
invites	array	yes	—

List Invites ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
status	string	no	—

Revoke Invite ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
invite_id	string	yes	—

Get Least Contacted Hr Get the least contacted HR email for a specific company. This endpoint uses the same logic as the unified email flow to select the best HR contact. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "success": true, "hr_email": "Hr Email", "company_name": "Company Name", "total_contacts":

Parameter	Type	Required	Notes
company_name	string	yes	Name of the company to get least contacted HR for

Get Cold Email Get cold emails for a user with pagination. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "cold_emails": [ { "user_id": "User Id", "recruiter_email": "Recruiter Email", "company_name": "Company Name", "sent_at": "2023-01-01T00:00:00Z", "sta

Parameter	Type	Required	Notes
offset	integer	yes	—
pagination	integer	yes	—
user_id	string	no	—

Send Cold Email Send a cold email with a pre-generated message. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "user_id": "User Id", "recruiter_email": "Recruiter Email", "company_name": "Company Name", "sent_at": "2023-01-01T00:00:00Z", "status": "Status", "followup_interval_hou

Parameter	Type	Required	Notes
recruiter_email	string	yes	—
company_name	string	yes	—
user_id	string	yes	—
user_profile	object	yes	—
message	string	yes	—

Preview Cold Email Generate a preview of a cold email without sending it. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "message": "Message", "subject": "Subject" } ``

Parameter	Type	Required	Notes
recruiter_email	string	yes	—
company_name	string	yes	—
user_id	string	yes	—
user_profile	object	yes	—

Send Cold Email To Hr Send a cold email to a specific HR contact. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
user_id	string	yes	—
company_id	string	yes	—
company_name	string	yes	—
hr_email	string	yes	—
user_profile	object	yes	—

Send Unified Cold Email Unified cold email endpoint that handles: 1. Company creation if it doesn't exist 2. HR email auto-selection if not provided 3. HR contact addition to company 4. Email sending with tracking Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ```json { "success": true, "cold_emai

Parameter	Type	Required	Notes
company_name	string	yes	—
is_new_company	boolean	no	—
user_id	string	yes	—
sender_user_id	string	no	—
user_profile	object	yes	—
hr_email	string	no	—
fallback_enabled	boolean	no	—
email_content	string	no	—
subject	string	no	—
jobLink	string	no	—

Preview Unified Cold Email Generate a preview for unified cold email flow. Requires authentication. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "message": "Message", "subject": "Subject" } ``

Parameter	Type	Required	Notes
company_name	string	yes	—
is_new_company	boolean	no	—
user_id	string	yes	—
sender_user_id	string	no	—
user_profile	object	yes	—
hr_email	string	no	—
fallback_enabled	boolean	no	—
email_content	string	no	—
subject	string	no	—
jobLink	string	no	—

Get Cold Email Replies Get replies for a specific cold email using its ID. This checks both the cold_emails collection and email_conversations collection. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
cold_email_id	string	yes	—

Get Cold Email Replies By Message Id Get replies for a cold email using its Gmail message_id. This is useful when you have the message_id from the cold email response. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
message_id	string	yes	—

List Companies ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json [ { "hrContacts": [ { "email": "Email" } ], "hrContactCount": 1 } ] ``

No parameter schema on file.

Create Company Endpoint ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "hrContacts": [ { "email": "Email" } ], "hrContactCount": 1 } ``

Parameter	Type	Required	Notes
name	string	yes	—
hrEmail	string	yes	—

Add Hr Contact Endpoint ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "name": "Name" } ``

Parameter	Type	Required	Notes
company_id	string	yes	—

Tracking Pixel Endpoint for the email tracking pixel. When loaded, it updates the corresponding email record as opened. ### Responses: 200: Successful Response (Success Response) Content-Type: application/json

Parameter	Type	Required	Notes
email_id	string	yes	—

Get Job Details Get detailed job listings with advanced filters and pagination ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true, "personalized": true } ``

Parameter	Type	Required	Notes
limit	integer	no	Maximum number of jobs to return
offset	integer	no	Number of jobs to skip
sort_by	string	no	Field to sort by, or 'relevance' for a personalised ranking
sort_order	string	no	Sort order (asc or desc)
search	string	no	Search term for job title, company, or description
location	string	no	Filter by location
remote	boolean	no	Filter by remote jobs
job_type	string	no	Filter by job type
experience_level	string	no	Filter by experience level
company	string	no	Filter by company name
salary_min	number	no	Minimum salary
salary_max	number	no	Maximum salary

Get Job Detail Get a detailed job listing by ID ### Responses: 200: Successful Response (Success Response) Content-Type: application/json Example Response: ``json { "success": true } ``

Parameter	Type	Required	Notes
job_id	string	yes	Job ID

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install HopeHire or to call it, at any volume.

ATool-list grade · score 90 / 100

Release 1.0.0 · scanned 28 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score90

Findings0 threat · 1 capability

Capabilityhigh

Coveragemanifest

Verificationnot in this report

Surface digest9978df9b8781799b179eaf2120e346434a67537f1525d1f09e16c1e142744d2d

Score vectorthreat 100 → client 90

Term	Level	What it prices	Points
capability-exposure	high	capability blast radius (high) — client exposure if the model is manipulated	−6
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.

Tool	Capability tags	Why the tag was assigned
get_notifications_api_notifications_get	untrusted-input	untrusted-input: keyword "fetch"
mark_all_notifications_as_read_api_notifications_read_all_post	no tags
mark_notification_as_read_api_notifications__notification_id__read_patch	no tags
delete_notification_api_notifications__notification_id__delete	no tags
get_ats_score_api_resume_ats_score_get	no tags
refresh_ats_score_api_resume_ats_score_refresh_post	no tags
resume_ai_chat_api_resume_ai_chat_post	no tags
mark_improvement_suggestions_invalid_api_resume_improvement_suggestions_mark_invalid_post	no tags
generate_yaml_version_api_resume_generate_yaml_post	no tags
apply_suggestions_api_resume_apply_suggestions_post	no tags
get_yaml_suggestions_api_resume_yaml_suggestions_post	no tags
generate_complete_resume_api_resume_generate_complete_post	no tags
render_raw_yaml_api_resume_render_raw_yaml_post	no tags
list_themes_api_resume_themes_get	no tags
apply_resume_theme_api_resume_apply_theme_post	no tags
save_resume_yaml_api_resume_save_yaml_post	no tags
create_resume_from_linkedin_api_resume_from_linkedin_post	no tags
get_rendercv_pdf_api_resume_rendercv_pdf_get	untrusted-input	untrusted-input: keyword "download"
get_rendercv_pdf_download_api_resume_rendercv_pdf_download_get	untrusted-input	untrusted-input: keyword "download"
test_pdf_generation_api_resume_test_pdf_generation_get	no tags
debug_pdf_api_resume_debug_pdf_get	no tags
download_resume_api_resume_download_get	untrusted-input	untrusted-input: keyword "download"
public_resume_api_resume_public_get	no tags
show_resume_api_resume__resume_id__get	no tags
get_resume_api_resume_get	no tags
upload_resume_api_resume_post	no tags
update_resume_manual_api_resume_put	no tags
delete_resume_api_resume_delete	no tags
set_cold_email_resume_source_api_resume_cold_email_source_put	no tags
get_preferences_api_job_preferences_get	no tags
create_preferences_api_job_preferences_post	no tags
update_preferences_api_job_preferences_put	no tags
delete_preferences_api_job_preferences_delete	no tags
start_job_matching_api_job_matches_start_post	no tags
get_filtered_jobs_api_job_matches_get	no tags
clear_job_matches_api_job_matches_delete	no tags
start_conversation_api_auto_apply_start_conversation_post	no tags
start_auto_apply_api_auto_apply_post	no tags
get_auto_apply_tasks_api_auto_apply_get	no tags
get_auto_apply_status_api_auto_apply__task_id__get	no tags
get_auto_apply_status_by_task_id_api_auto_apply_status__task_id__get	no tags
start_conversation_api_email_conversations_start_conversation_post	no tags
get_conversations_api_email_conversations_get	no tags
get_conversation_details_api_email_conversations__conversation_id__get	no tags
pause_conversation_api_email_conversations__conversation_id__pause_post	no tags
resume_conversation_api_email_conversations__conversation_id__resume_post	no tags
send_manual_message_api_email_conversations__conversation_id__message_post	no tags
resolve_protocol_api_email_conversations__conversation_id__resolve_post	no tags
get_system_stats_api_multi_tenant_monitoring_stats_get	no tags
get_active_users_api_multi_tenant_monitoring_users_active_get	no tags
enable_user_monitoring_api_multi_tenant_monitoring_users__user_id__enable_post	no tags
disable_user_monitoring_api_multi_tenant_monitoring_users__user_id__disable_post	no tags
update_user_monitoring_config_api_multi_tenant_monitoring_users__user_id__config_put	no tags
trigger_user_discovery_api_multi_tenant_monitoring_discovery_trigger_post	no tags
get_user_monitoring_status_api_multi_tenant_monitoring_users__user_id__status_get	no tags
get_email_analytics_report_api_reports__user_id___duration__get	no tags
get_email_analytics_summary_api_reports__user_id__summary_get	no tags
get_user_memory_api_user_memory__user_id__get	no tags
create_user_memory_api_user_memory__user_id__post	no tags
update_user_memory_api_user_memory__user_id__put	no tags
delete_user_memory_api_user_memory__user_id__delete	no tags
get_user_memory_history_api_user_memory__user_id__history_get	no tags
add_ai_interaction_context_api_user_memory__user_id__context_post	no tags
update_remembered_field_answer_api_user_memory__user_id__remembered_field_put	no tags
delete_remembered_field_answer_api_user_memory__user_id__remembered_field_delete	no tags
apply_memory_suggestion_api_user_memory_apply_suggestion_post	no tags
user_memory_ai_chat_api_user_memory_ai_chat_post	no tags
get_available_senders_api_email_sender_pool_senders_get	no tags
get_least_used_sender_api_email_sender_pool_least_used_sender_get	no tags
get_fallback_sender_api_email_sender_pool_fallback_sender_get	no tags
send_email_via_pool_api_email_sender_pool_send_email_post	external-sink	external-sink: keyword "send_email"
get_my_footer_api_email_footer_me_get	no tags
update_my_footer_api_email_footer_me_put	no tags
get_email_footer_api_email_footer__user_id__get	no tags
update_email_footer_api_email_footer__user_id__put	no tags
get_formatted_footer_api_email_footer__user_id__formatted_get	no tags
generate_footer_from_resume_api_email_footer__user_id__generate_from_resume_post	no tags
get_user_config_api_config_user__user_id__get	no tags
update_user_config_api_config_user__user_id__put	no tags
reset_user_config_api_config_user__user_id__delete	no tags
get_campaign_config_api_config_campaign__campaign_id__get	no tags
update_campaign_config_api_config_campaign__campaign_id__put	no tags
reset_campaign_config_api_config_campaign__campaign_id__delete	no tags
get_effective_config_api_config_effective__user_id__get	no tags
get_default_config_api_config_defaults_get	no tags
get_all_user_configs_api_config_admin_users_get	no tags
get_all_campaign_configs_api_config_admin_campaigns_get	no tags
get_available_leads_api_linkedin_leads_get	no tags
get_all_leads_admin_api_linkedin_leads_all_get	no tags
get_lead_stats_api_linkedin_leads_stats_get	no tags
list_accounts_api_linkedin_leads_accounts_get	no tags
add_account_api_linkedin_leads_accounts_post	no tags
update_account_status_api_linkedin_leads_accounts__account_id__status_patch	no tags
list_scrape_runs_api_linkedin_leads_scrape_runs_get	untrusted-input	untrusted-input: keyword "scrape"
get_lead_outreach_history_api_linkedin_leads__lead_id__history_get	no tags
get_lead_api_linkedin_leads__lead_id__get	untrusted-input	untrusted-input: keyword "fetch"
update_outreach_status_api_linkedin_leads__lead_id__outreach_patch	no tags
send_outreach_from_lead_api_linkedin_leads__lead_id__send_outreach_post	untrusted-input	untrusted-input: keyword "fetch"
generate_linkedin_message_api_linkedin_leads__lead_id__generate_linkedin_message_post	no tags
bulk_send_outreach_api_linkedin_leads_bulk_outreach_post	no tags
trigger_scrape_api_linkedin_leads_trigger_post	untrusted-input	untrusted-input: keyword "scrape"
apify_webhook_api_linkedin_leads_webhook_apify_post	external-sink	external-sink: keyword "webhook"
list_templates_api_email_templates_get	no tags
update_template_api_email_templates__template_id__put	no tags
regenerate_templates_api_email_templates_regenerate_post	no tags
get_tools_schema_api_tools_schema_get	no tags
execute_tool_api_tools_execute_post	no tags
get_connection_url_api_tools_connect__app_name__get	no tags
disconnect_app_api_tools_connect__app_name__delete	no tags
list_connections_api_tools_connections_get	no tags
get_integration_status_api_tools_status_get	no tags
get_user_credits_api_referrals_credits_get	no tags
get_referral_code_api_referrals_code_get	no tags
claim_referral_code_api_referrals_claim_post	no tags
get_outreach_queue_api_outreach_queue_get	no tags
approve_outreach_item_api_outreach_queue__item_id__approve_post	no tags
dismiss_outreach_item_api_outreach_queue__item_id__delete	no tags
get_autopilot_settings_api_autopilot_settings_get	no tags
update_daily_outreach_settings_api_autopilot_settings_patch	no tags
resume_outreach_endpoint_api_autopilot_resume_outreach_post	no tags
update_legacy_autopilot_settings_api_autopilot_legacy_settings_patch	no tags
get_active_outreach_batch_api_outreach_batches_active_get	no tags
get_outreach_batch_api_outreach_batches__batch_id__get	no tags
create_outreach_batch_api_outreach_batches_post	no tags
cancel_outreach_batch_api_outreach_batches__batch_id__cancel_post	no tags
get_pending_auto_replies_api_auto_replies_get	no tags
cancel_pending_auto_reply_api_auto_replies__reply_id__delete	no tags
create_application_api_applications_post	no tags
list_applications_api_applications_get	no tags
update_application_status_api_applications__application_id__status_patch	no tags
answer_fields_api_extension_answer_fields_post	no tags
agent_step_api_extension_agent_step_post	no tags
remember_field_answer_api_extension_remember_field_answer_post	no tags
tailor_resume_api_extension_tailor_resume_post	no tags
match_score_api_extension_match_score_post	no tags
get_extension_settings_api_extension_settings_get	no tags
update_extension_settings_api_extension_settings_patch	no tags
extension_apply_api_extension_apply_post	no tags
send_product_update_broadcast_api_newsletter_send_post	no tags
unsubscribe_api_newsletter_unsubscribe_get	no tags
submit_feedback_api_feedback_post	no tags
list_keys_api_api_keys_get	sensitive-source	sensitive-source: keyword "list_keys"
create_key_api_api_keys_post	no tags
delete_key_api_api_keys__key_id__delete	no tags
invite_info_api_orgs_invites__token__get	no tags
my_org_api_orgs_me_get	no tags
my_org_summary_api_orgs_me_summary_get	no tags
my_students_api_orgs_me_students_get	no tags
remove_student_api_orgs_me_students__user_id__delete	no tags
create_invites_api_orgs_me_invites_post	no tags
list_invites_api_orgs_me_invites_get	no tags
revoke_invite_api_orgs_me_invites__invite_id__delete	no tags
get_least_contacted_hr_api_cold_email_least_contacted_hr_get	no tags
get_cold_email_api_cold_email_get	no tags
send_cold_email_api_cold_email_post	no tags
preview_cold_email_api_cold_email_preview_post	no tags
send_cold_email_to_hr_api_cold_email_send_to_hr_post	no tags
send_unified_cold_email_api_cold_email_unified_post	no tags
preview_unified_cold_email_api_cold_email_unified_preview_post	no tags
get_cold_email_replies_api_cold_email__cold_email_id__replies_get	no tags
get_cold_email_replies_by_message_id_api_cold_email_message__message_id__replies_get	no tags
list_companies_api_companies_get	no tags
create_company_endpoint_api_companies_post	no tags
add_hr_contact_endpoint_api_companies__company_id__hr_contacts_post	no tags
tracking_pixel_api_tracking_pixel__email_id__png_get	no tags
get_job_details_api_v1_jobs_get	no tags
get_job_detail_api_v1_jobs__job_id__get	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

download_resume_api_resume_download_get → list_keys_api_api_keys_get → apify_webhook_api_linkedin_leads_webhook_apify_post

A cross-tool exfiltration chain exists: download_resume_api_resume_download_get → list_keys_api_api_keys_get → apify_webhook_api_linkedin_leads_webhook_apify_post.

Supply chain and provenance

Integrityfirst-seen

Surface digest9978df9b8781799b

Scanned2026-10-28

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.

HopeHire MCP

What it does

Quickstart

Where are you running it?

Tool surface

What counts against your monthly calls

What the scan could actually read

Capability — what it could do if the model were manipulated

Toxic-flow graph

Supply chain and provenance

Release history

See also