Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ComputeFirst

REMOTE · COMPUTEFIRST.NET

Free deterministic tools for math, data transforms, dates, text, statistics, finance, and units.

Available components

+3 this week 70 Trust /100

Last scanned (3 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1165 tokens (~77/item across 15 items; 15 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage73
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 5% of tool parameters carry a description.Partial
  • Structured output schemas are declared (27% of tools); any adoption earns full credit.Pass
Tool Safety83
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 1 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 30 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 26 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://computefirst.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=computefirst.net CN=WE1,O=Google Trust Services,C=US 29 Sept 2026 28 Dec 2026 ECDSA 256 ECDSA-SHA256 c70300b7570d0c661352f0623fe28a75
SANs: computefirst.net, www.computefirst.net, *.www.computefirst.net
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of computefirst.net. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
net. present 37331 13 Verified
computefirst.net. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://computefirst.net/mcp Verified 200
http (plaintext) http://computefirst.net/mcp HTTPS enforced 301 https://computefirst.net/mcp
MCP tools · 15 exposed · ~1,059 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activity ~45

The account's recent calls and outcomes; pass next as before for older ones. Without a key: signed_in:false.

NameTypeReqDescription
beforestring––
limitinteger––

No output schema declared.

No examples provided.

describe ~39

Input schema, limits and examples of one ComputeFirst catalog tool, by id and version.

NameTypeReqDescription
idstringyes–
versionstringyes–
NameTypeReqDescription
descriptionstring––
idstringyes–
input_schemaobjectyes–
versionstringyes–

No examples provided.

execute ~86

Run one ComputeFirst catalog tool by id and version with its JSON input. Returns the deterministic result and an unmeasured savings receipt. Limits: computefirst.net/docs#limits.

NameTypeReqDescription
idstringyes–
inputobjectyes–
modelstring–Optional: your model id, only so savings can be shown per model
versionstringyes–
NameTypeReqDescription
invitestring––
result–yes–
savingsobject––

No examples provided.

execute_batch ~149

Run 1–20 ComputeFirst catalog tools in one request. Optional bindings fill an input key from an earlier result (JSON Pointer); include_result:false omits an intermediate. Steps after a failed dependency are skipped; nothing is retried automatically. Each success is one execution. Inputs, results and response: 256 KiB each. A factory work budget can skip an item with batch_work_limit; finance and exact decimal power/root/expression tools use the full factory allowance. Send additional factory operations separately. Split refused work; successful items are never retried automatically.

NameTypeReqDescription
modelstring–Optional: your model id, only so savings can be shown per model
operationsarrayyes–
NameTypeReqDescription
invitestring––
resultsarrayyes–
summaryobjectyes–

No examples provided.

feedback ~68

Tell ComputeFirst what helped or went wrong (a missing tool fits request_tool). A stable request_id makes retries safe. Leave out secrets and raw data.

NameTypeReqDescription
categorystringyes–
execution_refstring––
messagestringyes–
request_idstringyes–

No output schema declared.

No examples provided.

list_saved_tools ~34

Tools saved in the account's library (id, version, note). Without a key: signed_in:false and no tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

profile ~32

The signed-in account: keys, privileges and tool-request status. Without a key: signed_in:false and the optional extras.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

remove_saved_tool ~41

Remove a tool id and version from the account's library. Without a key nothing changes.

NameTypeReqDescription
idstringyes–
versionstringyes–

No output schema declared.

No examples provided.

report_savings ~138

Optional, for the person: your model id and, if known, your own estimate of the tokens a call saved (estimated_tokens_saved). Returns its dollar value at public list prices; unknown stays null. A measured comparison adds task_id, baseline_id, baseline, actual, whole_task:true, execution_ref.

NameTypeReqDescription
actualobject––
baselineobject––
baseline_idstring––
estimated_tokens_savedobject––
execution_refstring––
modelstringyes–
providerstring––
task_idstring––
whole_task–––

No output schema declared.

No examples provided.

request_tool ~92

Ask for a tool that does not exist yet: the task, optionally example input and output. Optional contact_email (with email_consent:true), only if the person wants one email when it ships. Leave out secrets.

NameTypeReqDescription
contact_emailstring––
descriptionstringyes–
email_consentboolean––
example_inputstring––
example_outputstring––

No output schema declared.

No examples provided.

save_tool ~59

Save a tool id and version to the account's library, with an optional note (saving again replaces the note). Without a key nothing is saved.

NameTypeReqDescription
idstringyes–
notestring––
versionstringyes–

No output schema declared.

No examples provided.

savings ~46

Savings totals, optionally for one model: with a key, the account's measured and estimated totals; otherwise community verified totals. Unmeasured is not zero.

NameTypeReqDescription
modelstring––

No output schema declared.

No examples provided.

search ~88

Search the ComputeFirst catalog (computefirst.net/tools) with an English task. Returns up to 5 tools (3 by default) with id, version and a 0–1 score; a confident first match includes its input contract. No match: request_tool can ask for one.

NameTypeReqDescription
include_contractboolean––
limitinteger––
querystringyes–
NameTypeReqDescription
hintstring––
methodstring––
resultsarrayyes–

No examples provided.

sign_in ~96

Only when the person explicitly asks for a free account (consent:true): creates one for their email (unverified) and returns an agent key once, for saved tools, history, personal savings and a higher limit. The person stores the key in their client settings; do not repeat it in the conversation. newsletter:true only if they ask.

NameTypeReqDescription
consent–yes–
emailstringyes–
newsletterboolean––

No output schema declared.

No examples provided.

subscribe ~46

Subscribe an email to new-tool announcements, only when the person asks for them (consent:true). Every email has an unsubscribe link.

NameTypeReqDescription
consent–yes–
emailstringyes–

No output schema declared.

No examples provided.

Install

How do I install the ComputeFirst MCP server?

ComputeFirst is a hosted endpoint at https://computefirst.net/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · computefirst.net

# add to Claude Code
claude mcp add --transport http 321zz321-computefirst 'https://computefirst.net/mcp'
Common questions

What is the ComputeFirst MCP server?

ComputeFirst is an MCP server listed in the public MCP registry as io.github.321zz321/computefirst. Free deterministic tools for math, data transforms, dates, text, statistics, finance, and units. This page covers its hosted endpoint (https://computefirst.net/mcp).

Is the ComputeFirst MCP server safe to use?

ComputeFirst scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ComputeFirst MCP server expose?

ComputeFirst exposes 15 tools: search, describe, execute, execute_batch, savings, and 10 more. Their descriptions and schemas cost roughly 1,059 tokens of context every time the server is loaded.

Does the ComputeFirst MCP server require authentication?

No. We connected to ComputeFirst without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ComputeFirst MCP server still maintained?

ComputeFirst is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.