# RipSeek (remote · ripseek.2cstudio.app)

Live odds, expected value and chase cards for Collector Crypt graded card packs; recent pulls.

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

## Components

- remote · `ripseek.2cstudio.app`: 70/100 (this document), [markdown](https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek.md), [page](https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek)

## Channel facts

- Endpoint: `https://ripseek.2cstudio.app/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-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1184 tokens (~197/item across 6 items; 6 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RipSeek MCP server?

RipSeek is a hosted endpoint at https://ripseek.2cstudio.app/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 2cstudiodev-web-ripseek 'https://ripseek.2cstudio.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "2cstudiodev-web-ripseek": {
      "url": "https://ripseek.2cstudio.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "2cstudiodev-web-ripseek": {
      "type": "http",
      "url": "https://ripseek.2cstudio.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.2cstudiodev-web-ripseek]
url = "https://ripseek.2cstudio.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "2cstudiodev-web-ripseek": {
      "type": "remote",
      "url": "https://ripseek.2cstudio.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add 2cstudiodev-web-ripseek --url 'https://ripseek.2cstudio.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  2cstudiodev-web-ripseek:
    url: "https://ripseek.2cstudio.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "2cstudiodev-web-ripseek": {
      "Transport": "http",
      "Url": "https://ripseek.2cstudio.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add 2cstudiodev-web-ripseek -t streamable-http -u 'https://ripseek.2cstudio.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "2cstudiodev-web-ripseek": {
      "type": "http",
      "url": "https://ripseek.2cstudio.app/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-21 (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-19 (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-18 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (6)

### `list_packs` (~151 tokens)

List the packs

Lists every live Collector Crypt graded-card pack with price, category, chance of each rarity, card value range per rarity, buyback rate, average value per dollar and popularity (pulls in the last 7 days), most popular first. Use it first to compare packs or to find a pack code; use get_pack for one pack's top cards and cards left, and search_cards to look for a specific card. Read-only, no sign-in; numbers are Collector Crypt's live mainnet data, at most 5 minutes old.

Input parameters:

- `category` (string): Only packs of this category. 'Others' covers Lorcana, Riftbound, Dragon Ball and anime. Leave out for all packs.

Output parameters:

- `note` (string)
- `packs` (array)
- `rules` (string)

### `get_pack` (~142 tokens)

One pack in detail

Shows one pack in detail: odds and value range per rarity, buyback rate, how many cards of each rarity are left, and the 10 most valuable cards in its pool right now with the chance per pack of pulling each one. Use it when the user names or picks a pack; use list_packs to compare packs and estimate_budget to see what spending a set amount on this pack usually returns. Read-only; pool cards are rescanned every few minutes and can be pulled by anyone at any time.

Input parameters:

- `code` (string, required): Pack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100.

Output parameters:

- `cards_left` (object): Cards left per rarity.
- `most_valuable_now` (array)
- `note` (string)
- `pack` (object)

### `search_cards` (~218 tokens)

Find a card in the packs

Finds Rare and Epic cards sitting in any pack's pool right now by name words and/or minimum value (e.g. 'charizard psa 10'), up to 25, most valuable first, with the pack each is in and the chance per pack of pulling that exact card. Use it when the user asks whether a card can be pulled or which pack holds the best cards; use get_card for one result's full detail (pass its nft) and list_recent_pulls for cards already pulled. Read-only; pools are rescanned every few minutes, Commons and Uncommons aren't indexed.

Input parameters:

- `category` (string): Only packs of this category. 'Others' covers Lorcana, Riftbound, Dragon Ball and anime. Leave out for all packs.
- `min_value` (number): Only cards worth at least this many US$, e.g. 500.
- `query` (string): Words that must all appear in the card name, any order, e.g. 'umbreon vmax' or 'psa 10 rookie'.

Output parameters:

- `cards` (array)
- `note` (string)

### `get_card` (~136 tokens)

One card in detail

Shows one Rare or Epic card that is in a pack pool right now: name, insured value, picture, and every pack it can come from with that pack's price and the chance per pack of pulling this exact card. Use it after search_cards, passing the nft field of a result; use search_cards when you only have a card name. Read-only; fails with a clear message if the card has just been pulled and left the pool.

Input parameters:

- `nft` (string, required): The card's NFT address (Solana, base58) from a search_cards result, e.g. 7xKX...q9Fz.

Output parameters:

- `card` (string)
- `image` (string|null)
- `nft` (string)
- `note` (string)
- `packs` (array)
- `value_usd` (number)

### `list_recent_pulls` (~205 tokens)

What people just pulled

Lists the newest pack openings on Collector Crypt across every site that sells its packs, newest first (from the latest ~200): card, insured value, rarity, pack and its price, how many times the pack price the card was worth, and when. Use it to show what people are really getting right now, optionally for one pack, one rarity or above a value; use search_cards for cards still waiting in a pool. Read-only; the feed is at most 30 seconds old and wallets are shortened.

Input parameters:

- `code` (string): Pack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100.
- `limit` (number): How many pulls to return, 1 to 50 (default 20).
- `min_value` (number): Only cards worth at least this many US$, e.g. 100.
- `rarity` (string): Only pulls of this rarity, e.g. epic.

Output parameters:

- `note` (string)
- `pulls` (array)

### `estimate_budget` (~171 tokens)

What a budget usually returns

Estimates what spending a budget on one pack usually returns: how many packs it buys, the average insured value pulled, the average cash back if every card is sold back, the average result, and the chance of at least one Rare or Epic. Use it when the user asks what to expect from spending an amount, or whether a pack is worth it; use get_pack for the pack's odds and top cards. Read-only; honest averages from Collector Crypt's live odds, not a promise, and real results swing a lot with few packs.

Input parameters:

- `budget` (number, required): Budget in US$, e.g. 250. Must cover at least one pack.
- `code` (string, required): Pack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100.

Output parameters:

- `average_cash_back_if_all_sold_usd` (number)
- `average_insured_value_pulled_usd` (number)
- `average_result_if_all_sold_usd` (number)
- `chance_at_least_one_epic_pct` (number)
- `chance_at_least_one_rare_or_epic_pct` (number)
- `note` (string)
- `pack` (string)
- `packs` (number)
- `play_safe` (string)
- `spent_usd` (number)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 68
- 2026-11-17: 68

## Common questions

### What is the RipSeek MCP server?

RipSeek is an MCP server listed in the public MCP registry as io.github.2cstudiodev-web/ripseek. Live odds, expected value and chase cards for Collector Crypt graded card packs; recent pulls. This page covers its hosted endpoint (https://ripseek.2cstudio.app/mcp).

### Is the RipSeek MCP server safe to use?

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

RipSeek exposes 6 tools: list_packs, get_pack, search_cards, get_card, list_recent_pulls, estimate_budget. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.

### Does the RipSeek MCP server require authentication?

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

### Is the RipSeek MCP server still maintained?

RipSeek 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 RipSeek MCP server?

VerifyMCP ran 12 checks on RipSeek, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about RipSeek: HTTPS. 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.

## Links

- Remote endpoint: https://ripseek.2cstudio.app/mcp
- Website: https://ripseek.2cstudio.app/blog/ripseek-mcp
- Changelog RSS feed: https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek.xml
- Changelog JSON feed: https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek.json
- HTML version of this page: https://verifymcp.io/servers/2cstudiodev-web-ripseek/ripseek
