Inspect your SendFox account and contact-list summaries using a personal access token. Search a provider-default page of lists or read a known list’s counts and engagement percentages. These three reads do not expose contact addresses, send campaigns or transactional email, change subscriptions, or provide managed OAuth.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
Read my SendFox account summary — sendfox.user.get |
Read |
Search SendFox contact lists — sendfox.lists.list |
Read |
Read a SendFox contact-list summary — sendfox.lists.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for SendFox, then enter the issued values in the connection form below.
- Sign in to SendFox and open Settings → API tokens (sendfox.com/account/oauth). Choose Create New Token, name it for this connection and copy it immediately. Enter it in SendFox personal access token here; do not use your login password or an OAuth client secret. The current API permits account and list reads on Free plans as well, but account restrictions still apply. Older transactional-only tokens do not authorize these account/list endpoints. Select user.get or lists.list, save and create an Tooluse.net API key scoped to the selected reads. Use a returned list ID with lists.get. Revoke the token in SendFox and create a replacement when rotating; this connection does not perform OAuth authorization or automatic refresh.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| SendFox personal access token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
Read my SendFox account summary — sendfox.user.get
Read your SendFox user ID, name, contact count and contact limit. Email addresses, login metadata and tokens are excluded. This endpoint is available across current plans; the provider still enforces restrictions on your account.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
This tool has no input parameters.
Full JSON Schema
Example input
{}
At most 1 provider requests per invocation; timeout: 30 seconds.
Search SendFox contact lists — sendfox.lists.list
Read one provider-default page of list IDs, names, subscriber counts, average open/click percentages and timestamps. Use query to narrow names. Returns the provider’s current_page, per_page and total when present. No undocumented page controls or automatic pagination are added, and no contact addresses are returned.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.query |
string | Required | Search text to narrow contact lists on the provider’s first/default page. | minLength: 1; maxLength: 500 |
Full JSON Schema
Example input
{
"query": {
"query": "Example"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Read a SendFox contact-list summary — sendfox.lists.get
Read a known list’s ID, name, subscribed/unsubscribed counts, average open/click percentages and timestamps. Obtain id from lists.list or the SendFox list URL. Does not fetch contacts, public descriptions, campaign HTML or send email.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.id |
integer | Required | The contact-list ID from lists.list or your SendFox list URL. | minimum: 1; maximum: 9007199254740991 |
Full JSON Schema
Example input
{
"path": {
"id": 42
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.