# RigBase (remote · getrigbase.com)

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

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `getrigbase.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-getrigbase-rigbase/getrigbase.md), [page](https://verifymcp.io/servers/com-getrigbase-rigbase/getrigbase)

## Channel facts

- Endpoint: `https://getrigbase.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-getrigbase-rigbase 'https://getrigbase.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-getrigbase-rigbase": {
      "url": "https://getrigbase.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-getrigbase-rigbase": {
      "type": "http",
      "url": "https://getrigbase.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-getrigbase-rigbase]
url = "https://getrigbase.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-getrigbase-rigbase": {
      "type": "remote",
      "url": "https://getrigbase.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-getrigbase-rigbase --url 'https://getrigbase.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-getrigbase-rigbase:
    url: "https://getrigbase.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-getrigbase-rigbase": {
      "Transport": "http",
      "Url": "https://getrigbase.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-getrigbase-rigbase -t streamable-http -u 'https://getrigbase.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-getrigbase-rigbase": {
      "type": "http",
      "url": "https://getrigbase.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 70, +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.

### 2026-11-03 (score 69, +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.

### 2026-11-02 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-01 (score 68)

First indexed and scored.

## MCP tools (4)

### `search_builds` (~204 tokens)

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.

Input parameters:

- `currency` (string): Optional currency filter: EUR or USD.
- `gpu` (string): Substring to match in the GPUs field (e.g. "3090", "DGX Spark", "5090").
- `limit` (integer): Max builds to return (default 8, max 25).
- `max_price` (number): Maximum reported build cost (same currency as the build, usually EUR or USD).
- `min_vram_gb` (number): Minimum total VRAM / unified memory in GB.
- `model` (string): Substring to match a measured model name (e.g. "Qwen3.8", "gpt-oss 120B").

### `can_it_run` (~183 tokens)

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.

Input parameters:

- `count` (integer): How many identical GPUs / nodes (default 1).
- `gpu` (string, required): GPU or system name, e.g. "RTX 3090", "RTX 5090", "DGX Spark", "Apple Silicon Mac".
- `model` (string, required): Model name, e.g. "Qwen3.8 27B", "gpt-oss 120B", "Gemma 4 31B".
- `quant` (string): Optional quant for the estimate (default Q4_K_M). Avoid below Q4.

### `best_gpu_for_model` (~96 tokens)

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.

Input parameters:

- `limit` (integer): How many top results to return (default 5, max 15).
- `model` (string, required): Model name or substring, e.g. "Gemma 4 31B" or "Qwen3.8".

### `get_build` (~63 tokens)

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

Input parameters:

- `slug` (string, required): Build slug from a RigBase /builds/.../ URL.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-getrigbase-rigbase/getrigbase#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 69
- 2026-11-03: 69
- 2026-11-02: 68
- 2026-11-01: 68

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

## Links

- Remote endpoint: https://getrigbase.com/mcp
- Website: https://getrigbase.com/mcp-server/
- Changelog RSS feed: https://verifymcp.io/servers/com-getrigbase-rigbase/getrigbase.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getrigbase-rigbase/getrigbase.json
- HTML version of this page: https://verifymcp.io/servers/com-getrigbase-rigbase/getrigbase