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.

dev.pages.matrix-compute-website/matrix-compute-mcp

REMOTE · MCP.MATRIX-COMPUTE.NET · 2 COMPONENTS

P2P GPU matrix multiply, exact cosine search, and PCA/SVD verified via Freivalds' algorithm.

61 Trust /100

Last scanned (17 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

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 Security60
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 882 tokens (~176/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_distributed_matmul" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 20 Nov 26 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 58

    First indexed and scored.

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 21 Nov 2026 · Probed https://mcp.matrix-compute.net/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.matrix-compute.net CN=YE2,O=Let's Encrypt,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA384 58e4b5f4145458d8e360936905870c75132
SANs: mcp.matrix-compute.net
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of mcp.matrix-compute.net. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
net. DS published 37331 13 Verified
matrix-compute.net. DS published 4850 8 Verified
mcp.matrix-compute.net. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.matrix-compute.net/mcp Verified 200
http (plaintext) http://mcp.matrix-compute.net/mcp HTTPS enforced 308 https://mcp.matrix-compute.net/mcp
MCP tools · 5 exposed · ~882 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
batch_similarity_search ~162

Runs exact cosine similarity search between query embeddings (M x D) and corpus embeddings (N x D) on distributed GPUs using OUTPUT_GRID_2D zero-reduction tiling.

NameTypeReqDescription
corpus_embeddings–yesFile path (.npy/.npz/.safetensors) or inline 2D array of shape (N, D).
dtypestring–Target GEMM precision.
output_pathstring–Optional file path (.npy/.safetensors) to save the full similarity matrix.
queries–yesFile path (.npy/.npz/.safetensors) or inline 2D array of shape (M, D).
top_kinteger–Number of top matching corpus indices and scores to return per query.

No output schema declared.

No examples provided.

compute_pca_svd ~154

Computes verified top-k Principal Component Analysis (PCA) / Singular Value Decomposition (SVD) on distributed GPU workers via randomized subspace iteration or stateful power iteration.

NameTypeReqDescription
centerboolean–Mean-center columns before decomposition (standard PCA).
kintegeryesNumber of top singular/principal components to extract.
matrix–yesFile path (.npy/.npz/.safetensors) or inline 2D array of shape (M, N).
methodstring–Decomposition algorithm ('randomized' or 'power_iteration').
output_pathstring–Optional output file path (.npz or .safetensors) to save U, S, Vt.

No output schema declared.

No examples provided.

estimate_job_cost ~228

Calculates exact upload/download network bandwidth (MB), task count, GFLOPs, and satoshi cost estimates for a distributed matrix multiplication C (m x n) = A (m x k) x B (k x n).

NameTypeReqDescription
dtypestring–Precision format ('fp32', 'fp16', 'bf16').
grid_colsinteger–Column partitions P_c when using output_grid_2d.
grid_rowsinteger–Row partitions P_r when using output_grid_2d.
kintegeryesInner dimension K (columns of A / rows of B).
mintegeryesRows of matrix A (M > 0).
nintegeryesColumns of matrix B (N > 0).
num_stripsinteger–Strip count when using outer_product_1d.
partitioning_strategystring–Matrix partitioning strategy.
sats_per_gflopnumber–Override worker price in satoshis per GFLOP.
tile_sizeinteger–Tile block size dimension.

No output schema declared.

No examples provided.

execute_distributed_matmul ~251

Executes verified distributed matrix multiplication C = A x B across decentralized GPU workers with dynamic Freivalds verification and L402 settlement. Accepts file paths (.npy, .npz, .safetensors) or inline 2D JSON arrays.

NameTypeReqDescription
dtypestring–Computation precision ('fp32', 'fp16', 'bf16').
matrix_a–yesFile path (.npy/.npz/.safetensors) or inline 2D array for matrix A (M x K).
matrix_b–yesFile path (.npy/.npz/.safetensors) or inline 2D array for matrix B (K x N).
output_pathstring–Optional output file path (.npy, .npz, or .safetensors) to write C.
partitioning_strategystring–Matrix partitioning topology.
tensor_key_astring–Optional tensor key when loading matrix_a from .safetensors or .npz.
tensor_key_bstring–Optional tensor key when loading matrix_b from .safetensors or .npz.
tile_sizeinteger–Optional tile block size override.

No output schema declared.

No examples provided.

get_network_status ~87

Queries the Matrix Compute discovery relay for live GPU worker availability, total VRAM capacity, confidential computing (TEE) enclaves, and sats_per_gflop pricing.

NameTypeReqDescription
max_price_per_gflopnumber–Maximum worker price filter in satoshis per GFLOP (optional).
min_vram_mbinteger–Minimum worker VRAM filter in MB (optional).

No output schema declared.

No examples provided.

Install

How do I install the dev.pages.matrix-compute-website/matrix-compute-mcp server?

dev.pages.matrix-compute-website/matrix-compute-mcp is a hosted endpoint at https://mcp.matrix-compute.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 · mcp.matrix-compute.net

# add to Claude Code
claude mcp add --transport http dev-pages-matrix-compute-website-matrix-compute- 'https://mcp.matrix-compute.net/mcp'
Common questions

What is the dev.pages.matrix-compute-website/matrix-compute-mcp server?

dev.pages.matrix-compute-website/matrix-compute-mcp is listed in the public MCP registry as dev.pages.matrix-compute-website/matrix-compute-mcp. P2P GPU matrix multiply, exact cosine search, and PCA/SVD verified via Freivalds' algorithm. This page covers its hosted endpoint (https://mcp.matrix-compute.net/mcp).

Is the dev.pages.matrix-compute-website/matrix-compute-mcp server safe to use?

dev.pages.matrix-compute-website/matrix-compute-mcp scores 61 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 dev.pages.matrix-compute-website/matrix-compute-mcp server expose?

dev.pages.matrix-compute-website/matrix-compute-mcp exposes 5 tools: get_network_status, estimate_job_cost, execute_distributed_matmul, batch_similarity_search, compute_pca_svd. Their descriptions and schemas cost roughly 882 tokens of context every time the server is loaded.

Does the dev.pages.matrix-compute-website/matrix-compute-mcp server require authentication?

No. We connected to dev.pages.matrix-compute-website/matrix-compute-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the dev.pages.matrix-compute-website/matrix-compute-mcp server still maintained?

dev.pages.matrix-compute-website/matrix-compute-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the dev.pages.matrix-compute-website/matrix-compute-mcp server?

VerifyMCP ran 12 checks on dev.pages.matrix-compute-website/matrix-compute-mcp, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about dev.pages.matrix-compute-website/matrix-compute-mcp: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.