Check MCP integration for AI agents.
Connect AI agents to Check through 3 structured actions, including get agency, validate address, and list agencies. Review authentication, inputs, workflows…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Check integration exposes
The Check Agent App exposes 3 provider-backed actions for finance and data work. Its current contract lets an authorized agent get one check tax agency by id, validate a us address using check's address validation endpoint, and list check tax agencies with optional id, jurisdiction, label, and page size filters. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Check account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Check capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_agencyREADGet one Check tax agency by ID.
INPUTS: id
validate_addressREVIEWValidate a US address using Check's address validation endpoint.
INPUTS: line1 / line2 / city / state / postalCode
list_agenciesREADList Check tax agencies with optional ID, jurisdiction, label, and page size filters.
INPUTS: ids / jurisdictions / labelContains / limit
INPUT CONTRACTS
Know what the action needs before it runs.
get_agency
idREQUIRED- The Check agency ID.
validate_address
line1REQUIRED- A street address line to validate with Check.
line2OPTIONAL- A second street address line to validate with Check.
cityREQUIRED- The city for the address to validate.
stateREQUIRED- The US state code for the address to validate.
postalCodeREQUIRED- The postal code for the address to validate.
list_agencies
idsOPTIONAL- The Check agency IDs to look up. Check accepts repeated id query parameters.
jurisdictionsOPTIONAL- The lowercase jurisdiction codes used to filter agencies.
labelContainsOPTIONAL- A case-insensitive substring filter applied to the agency label.
limitOPTIONAL- The number of agencies to return per page. Check allows up to 500.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Agency
Get one Check tax agency by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_agencyVerify with List Agencies
List Check tax agencies with optional ID, jurisdiction, label, and page size filters. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_agenciesSAFETY BOUNDARY
Operate Check with explicit limits
- Authorize Check with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Check data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Check rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Check task completed successfully.
CONNECTION MODEL
API key
Check API key sent as an Authorization Bearer token. Use a sandbox or production key from your Check account.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Check.