Addepar MCP
Ask Claude about Addepar holdings, performance, exposure, transactions and private fund capital calls.
Work Check's US payroll API from Claude: companies, employees, payrolls, taxes.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Check MCP server connects the Check Payroll API — US payroll infrastructure for software platforms — to Claude and other MCP clients. It manages companies, employees, contractors, payrolls, tax settings, filings and documents, with 270 tools behind three meta-tools. Check says the version in Claude's directory leaves out the tools that move money.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
read_only parameter, X-MCP-Readonly header), toolset filtering (X-MCP-Toolsets) and tool exclusion (X-MCP-Exclude-Tools) are documented for Check's hosted endpoints, not for the directory one.scopes_supported, so access is bounded by Console permissions and the controls above, not by consent scopes.No, according to Check. Its hosted MCP guide states the directory version does not include tools that move money, such as approving a payroll or the payments tools. Anthropic's listing still names approve_payroll and create_contractor_payment, which matches Check's full server rather than the directory one. We could not read the live list to settle the difference.
Yes, on Check's own hosted URLs. Appending read_only=true to the endpoint, or sending the X-MCP-Readonly header, disables create, update, delete and approve operations. Check also lets you limit a session to named toolsets or exclude individual tools by name. Check documents these controls for its hosted endpoints; it does not say whether the directory endpoint honours them.
Start with sandbox. Check recommends its sandbox endpoint for testing and warns that production actions are real: payrolls will be processed, payments sent and records modified. Use the production URL only when you are ready to work with live data, ideally with read-only mode or toolset filtering switched on to limit what an agent can change.
llms.txt (retrieved 2026-11-18) · retrieved 2026-11-18initialize to https://mcp.checkhq.com/anthropic/mcp returned HTTP 401 with a WWW-Authenticate challenge naming https://mcp.checkhq.com/.well-known/oauth-protected-resource/anthropic/mcp, which lists https://mcp.checkhq.com/anthropic as authorization server and an empty scope list. Check's documented https://mcp.checkhq.com/check/mcp returned its own 401 and descriptor; an invented path returned 404; a GET on the directory endpoint returned 405 (2026-11-18). · retrieved 2026-11-18Connect Check once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.