MCP server for the Check Payroll API
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"check": {
"env": {
"CHECK_API_KEY": "your-api-key"
},
"args": [
"run",
"--directory",
"/path/to/mcp-server-check",
"mcp-server-check"
],
"command": "uv"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
⚠️ Early Access Beta — This MCP server is currently in beta and available to select partners. APIs, tools, and behavior may change without notice. Please share feedback with your Check point of contact.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in finance
Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators
A Model Context Protocol server for building an investor agent
AI agents get on-chain identity, credentials, reputation, escrow, and persistent memory on XRPL.
Remote MCP server to integrate and validate self-hosted PayRam deployments.
MCP Security Weekly
Get CVE alerts and security updates for Mcp Server Check and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
⚠️ Early Access Beta — This MCP server is currently in beta and available to select partners. APIs, tools, and behavior may change without notice. Please share feedback with your Check point of contact.
Terms of Service — By using this MCP server to access the Check API, you agree to the MCP Usage Terms, which are in addition to your existing agreement with Check.
An MCP server that wraps the Check Payroll API, providing 263 tools for managing companies, employees, contractors, payrolls, tax configuration, embedded components, and more.
git clone https://github.com/check-technologies/mcp-server-check.git
cd mcp-server-check
uv sync
CHECK_API_KEY=your-key uv run mcp-server-check
| Environment Variable | Required | Default | Description |
|---|---|---|---|
CHECK_API_KEY | Yes | — | Your Check API key (Bearer token) |
CHECK_API_BASE_URL | No | https://sandbox.checkhq.com | API base URL |
CHECK_TOOL_MODE | No | dynamic | Tool mode: dynamic (3 meta-tools) or all (all tools individually) |
CHECK_TOOLSETS | No | — | Comma-separated list of toolsets to enable (e.g. companies,employees) |
CHECK_TOOLS | No | — | Comma-separated allowlist of individual tool names |
CHECK_EXCLUDE_TOOLS | No | — | Comma-separated list of tool names to hide |
CHECK_READ_ONLY | No | — | Set to 1, true, or yes to disable all write/mutating tools |
CHECK_TRANSPORT | No | stdio | Transport protocol: stdio, sse, or streamable-http |
By default the server connects to the Check sandbox (https://sandbox.checkhq.com), which is safe for testing and development. The sandbox supports simulation endpoints (e.g. simulate_start_processing, simulate_complete_funding) that let you advance payrolls through processing states without real money movement.
To point at production, set:
CHECK_API_BASE_URL=https://api.checkhq.com
The server supports fine-grained tool filtering, configurable via environment variables (for stdio) or HTTP headers (for SSE / streamable-http). This follows the GitHub MCP Server configuration pattern.
| Feature | Environment Variable | HTTP Header |
|---|---|---|
| Toolsets | CHECK_TOOLSETS | X-MCP-Toolsets |
| Individual tools | CHECK_TOOLS | X-MCP-Tools |
| Exclude tools | CHECK_EXCLUDE_TOOLS | X-MCP-Exclude-Tools |
| Read-only | CHECK_READ_ONLY | X-MCP-Readonly |
Filtering precedence: exclude_tools > read_only > tools > toolsets. Exclude always wins; if tools is set it acts as an allowlist independent of toolsets.
There are 17 toolsets, one per API module: bank_accounts, companies, compensation, components, contractor_payments, contractors, documents, employees, external_payrolls, forms, payments, payroll_items, payrolls, platform, tax, webhooks, workplaces.
Enable only specific toolsets:
CHECK_TOOLSETS=companies,employees CHECK_API_KEY=your-key uv run mcp-server-check
Allow only specific tools by name:
CHECK_TOOLS=list_companies,get_company,list_employees CHECK_API_KEY=your-key uv run mcp-server-check
Hide specific tools while keeping everything else:
CHECK_EXCLUDE_TOOLS=create_company,delete_company CHECK_API_KEY=your-key uv run mcp-server-check
Set CHECK_READ_ONLY=1 to run the server with only read-only tools (list, get, download, preview, etc.). All create, update, delete, and other mutating tools are excluded. This is useful when you want to allow exploration of your Check data without risk of modifications.
CHECK_READ_ONLY=1 CHECK_API_KEY=your-key uv run mcp-server-check