Inspect host uptime, operating-system identity and filesystem capacity using fixed SSH commands. Authenticate with exactly one of a dedicated restricted account’s password or private key; no arbitrary shell, forwarding or file transfer. Obtain and verify the server SHA-256 host-key fingerprint out of band. Output is capped at 32 KiB; one bounded native invocation, public addresses only, no retries.
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 |
|---|---|
Inspect host uptime — ssh.uptime |
Read |
Inspect operating system (uname -a) — ssh.system |
Read |
Inspect filesystem capacity (df -Pk) — ssh.disks |
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 SSH, then enter the issued values in the connection form below.
- Create a dedicated restricted SSH account on your server. Enable only the fixed uptime, uname -a and df -Pk inspection commands needed by that account. In Tooluse.net Tools → SSH → Connect enter its public hostname, port and username, then fill exactly one of SSH password or Private key (PEM/OpenSSH); leave the other blank. For a protected key, also fill Private key passphrase. Install its public key on the server when using key authentication. Obtain the server SHA-256 host-key fingerprint from a trusted administrator or local console and compare it out of band before entering it; do not trust a fingerprint obtained only from the first network connection. Save, allow only the needed commands and call examples using your Tooluse.net API key. No provider API key is needed. Server access is enforced by the dedicated account; no arbitrary shell, forwarding or file transfer is exposed. Public addresses only, at most 32 KiB output, and no automatic retries.
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 |
|---|---|
| Public hostname | Required |
| Port | Optional |
| Username | Required |
| SSH password (leave blank with a private key) | Optional |
| Private key (PEM/OpenSSH) | Optional |
| Private key passphrase | Optional |
| Server host-key fingerprint (SHA256:base64) | 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
Inspect host uptime — ssh.uptime
Run the fixed uptime command through the restricted SSH account and return stdout, stderr and exitCode. Password and private-key authentication both require a trusted host-key fingerprint. Output is limited to 32 KiB; no custom shell command or retries.
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: 15 seconds.
Inspect operating system (uname -a) — ssh.system
Run the fixed uname -a command through the restricted SSH account and return operating-system identity. No arbitrary shell arguments, forwarding or retries; output is limited to 32 KiB.
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: 15 seconds.
Inspect filesystem capacity (df -Pk) — ssh.disks
Run the fixed df -Pk command through the restricted SSH account and return filesystem capacity in POSIX kilobyte units. No arbitrary shell arguments, mount changes or retries; output is limited to 32 KiB.
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: 15 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.