About Recruitercheck Mcp
RecruiterCheck MCP is a server for assessing scam risk in job postings, recruiter emails, and company domains. Its tools return deterministic risk scores and explanations, and persist scan events to Supabase.
Key features
- 01Assess job posting legitimacy
- 02Check recruiter email risk
- 03Check company domain risk
- 04Explain risk signals
- 05Persist scan events to Supabase
Use cases
- 01Screen a job posting before applying
- 02Assess an unexpected recruiter email
- 03Check a company domain linked to an opportunity
MCP support
RecruiterCheck exposes tools to MCP clients for checking job postings, recruiter emails, company domains, and risk signals. Each tool requires an API key.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp-server-seven-alpha.vercel.app/mcpclaude mcp add --transport http recruitercheck https://mcp-server-seven-alpha.vercel.app/mcp{"mcpServers":{"recruitercheck":{"type":"http","url":"https://mcp-server-seven-alpha.vercel.app/mcp"}}}Open in Cursor{"servers":{"recruitercheck":{"type":"http","url":"https://mcp-server-seven-alpha.vercel.app/mcp"}}}Open in VS Code{"mcpServers":{"recruitercheck":{"type":"http","url":"https://mcp-server-seven-alpha.vercel.app/mcp"}}}{"mcpServers":{"recruitercheck":{"serverUrl":"https://mcp-server-seven-alpha.vercel.app/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://mcp-server-seven-alpha.vercel.app/mcpAuth requiredTools
4| Parameter | Type | Required | Description |
|---|---|---|---|
| apiKey | string | Yes | |
| title | string | Yes | |
| description | string | Yes | |
| companyName | string | No | |
| recruiterEmail | string | No | |
| jobPostingUrl | string | No | |
| observedSignals | array | No |
Details
From the project READMERecruiterCheck MCP
RecruiterCheck is an MCP server that helps users quickly assess scam risk in job postings, recruiter emails, and company domains.
What it provides
Tools:
- check_job_posting_legitimacy
- check_recruiter_email
- check_company_domain
- explain_risk_signals
Each tool:
- requires an API key
- returns deterministic risk scoring output
- persists scan events to Supabase
Repo structure
- apps/mcp-server: TypeScript MCP server
- supabase/migrations: SQL migrations
- apps/landing: minimal landing page
- registry: registry submission assets
Quick start
- Install deps
cd apps/mcp-server npm install
- Set env
export SUPABASE_URL="https://.supabase.co" export SUPABASE_SERVICE_ROLE_KEY=""
- Build
npm run build
- Run server
npm run start
Apply database schema
From repo root:
supabase link --project-ref supabase db push
Migration file applied for MVP:
- supabase/migrations/202605180001_mvp_core.sql
Creates:
- public.users
- public.api_keys
- public.flagged_domains
- public.scans
API key model
The server expects apiKey in each tool input.
api_keys.key_hash stores SHA-256 of API keys.
Recommended flow:
- generate key in your backend
- hash with SHA-256
- store hash in public.api_keys with user_id
- give raw key to customer once
Local smoke test
cd apps/mcp-server node scripts/mcp-smoke.mjs
MCP client config example
Use this in local MCP-capable clients:
{ "mcpServers": { "recruitercheck": { "command": "node", "args": ["/ABSOLUTE/PATH/recruitercheck-mcp/apps/mcp-server/dist/index.js"], "env": { "SUPABASE_URL": "https://.supabase.co", "SUPABASE_SERVICE_ROLE_KEY": "" } } } }
Landing page
Minimal page is at:
- apps/landing/index.html
Registry assets
See:
- registry/mcp.json
- registry/install.md
- registry/prompts.md
- registry/submissions.md
- registry/distribution.md
Hosted MCP endpoint (production)
- Health: https://mcp-server-seven-alpha.vercel.app/
- MCP: https://mcp-server-seven-alpha.vercel.app/mcp
- Required header: Accept: application/json, text/event-stream
Status
Roadmap status is tracked in:
- docs/ROADMAP_MVP.md
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.