# ScoreCompute CLI 0.14.2

A dependency-free Node.js 20+ client for the remote ScoreCompute MCP endpoint.
The archive is distributed by ScoreCompute, not published to the npm registry.
`npx` downloads and executes this client; calculations run on the selected server.
No scientific engine, CUDA runtime or contributor client is installed.

```sh
npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call check_arithmetic --arguments '{"expression":"0.1+0.2","claimed_value":0.3}'
npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call --list
```

For shell-independent JSON quoting, save arguments in `arguments.json` and use
`scorecompute-call check_arithmetic --stdin`. Pipe the file with
`cat arguments.json | ...` on Linux or `Get-Content -Raw arguments.json | ...`
in PowerShell. No arbitrary file path is sent to the service.

## Optional personal access

Anonymous calls remain available. For an optional manual key or a Pro API key,
set `SCORECOMPUTE_KEY_FILE` to that file's path; do not copy the secret into the
command, a URL, source code or a shell history. This is the only credential
configuration. Do not use the service's operator token.

```sh
chmod 600 /path/to/scorecompute-client.key
SCORECOMPUTE_KEY_FILE=/path/to/scorecompute-client.key npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call --access-status
```

PowerShell uses a file path too:

```powershell
$env:SCORECOMPUTE_KEY_FILE = 'C:\private\scorecompute-client.key'
npx --yes --package https://scorecompute.com/downloads/scorecompute-call-0.14.2.tgz scorecompute-call --access-status
```

Restrict the Windows file ACL to your account. The client checks POSIX group and
other permissions on Unix; it does not inspect Windows ACLs. The final file
must be regular, not a symlink, and at most 256 bytes. Its contents are one issued
`sc_client_` (manual) or `sc_paid_` (Pro) key followed by 43 base64url characters, optionally ending in LF or
CRLF. Billing-owner cookies and account recovery codes are never accepted. No JSON wrapper, spaces or second line is accepted. Keys are read for the
command and are not written to a configuration file or included in its output.

When a key is configured, its Authorization header can only go to the exact
`https://scorecompute.com` origin, or an explicitly selected loopback endpoint
for private testing. Another HTTPS origin, a subdomain or a different public port
is refused before a network request. Redirects remain refused.

`--access-status` makes one GET to `/api/access/status` on the selected origin.
It does not initialize MCP or start a calculation. It returns public access mode
or the key's daily limit, used attempts, remaining attempts and UTC reset time.
Pro status also includes the subscription expiry and, when supplied, the remaining HTTP request allowance. The status request counts toward the HTTP allowance, but does not consume a daily tool attempt.
No administrative mode is supported. A keyed attempt is counted once reserved
by the service even if its calculation subsequently fails. There is no automatic
refund or retry. A manual key has no paid entitlement. A Pro key follows the active subscription and published allowances; it does not reserve GPU capacity, change scientific results or create an SLA. Anonymous access remains subject to shared limits.

## Output and protocol

The CLI emits the complete MCP result as JSON. Tool errors are returned on
stdout with exit code 2; client, HTTP and protocol errors use stderr and exit 1.
Exit 0 means that a tool result or access status was returned, not that a
scientific verdict is positive. Inspect each result and its stated scope.
If a response reflects the current credential, the client refuses to print it.

Options: `--arguments JSON`, `--arguments -`, `--stdin`, `--list`,
`--access-status`, `--url URL`, `--timeout-ms 100..60000`, `--help`, `--version`.
Choose exactly one tool, `--list` or `--access-status`.

Default endpoint: `https://scorecompute.com/mcp`. Without a key, an explicit
`--url` can select another HTTPS endpoint or HTTP loopback server for private
testing. Embedded URL credentials are refused. Client name `ScoreComputeCLI`
and version are self-declared and can appear in the public activity stream.

Bounds: 64 KiB argument input; 2 MiB cumulative MCP response data; eight catalogue
pages / 1,024 tools; 16 KiB access-status response; 35-second command deadline by
default, plus at most one second for best-effort session deletion. The same key
is included during initialization, notification, tool call/list and session
DELETE. No retry or automatic stream resumption is attempted. A timeout does
not establish that server work stopped. Local key-file operations are bounded
in size but filesystem latency is controlled by the operating system.

JSON and SSE are supported, with session and protocol negotiation. This client
does not implement OAuth, stdio serving, elicitation, sampling, long-running
Tasks or a general-purpose MCP host.

Connection and limits: https://scorecompute.com/connect/
Privacy: https://scorecompute.com/privacy/
