Data247 MCP integration for AI agents.
Connect AI agents to Data247 through 5 structured actions, including check balance, append gender, and check dnc. Review authentication, inputs, workflows, a…
- ACTION CONTRACTS
- 5
- 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 Data247 integration exposes
The Data247 Agent App exposes 5 provider-backed actions for data, communication, and marketing work. Its current contract lets an authorized agent check the current data247 account balance, infer a probable gender from a first name using data247, and check a phone number against data247 do-not-call data. 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 Data247 account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Data247 capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
check_balanceREADCheck the current Data247 account balance.
append_genderREVIEWInfer a probable gender from a first name using Data247.
INPUTS: fname
check_dncREADCheck a phone number against Data247 Do-Not-Call data.
INPUTS: phone
get_carrier_typeREADDetermine whether a USA or Canadian phone number is mobile, landline, or VOIP.
INPUTS: phone
verify_phoneREVIEWVerify whether an international phone number is active.
INPUTS: phone
INPUT CONTRACTS
Know what the action needs before it runs.
append_gender
fnameREQUIRED- The first name to submit to Data247.
check_dnc
phoneREQUIRED- The phone number to submit to Data247.
get_carrier_type
phoneREQUIRED- The phone number to submit to Data247.
verify_phone
phoneREQUIRED- The phone number to submit to Data247.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Check Balance
Check the current Data247 account balance. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
check_balanceVerify with Check Dnc
Check a phone number against Data247 Do-Not-Call data. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
check_dncSAFETY BOUNDARY
Operate Data247 with explicit limits
- Authorize Data247 with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Data247 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 Data247 rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Data247 task completed successfully.
CONNECTION MODEL
API key
Data247 v3 API key sent with the key query parameter. The Data247 API manual describes API key usage: https://www.data247.com/api_user_manual
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
- 3
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 2
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 Data247.