How do I use mcp-server-check?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-server-check list my companies" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

mcp-server-check

Official

by check-technologies

Overview Schema Related Servers Score Discussions

Python

Remote

This server wraps the Check Payroll API, providing comprehensive payroll and HR management through 263 tools organized across 20 toolsets.

Tool Discovery & Execution (Default Dynamic Mode)

search_tools — find relevant tools by keyword
list_toolsets — browse available categories
run_tool — execute any tool by name with arguments

Set CHECK_TOOL_MODE=all to expose all 263 tools individually instead.

Payroll & Payments Create, update, approve, reopen, preview, and delete payrolls; manage payroll items, contractor payments, and external payrolls; retry/refund/cancel payments; simulate payroll processing states in sandbox.

People Management

Employees: Create, update, onboard; manage paystubs, forms, SSN, tax elections, and attributes
Contractors: Create, update, onboard; manage payments, forms, and SSN/EIN
Companies: Create, update, onboard; manage signatories, enrollment, and embedded setup
Workplaces: Create and manage workplace locations

Compensation & Benefits Manage pay schedules, paydays, employee/company benefits, post-tax deductions, earning rates, earning codes, and net pay splits.

Tax Management Configure company/employee tax parameters and elections; manage filings and filing blockers; access tax statements, packages, and reference data (taxes, agencies, jurisdictions).

Documents & Forms Access and download company/employee/contractor tax documents; manage authorization and setup documents; list, render, validate, and submit forms.

Reporting Payroll journal, payroll summary, tax liabilities, contractor payments, W-2 preview, cash requirements, paper checks, and more.

Embedded UI Components Generate embeddable component URLs for 25 company workflows (e.g., run payroll, tax setup), 9 employee workflows (e.g., benefits, paystubs), and 1 contractor component (tax documents).

Platform & Integrations Manage webhooks, API logs, notifications, accounting sync, integration partners, and address validation.

Configuration & Safety

CHECK_READ_ONLY=1 — disable all mutating tools
Toolset and individual tool allow/exclude filtering via environment variables or HTTP headers
Sandbox environment for safe testing without real money movement
Cursor-based pagination (limit + cursor) on all list tools

mcp-server-check

⚠️ 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 261 tools for managing companies, employees, contractors, payrolls, tax configuration, embedded components, and more.

Quickstart

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

Related MCP server: TimePRO MCP Server

