ScoreCompute is a remote MCP server for scientific calculation. Add the endpoint, review the available tools, then ask for a real calculation. Each engine can be called directly; composition is optional.
Open your connector settings, add a custom connector called ScoreCompute, and paste the MCP URL. Enable it for the conversation when needed. Organization policies can restrict this setting.
Keep the full endpoint above for all tools, or choose a focused connection. Every selected tool retains its complete schema, validation and limits.
Five explicit claim domains, one tool and a signed calculation receipt.
https://scorecompute.com/mcp?tools=verify_claim
1.3 kB of tool definitions instead of 175.1 kB for the full catalogue, measured on transport 0.15.0. These are JSON bytes, not model-token counts or calculation speed.
Choosing other tools
Use ?tools=name1,name2 with one to eight distinct names from the catalogue. Start a new MCP connection after changing your selection. This is a discovery filter, not a permission boundary; the public endpoint remains available. A composite tool can still run its documented internal engines.
Paste the focused URL wherever the setup instructions below use the full MCP URL. Authentication and daily quotas work in the same way.
ONE COMMAND / ANY DIRECT TOOL
Call an engine from your terminal.
With Node.js 20+ and npm, this downloadable client calls the remote MCP service. It installs no Rust engine or GPU stack on your machine.
Change the tool name and arguments to call another engine independently. Use --list to discover the current catalogue. For PowerShell or larger inputs, pipe a JSON file with --stdin.
The archive is served here, not published in the npm registry. Calls use shared public capacity; the self-declared client name is visible in the observatory.
OPTIONAL / CONTROL YOUR CALL BUDGET
Connect your Pro key to your workflow.
Public access stays available without a key. Pro provides a personal key, a daily allowance of submitted tool-call attempts and an account to manage access. The daily limit is shared across the web gateway and MCP; discovery and quota checks do not consume it.
Both plans use shared compute and the same scientific methods. An unknown tool, refused argument, inconclusive result or later failure can consume an admitted attempt. A key does not reserve CPU or GPU capacity or guarantee availability.
Your browser account manages the subscription; it does not authenticate calculations in the web demonstrations. To use your Pro allowance, configure your personal API key in your MCP client or API requests. Open the step-by-step Pro connection guide.
With client 0.14.2, set SCORECOMPUTE_KEY_FILE to the private key file provided to you. Use scorecompute-call --access-status to confirm paid: true, tier: pro and inspect its UTC quota. After replacing a key, reconnect the MCP server so it starts a new authenticated session. Keep the secret out of prompts, URLs and public configurations.
The public HTTPS endpoint uses Streamable HTTP. No ScoreCompute package or GPU installation is needed on your computer. Call a scientific engine directly, or choose a composition tool for a larger task.
Review the tools your assistant enables. Public access requires no ScoreCompute API key; your client or organization can still require approval.
The downloadable contributor client lends approved compute workloads to the network. It is not required to call MCP tools and does not install each scientific engine as a separate local server.
Use ScoreCompute check_arithmetic to check whether 0.1 + 0.2 equals 0.3. Return the actual tool result, its comparison mode and its limits.
Look for the returned expression, exact value, comparison mode and scope. Listing the tools is a connection check; receiving a tool result establishes that this call completed.
These are documented setup instructions, not a claim that your client or account has been tested. If no tools appear, check the client’s MCP log and service status.