Recruit Crm MCP Server

recruit-crm-mcp PyPI v0.19.0

Published by ebragas — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Recruit CRM

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (src/recruit_crm_mcp/install.py)MTC-SRC-002

In the server's implementation (`src/recruit_crm_mcp/install.py:108`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: = "Darwin": subprocess.run( ["sh", "-c", "curl -LsSf https://astral.sh/uv/install.sh | sh"],

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/recruit_crm_mcp/install.py

Tools 53

Each tool and what it can reach — statically extracted from the published source.

  • upload_filenetwork egress
  • assign_candidateno sensitive capability
  • create_candidateno sensitive capability
  • create_companyno sensitive capability
  • create_contactno sensitive capability
  • create_jobno sensitive capability
  • create_noteno sensitive capability
  • create_taskno sensitive capability
  • delete_noteno sensitive capability
  • get_assigned_candidatesno sensitive capability
Show 43 more tools ↓
  • get_candidateno sensitive capability
  • get_companyno sensitive capability
  • get_contactno sensitive capability
  • get_jobno sensitive capability
  • get_meetingno sensitive capability
  • get_noteno sensitive capability
  • get_taskno sensitive capability
  • list_candidate_custom_fieldsno sensitive capability
  • list_company_custom_fieldsno sensitive capability
  • list_contact_custom_fieldsno sensitive capability
  • list_contact_stagesno sensitive capability
  • list_hiring_pipeline_stagesno sensitive capability
  • list_hiring_pipelinesno sensitive capability
  • list_industriesno sensitive capability
  • list_job_custom_fieldsno sensitive capability
  • list_jobsno sensitive capability
  • list_meeting_typesno sensitive capability
  • list_note_typesno sensitive capability
  • list_task_typesno sensitive capability
  • list_usersno sensitive capability
  • log_meetingno sensitive capability
  • pingno sensitive capability
  • report_issueno sensitive capability
  • search_candidatesno sensitive capability
  • search_companiesno sensitive capability
  • search_contactsno sensitive capability
  • search_jobsno sensitive capability
  • search_meetingsno sensitive capability
  • search_notesno sensitive capability
  • search_tasksno sensitive capability
  • set_candidate_custom_fieldsno sensitive capability
  • set_company_custom_fieldsno sensitive capability
  • set_contact_custom_fieldsno sensitive capability
  • set_job_custom_fieldsno sensitive capability
  • unassign_candidateno sensitive capability
  • update_candidateno sensitive capability
  • update_companyno sensitive capability
  • update_contactno sensitive capability
  • update_hiring_stageno sensitive capability
  • update_jobno sensitive capability
  • update_meetingno sensitive capability
  • update_noteno sensitive capability
  • update_taskno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.19.0 latest A 93/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/recruit-crm-mcp/badge.svg)](https://mcptrustchecker.com/registry/recruit-crm-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/recruit-crm-mcp"><img src="https://mcptrustchecker.com/registry/recruit-crm-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/recruit-crm-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan recruit-crm-mcp --online --registry pypi

Use the free API → How scoring works

More in Business & CRM