Configuration

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`

Sandbox vs Production

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

Server Configuration

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.

Toolsets

There are 20 toolsets, one per API module: agencies, bank_accounts, companies, compensation, components, contractor_payments, contractors, documents, employees, external_payrolls, forms, logs, payments, payroll_items, payrolls, platform, tax, webhooks, workflows, workplaces.

Enable only specific toolsets:

CHECK_TOOLSETS=companies,employees CHECK_API_KEY=your-key uv run mcp-server-check

Individual Tools

Allow only specific tools by name:

CHECK_TOOLS=list_companies,get_company,list_employees CHECK_API_KEY=your-key uv run mcp-server-check

Excluding Tools

Hide specific tools while keeping everything else:

CHECK_EXCLUDE_TOOLS=create_company,delete_company CHECK_API_KEY=your-key uv run mcp-server-check

Read-Only Mode

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

HTTP Headers (Remote Transport)

When running with CHECK_TRANSPORT=sse or CHECK_TRANSPORT=streamable-http, clients can pass configuration via HTTP headers:

X-MCP-Toolsets: companies,employees
X-MCP-Readonly: true
X-MCP-Exclude-Tools: create_company,delete_company

Header-based configuration takes precedence over environment variables when headers provide any filter settings.

Dynamic Tool Mode (Default)

By default, the server runs in dynamic mode (CHECK_TOOL_MODE=dynamic), exposing 3 meta-tools instead of all individual tools. This avoids sending every tool schema to the LLM upfront, saving significant context window space.

search_tools(query, toolset?, limit?) — Search for tools by keyword with synonym matching. Returns matching tools with their full parameter schemas.
list_toolsets() — List all available toolsets with descriptions and example tools.
run_tool(tool_name, arguments?) — Execute a tool by name with a dict of arguments.

The LLM workflow becomes: browse toolsets or search for relevant tools → review their parameter schemas → call run_tool with the correct arguments. All filtering (CHECK_TOOLSETS, CHECK_READ_ONLY, etc.) is applied at both the search and execution layers.

Set CHECK_TOOL_MODE=all to expose all tools individually (legacy mode):

CHECK_TOOL_MODE=all CHECK_API_KEY=your-key uv run mcp-server-check

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "check": {
      "command": "uv",
      "args": ["run", "--directory", "/path/to/mcp-server-check", "mcp-server-check"],
      "env": {
        "CHECK_API_KEY": "your-api-key"
      }
    }
  }
}

Usage with Claude Code

claude mcp add check -- uv run --directory /path/to/mcp-server-check mcp-server-check

Then set the CHECK_API_KEY environment variable in your shell before running Claude Code.

Available Tools

261 tools organized across 17 categories. All list tools support limit and cursor parameters for cursor-based pagination — pass the cursor value from a previous response to fetch the next page.

Companies (26 tools)

Tool	Method	Description
`list_companies`	GET	List companies with optional filters
`get_company`	GET	Get details for a specific company
`create_company`	POST	Create a new company
`update_company`	PATCH	Update an existing company
`onboard_company`	POST	Onboard a company to active status
`get_company_paydays`	GET	Get upcoming paydays for a company
`list_company_tax_deposits`	GET	List tax deposits for a company
`get_company_benefit_aggregations`	GET	Get benefit aggregations for a company
`get_payroll_journal_report`	GET	Get payroll journal report; optional `include_contractor_id` for CSV
`get_payroll_summary_report`	GET	Get payroll summary report; optional `include_contractor_id` for CSV
`get_tax_liabilities_report`	GET	Get tax liabilities report
`get_contractor_payments_report`	GET	Get contractor payments report
`get_child_support_payments_report`	GET	Get child support payments report
`get_w4_exemption_status_report`	GET	Get W-4 exemption status report
`get_applied_for_ids_detailed_report`	GET	Get applied-for IDs detailed report
`get_w2_preview_report`	GET	Get W-2 preview report
`list_federal_ein_verifications`	GET	List federal EIN verifications
`get_federal_ein_verification`	GET	Get a specific EIN verification
`list_signatories`	GET	List signatories for a company
`create_signatory`	POST	Create a signatory
`get_enrollment_profile`	GET	Get enrollment profile
`create_enrollment_profile`	PUT	Create enrollment profile
`update_enrollment_profile`	PATCH	Update enrollment profile
`start_implementation`	POST	Start implementation for a company
`cancel_implementation`	POST	Cancel implementation
`request_embedded_setup`	POST	Request embedded setup

Employees (17 tools)

Tool	Method	Description
`list_employees`	GET	List employees with optional filters
`get_employee`	GET	Get details for a specific employee
`create_employee`	POST	Create a new employee
`update_employee`	PATCH	Update an existing employee
`onboard_employee`	POST	Onboard an employee to active status
`list_employee_paystubs`	GET	List paystubs for an employee
`get_employee_paystub`	GET	Get a specific paystub
`list_employee_forms`	GET	List forms for an employee
`get_employee_form`	GET	Get a specific employee form
`submit_employee_form`	POST	Submit an employee form
`sign_and_submit_employee_form`	POST	Sign and submit an employee form
`get_employee_company_defined_attributes`	GET	Get company-defined attributes
`update_employee_company_defined_attributes`	PATCH	Update company-defined attributes
`get_employee_reciprocity_elections`	GET	Get reciprocity elections
`update_employee_reciprocity_elections`	PATCH	Update reciprocity elections
`reveal_employee_ssn`	GET	Reveal employee SSN
`authorize_employee_partner`	POST	Authorize a partner for an employee

Contractors (10 tools)

Tool	Method	Description
`list_contractors`	GET	List contractors with optional filters
`get_contractor`	GET	Get details for a specific contractor
`create_contractor`	POST	Create a new contractor
`update_contractor`	PATCH	Update an existing contractor
`onboard_contractor`	POST	Onboard a contractor to active status
`list_contractor_payments_for_contractor`	GET	List payments for a contractor
`get_contractor_payment_for_payroll`	GET	Get contractor payment for a payroll
`list_contractor_forms`	GET	List forms for a contractor
`submit_contractor_form`	POST	Submit a contractor form
`reveal_contractor_ssn`	GET	Reveal contractor SSN/EIN

Workplaces (4 tools)

Tool	Method	Description
`list_workplaces`	GET	List workplaces
`get_workplace`	GET	Get details for a specific workplace
`create_workplace`	POST	Create a new workplace
`update_workplace`	PATCH	Update an existing workplace

Payrolls (15 tools)

Tool	Method	Description
`list_payrolls`	GET	List payrolls with optional filters
`get_payroll`	GET	Get details for a specific payroll
`create_payroll`	POST	Create a new payroll
`update_payroll`	PATCH	Update an existing payroll
`delete_payroll`	DELETE	Delete a payroll
`preview_payroll`	GET	Preview a payroll before approval
`approve_payroll`	POST	Approve a payroll for processing
`reopen_payroll`	POST	Reopen a previously approved payroll
`get_payroll_paper_checks`	GET	Get paper checks for a payroll
`get_payroll_cash_requirement_report`	GET	Get cash requirement report
`get_payroll_paper_checks_report`	GET	Get paper checks report
`simulate_start_processing`	POST	Simulate starting processing (sandbox)
`simulate_complete_funding`	POST	Simulate completing funding (sandbox)
`simulate_fail_funding`	POST	Simulate failing funding (sandbox)
`simulate_complete_disbursements`	POST	Simulate completing disbursements (sandbox)

Payroll Items (8 tools)

Tool	Method	Description
`list_payroll_items`	GET	List payroll items
`get_payroll_item`	GET	Get details for a specific payroll item
`create_payroll_item`	POST	Create a new payroll item
`update_payroll_item`	PATCH	Update an existing payroll item
`bulk_update_payroll_items`	PATCH	Bulk update payroll items
`delete_payroll_item`	DELETE	Delete a payroll item
`bulk_delete_payroll_items`	DELETE	Bulk delete payroll items
`get_payroll_item_paper_check`	GET	Get paper check for a payroll item

Contractor Payments (6 tools)

Tool	Method	Description
`list_contractor_payments`	GET	List contractor payments
`get_contractor_payment`	GET	Get details for a specific payment
`create_contractor_payment`	POST	Create a new contractor payment
`update_contractor_payment`	PATCH	Update a contractor payment
`delete_contractor_payment`	DELETE	Delete a contractor payment
`get_contractor_payment_paper_check`	GET	Get paper check for a payment

External Payrolls (8 tools)

Tool	Method	Description
`list_external_payrolls`	GET	List external payrolls; optionally omit line items with `include_items=false`
`get_external_payroll`	GET	Get details for a specific external payroll
`create_external_payroll`	POST	Create a new external payroll
`update_external_payroll`	PATCH	Update an external payroll
`delete_external_payroll`	DELETE	Delete an external payroll
`approve_external_payroll`	POST	Approve an external payroll
`reopen_external_payroll`	POST	Reopen an external payroll
`preview_external_payroll`	GET	Preview an external payroll

Compensation (32 tools)

Pay schedules, benefits, post-tax deductions, company benefits, earning rates, earning codes, and net pay splits.

Tool	Method	Description
Pay Schedules
`list_pay_schedules`	GET	List pay schedules
`get_pay_schedule`	GET	Get a specific pay schedule
`create_pay_schedule`	POST	Create a new pay schedule
`update_pay_schedule`	PATCH	Update a pay schedule
`delete_pay_schedule`	DELETE	Delete a pay schedule
`get_pay_schedule_paydays`	GET	Get paydays for a pay schedule
Benefits
`list_benefits`	GET	List employee benefits
`get_benefit`	GET	Get a specific benefit
`create_benefit`	POST	Create an employee benefit
`update_benefit`	PATCH	Update a benefit
`delete_benefit`	DELETE	Delete a benefit
Post-Tax Deductions
`list_post_tax_deductions`	GET	List post-tax deductions
`get_post_tax_deduction`	GET	Get a specific post-tax deduction
`create_post_tax_deduction`	POST	Create a post-tax deduction
`update_post_tax_deduction`	PATCH	Update a post-tax deduction
`delete_post_tax_deduction`	DELETE	Delete a post-tax deduction
Company Benefits
`list_company_benefits`	GET	List company-level benefits
`get_company_benefit`	GET	Get a specific company benefit
`create_company_benefit`	POST	Create a company benefit
`update_company_benefit`	PATCH	Update a company benefit
`delete_company_benefit`	DELETE	Delete a company benefit
Earning Rates
`list_earning_rates`	GET	List earning rates
`get_earning_rate`	GET	Get a specific earning rate
`create_earning_rate`	POST	Create an earning rate
`update_earning_rate`	PATCH	Update an earning rate
Earning Codes
`list_earning_codes`	GET	List earning codes
`get_earning_code`	GET	Get a specific earning code
`create_earning_code`	POST	Create an earning code
`update_earning_code`	PATCH	Update an earning code
Net Pay Splits
`list_net_pay_splits`	GET	List net pay splits
`get_net_pay_split`	GET	Get a specific net pay split
`create_net_pay_split`	POST	Create a net pay split

Bank Accounts (6 tools)

Tool	Method	Description
`list_bank_accounts`	GET	List bank accounts
`get_bank_account`	GET	Get a specific bank account
`create_bank_account`	POST	Create a new bank account
`update_bank_account`	PATCH	Update a bank account
`delete_bank_account`	DELETE	Delete a bank account
`reveal_bank_account_number`	GET	Reveal full account number

Documents (19 tools)

Tool	Method	Description
Company Tax Documents
`list_company_tax_documents`	GET	List company tax documents
`get_company_tax_document`	GET	Get a specific company tax document
`download_company_tax_document`	GET	Download a company tax document
Company Authorization Documents
`list_company_authorization_documents`	GET	List authorization documents
`get_company_authorization_document`	GET	Get an authorization document
`download_company_authorization_document`	GET	Download an authorization document
Employee Tax Documents
`list_employee_tax_documents`	GET	List employee tax documents
`get_employee_tax_document`	GET	Get an employee tax document
`download_employee_tax_document`	GET	Download an employee tax document
Contractor Tax Documents
`list_contractor_tax_documents`	GET	List contractor tax documents
`get_contractor_tax_document`	GET	Get a contractor tax document
`download_contractor_tax_document`	GET	Download a contractor tax document
Setup Documents
`list_setup_documents`	GET	List setup documents
`get_setup_document`	GET	Get a setup document
`download_setup_document`	GET	Download a setup document
Company Provided Documents
`list_company_provided_documents`	GET	List company-provided documents
`get_company_provided_document`	GET	Get a company-provided document
`create_company_provided_document`	POST	Create a company-provided document
`upload_company_provided_document_file`	POST	Upload a file for a document

Forms (4 tools)

Tool	Method	Description
`list_forms`	GET	List forms across all companies
`get_form`	GET	Get a specific form
`render_form`	GET	Render a form for display
`validate_form`	POST	Validate form data before submission

Logs (2 tools)

Tool	Method	Description
`list_logs`	GET	List API request logs; filter by path, method, status code/class, log ID, idempotency key, and time range
`get_log`	GET	Get the full record for a single API request log

Payments (6 tools)

Tool	Method	Description
`list_payments`	GET	List payments
`get_payment`	GET	Get a specific payment
`list_payment_attempts`	GET	List payment attempts
`retry_payment`	POST	Retry a failed payment
`refund_payment`	POST	Refund a payment
`cancel_payment`	POST	Cancel a payment

Tax (28 tools)

Tax parameters, elections (including tax exemptions), filings, statements, packages, and tax reference data.

Tool	Method	Description
Company Tax Params
`get_company_tax_params`	GET	Get tax parameters for a company
`update_company_tax_params`	PATCH	Update company tax parameters
`list_company_tax_param_settings`	GET	List tax parameter settings
`get_company_tax_param_setting`	GET	Get a specific tax param setting
`list_company_jurisdictions`	GET	List tax jurisdictions for a company
Employee Tax Params
`list_employee_tax_params`	GET	List employee tax parameters
`get_employee_tax_params`	GET	Get tax parameters for an employee
`update_employee_tax_params`	PATCH	Update employee tax parameters
`list_employee_tax_param_settings`	GET	List employee tax param settings
`get_employee_tax_param_setting`	GET	Get a specific setting
`list_employee_jurisdictions`	GET	List tax jurisdictions for an employee
`bulk_get_employee_tax_param_settings`	POST	Bulk get tax param settings
`bulk_update_employee_tax_param_settings`	POST	Bulk update tax param settings
Company Tax Elections
`list_company_tax_elections`	GET	List tax elections (exemption settings); filter by company, tax, exemptible, jurisdiction
`create_company_tax_elections`	POST	Create company tax elections
`update_company_tax_elections`	PATCH	Update company tax elections (incl. exemptions)
Employee Tax Elections
`list_employee_tax_elections`	GET	List tax elections (exemption settings); filter by employee, company, tax, exemptible, jurisdiction
`update_employee_tax_elections`	PATCH	Update employee tax elections (incl. exemptions)
Filings
`list_filings`	GET	List tax filings
`get_filing`	GET	Get a specific tax filing
`add_filing_blockers`	POST	Add blockers to a filing
`remove_filing_blockers`	POST	Remove blockers from a filing
Employee Tax Statements
`list_employee_tax_statements`	GET	List employee tax statements
`get_employee_tax_statement`	GET	Get a specific tax statement
Tax Packages
`request_tax_package`	POST	Request a tax package
`get_tax_package`	GET	Get a specific tax package
Taxes (reference data)
`list_taxes`	GET	List tax objects (payroll levies); filter by jurisdiction, payer, supported/remittable, effective status
`get_tax`	GET	Get a specific tax object

Agencies (2 tools)

The counterparties Check files and remits to (IRS, state revenue departments). Global read-only reference data.

Tool	Method	Description
`list_agencies`	GET	List agencies; filter by jurisdiction or label
`get_agency`	GET	Get a specific agency

Webhooks (7 tools)

Tool	Method	Description
`list_webhook_configs`	GET	List webhook configurations
`get_webhook_config`	GET	Get a specific webhook configuration
`create_webhook_config`	POST	Create a webhook configuration
`update_webhook_config`	PATCH	Update a webhook configuration
`delete_webhook_config`	DELETE	Delete a webhook configuration
`ping_webhook_config`	POST	Send a test ping
`list_webhook_deliveries`	GET	List webhook deliveries with status + attempts
`get_webhook_delivery`	GET	Get a webhook delivery
`retry_webhook_delivery`	POST	Re-enqueue a webhook delivery (sandbox only)

Platform (27 tools)

Notifications, communications, usage, integrations, accounting, company groups, addresses, setups, and requirements.

Tool	Method	Description
Notifications
`list_notifications`	GET	List notifications
`get_notification`	GET	Get a specific notification
Communications
`list_communications`	GET	List communications
`get_communication`	GET	Get a specific communication
`create_communication`	POST	Create a communication
Usage
`list_usage_summaries`	GET	List usage summaries
`list_usage_records`	GET	List usage records
Integrations
`list_integration_partners`	GET	List integration partners
`get_integration_partner`	GET	Get a specific integration partner
`authorize_integration_partner`	POST	Authorize an integration partner
`list_integration_permissions`	GET	List integration permissions
`get_integration_permission`	GET	Get a specific permission
`list_integration_accesses`	GET	List integration accesses
Accounting
`list_accounting_accounts`	GET	List accounting accounts for a company
`refresh_accounting_accounts`	POST	Refresh accounting accounts
`get_accounting_mappings`	GET	Get accounting mappings
`update_accounting_mappings`	PATCH	Update accounting mappings
`toggle_accounting_mappings`	POST	Toggle accounting mappings
`sync_accounting`	POST	Trigger an accounting sync
`list_accounting_sync_attempts`	GET	List accounting sync attempts
Company Groups
`list_company_groups`	GET	List company groups
Addresses
`validate_address`	POST	Validate an address
Setups
`list_setups`	GET	List setups
`get_setup`	GET	Get a specific setup
Requirements
`list_requirements`	GET	List requirements
`get_requirement`	GET	Get a specific requirement
Reports
`get_applied_for_ids_report`	GET	Get applied-for IDs report

Embedded Components (35 tools)

Generate embeddable UI component URLs via POST /{entity_type}/{entity_id}/components/{component_type}. All tools accept an entity_id and optional data configuration.

Company components (25): create_company_previous_provider_access_component, create_company_accounting_integration_component, create_company_authorization_documents_component, create_company_business_details_component, create_company_checklist_component, create_company_company_reports_component, create_company_connect_bank_account_component, create_company_details_component, create_company_early_enrollment_component, create_company_employee_setup_component, create_company_filing_authorization_component, create_company_filing_preview_component, create_company_full_service_setup_submission_component, create_company_integrations_component, create_company_integrations_authorize_component, create_company_pay_history_component, create_company_payment_setup_component, create_company_progress_tracker_component, create_company_run_payroll_component, create_company_signatory_agreements_component, create_company_tax_documents_component, create_company_tax_setup_component, create_company_team_setup_component, create_company_terms_of_service_component, create_company_verification_documents_component

Employee components (9): create_employee_benefits_component, create_employee_payment_setup_component, create_employee_paystubs_component, create_employee_post_tax_deductions_component, create_employee_profile_component, create_employee_ssn_setup_component, create_employee_tax_documents_component, create_employee_tax_setup_component, create_employee_withholdings_setup_component

Contractor components (1): create_contractor_tax_documents_component

Development

git clone https://github.com/check-technologies/mcp-server-check.git
cd mcp-server-check
uv sync --group dev
uv run pytest  # 311 tests

Pre-commit hooks

This repo ships a pre-commit config that runs ruff check and ruff format (the same checks as CI) before each commit. Enable it once after cloning:

uv run pre-commit install

To run the hooks manually against all files: uv run pre-commit run --all-files.

Available Tools

3 tools

list_toolsetsList ToolsetsA

Read-onlyIdempotent

List all available API toolsets with descriptions.

Returns a summary of each toolset including its name, description, tool count, and example tools. Use this to understand what's available before searching for specific tools.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnlyHint, idempotentHint, destructiveHint), description adds what the return summary includes (name, description, tool count, example tools). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose, minimal and efficient. No extraneous content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given output schema exists, description covers return fields, usage context, and differentiation. Complete for a simple list tool with no parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (no parameters). Baseline 3 applies; description adds no parameter info but none needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description states 'List all available API toolsets with descriptions' – a clear verb+resource. It distinguishes from sibling search_tools by suggesting to use this before searching.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use this to understand what's available before searching for specific tools' – gives concrete context and implies when to use vs search_tools. Could be more specific about not using for running tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

run_toolRun ToolA

Destructive

Execute an API tool by name with the given arguments.

Use search_tools first to find the tool name and its parameter schema.

tool_name: The exact tool name (e.g. "list_companies", "get_employee"). arguments: Tool arguments as a JSON string or dict (e.g. '{"company_id": "com_xxx"}' or {"company_id": "com_xxx"}). confirm: Set to true to confirm execution of a destructive tool (approve, delete, simulate, refund, cancel). Required when CHECK_CONFIRM_DESTRUCTIVE is enabled and the tool is destructive.

ParametersJSON Schema

Name	Required	Description	Default
`confirm`	No
`arguments`	No
`tool_name`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A5/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare destructiveHint=true, and the description adds crucial context by detailing the 'confirm' parameter's role in approving destructive actions. This goes beyond the annotation by explaining the execution workflow, making behavioral expectations transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with two short paragraphs and a bullet-style list for parameters. It is front-loaded with the core purpose and quickly provides actionable details without extraneous text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's generic execution role and the presence of an output schema (not shown), the description covers all necessary aspects: how to find the tool, how to pass arguments, and when to confirm destructive actions. It is complete for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Despite 0% schema description coverage, the description adds significant meaning: it specifies that 'tool_name' must be an exact name, explains 'arguments' as a JSON string or dict, and clarifies the 'confirm' parameter's purpose. This compensates for the schema's lack of explanation.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Execute an API tool by name with the given arguments.' This is a specific verb and resource, and it is distinctly different from the sibling tools 'list_toolsets' and 'search_tools', which are for discovery, not execution.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises to 'Use search_tools first to find the tool name and its parameter schema,' providing clear context for proper use. It also explains when the 'confirm' parameter is required, which is valuable guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

search_toolsSearch ToolsA

Read-onlyIdempotent

Search for available API tools by keyword.

Returns matching tools with their full parameter schemas, ready for use with run_tool. Call with an empty query to see all available toolsets. Supports synonym matching (e.g. "pay employees" finds payroll tools).

query: Search keywords (e.g. "list companies", "create employee", "payroll"). toolset: Optional toolset name to restrict search (e.g. "companies", "employees"). limit: Maximum number of results (default 20).

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	No
`toolset`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond annotations (readOnly, idempotent, non-destructive), description adds valuable behavioral traits: synonym matching and that results include full parameter schemas. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise and well-structured: starts with purpose, then describes return value and usage, followed by parameter details. Every sentence adds unique value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Complete for a search tool with 3 parameters and an output schema. Description covers all relevant aspects: behavior, parameters, return value, and usage context. Output schema handles return details.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema coverage, description fully explains all three parameters: query, toolset (optional restriction), limit (default 20). Provides examples and defaults, adding necessary meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: search for API tools by keyword. It also explains that it returns tools with full parameter schemas for use with run_tool, distinct from siblings list_toolsets and run_tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage guidance: call with empty query to see all toolsets, and mentions synonym matching. However, does not explicitly state when not to use or list alternatives, though sibling tools provide context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.6/5.0

Disambiguation5/5

Each tool has a distinct purpose: list_toolsets provides an overview, search_tools finds specific tools, and run_tool executes them. No overlap or ambiguity.

Naming Consistency5/5

All tools use a consistent verb_noun pattern in snake_case (list_toolsets, search_tools, run_tool), making the convention predictable.

Tool Count5/5

With 3 tools, the server is well-scoped for its meta-purpose of discovering and executing API tools. Each tool is essential and the count feels appropriate.

Completeness4/5

The set covers listing, searching, and executing tools. A minor gap is the lack of a dedicated tool to get details for a single toolset, but search_tools can handle that. Overall, it's complete for the stated purpose.

Maintenance

ActivityActive

ResponsivenessSyncing

Resources

GitHub Repository

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

modern-treasury A
io.usefulapi
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
Finance Payments & Billing
172
codat A
io.usefulapi
MCP server for Codat — companies, connections, invoices, bills and financial statements.
Finance ERP Systems Data Platforms
282
mcp-server
io.klokin
MCP server exposing klokin time-tracking operations (employees, time entries, stores) to AI clients.
Workplace & Productivity Project Management
2
jumpcloud-genaiOAuth
com.jumpcloud
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Cloud Platforms Security Developer Tools
2

Related MCP Servers

mcpPaylocity
Databases ERP Systems Developer Tools
mz462
F
license
A
quality
D
maintenance
An MCP server that provides access to Paylocity API endpoints, allowing retrieval of employee data, earnings, company codes, local taxes, and pay statements.
Updated a year ago (2025-06-06 04:28 UTC)
6
TimePRO MCP Server
Project Management Workplace & Productivity App Automation
calumjs
F
license
A
quality
D
maintenance
An MCP server that wraps the TimePRO API, enabling AI assistants to automatically create, view, and manage timesheets for authenticated users. It provides tools for searching clients and projects, retrieving configuration defaults, and performing full CRUD operations on timesheet entries.
Updated 3 months ago (2026-06-03 09:35 UTC)
10
prismhr-mcp
ERP Systems Finance
nikulk2992-jpg
A
license
A
quality
C
maintenance
MCP server for PrismHR, enabling AI agents to automate payroll, benefits, compliance, and billing tasks with verified-schema tools and scope-gated consent.
Updated 4 months ago (2026-04-21 04:34 UTC)
18
3
MIT
ConnectWise API Gateway MCP
CRM Developer Tools Search
iflow-mcp
F
license
Not graded
quality
D
maintenance
This MCP server simplifies interaction with the ConnectWise Manage API through API discovery, execution, and a fast memory system for efficient workflows.
Updated 10 months ago (2025-11-14 08:26 UTC)
20

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/check-technologies/mcp-server-check'

If you have feedback or need assistance with the MCP directory API, please join our Discord server