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.

RigBase

REMOTE · GETRIGBASE.COM

Measured local-LLM tok/s on home AI rigs. Search builds, can-it-run, best GPU; sourced + linked.

Available components

70 Trust /100

Last scanned (4 hours ago)

Scores higher than 55% of remote servers

Reachable. Last reached 5 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 Security74
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 684 tokens (~171/item across 4 items; 4 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 Management13
  • Stability observed for 4 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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 2 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 1 Nov 26 68

    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 5 Nov 2026 · Probed https://getrigbase.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getrigbase.com CN=WE1,O=Google Trust Services,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 8ae5177d92a75332139afe4bf33ea60c
SANs: getrigbase.com
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 getrigbase.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
getrigbase.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://getrigbase.com/mcp Verified 200
http (plaintext) http://getrigbase.com/mcp HTTPS enforced 301 https://getrigbase.com/mcp
MCP tools · 4 exposed · ~546 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
best_gpu_for_model ~96

Return the fastest measured RigBase result for a model, plus tok/s per euro where a build cost or known GPU street price exists. Includes source credit and canonical URL.

NameTypeReqDescription
limitinteger–How many top results to return (default 5, max 15).
modelstringyesModel name or substring, e.g. "Gemma 4 31B" or "Qwen3.8".

No output schema declared.

No examples provided.

can_it_run ~183

Ask whether a given GPU setup can run a model. Returns measured RigBase results when available; otherwise a VRAM-fit estimate clearly labelled as an estimate (weights arithmetic, not a measured speed). Advises against quants below Q4. Always includes source credit and URLs for measured rows.

NameTypeReqDescription
countinteger–How many identical GPUs / nodes (default 1).
gpustringyesGPU or system name, e.g. "RTX 3090", "RTX 5090", "DGX Spark", "Apple Silicon Mac".
modelstringyesModel name, e.g. "Qwen3.8 27B", "gpt-oss 120B", "Gemma 4 31B".
quantstring–Optional quant for the estimate (default Q4_K_M). Avoid below Q4.

No output schema declared.

No examples provided.

get_build ~63

Fetch one RigBase build by slug (e.g. "dual-3090-ryzen-3700x"). Returns parts, measured results, source credit and canonical URL.

NameTypeReqDescription
slugstringyesBuild slug from a RigBase /builds/.../ URL.

No output schema declared.

No examples provided.

search_builds ~204

Search RigBase measured home AI builds. Filter by GPU name, model name, minimum VRAM (GB), and/or maximum build cost. Returns top matches with tok/s, quant, engine, source credit and canonical getrigbase.com URL. Never invents numbers.

NameTypeReqDescription
currencystring–Optional currency filter: EUR or USD.
gpustring–Substring to match in the GPUs field (e.g. "3090", "DGX Spark", "5090").
limitinteger–Max builds to return (default 8, max 25).
max_pricenumber–Maximum reported build cost (same currency as the build, usually EUR or USD).
min_vram_gbnumber–Minimum total VRAM / unified memory in GB.
modelstring–Substring to match a measured model name (e.g. "Qwen3.8", "gpt-oss 120B").

No output schema declared.

No examples provided.

Install

How do I install the RigBase MCP server?

RigBase is a hosted endpoint at https://getrigbase.com/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 · getrigbase.com

# add to Claude Code
claude mcp add --transport http com-getrigbase-rigbase 'https://getrigbase.com/mcp'
Common questions

What is the RigBase MCP server?

RigBase is an MCP server listed in the public MCP registry as com.getrigbase/rigbase. Measured local-LLM tok/s on home AI rigs. Search builds, can-it-run, best GPU; sourced + linked. This page covers its hosted endpoint (https://getrigbase.com/mcp).

Is the RigBase MCP server safe to use?

RigBase 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 RigBase MCP server expose?

RigBase exposes 4 tools: search_builds, can_it_run, best_gpu_for_model, get_build. Their descriptions and schemas cost roughly 546 tokens of context every time the server is loaded.

Does the RigBase MCP server require authentication?

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

Is the RigBase MCP server still maintained?

RigBase 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.