RipSeek
REMOTE · RIPSEEK.2CSTUDIO.APP
Live odds, expected value and chase cards for Collector Crypt graded card packs; recent pulls.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category E-commerce
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- Authorization
- 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.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
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 →
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.
- 21 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.
- 19 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.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 68
First indexed and scored.
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://ripseek.2cstudio.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=2cstudio.app | CN=WE1,O=Google Trust Services,C=US | 16 Nov 2026 | 14 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 36d31a6a7eb61c640e365dc3c62ed861 |
| SANs: 2cstudio.app, ripseek.2cstudio.app, *.ripseek.2cstudio.app | ||||||
| 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 ripseek.2cstudio.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| 2cstudio.app. | No DS | 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=63072000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ripseek.2cstudio.app/mcp | Verified | 200 | |
| http (plaintext) | http://ripseek.2cstudio.app/mcp | Inconclusive | 405 |
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 →
estimate_budget What a budget usually returns ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | yes | Budget in US$, e.g. 250. Must cover at least one pack. |
| code | string | yes | Pack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| packs | number | yes | – |
| play_safe | string | – | – |
| spent_usd | number | – | – |
No examples provided.
get_card One card in detail ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nft | string | yes | The card's NFT address (Solana, base58) from a search_cards result, e.g. 7xKX...q9Fz. |
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | – |
| image | string|null | – | – |
| nft | string | – | – |
| note | string | – | – |
| packs | array | yes | – |
| value_usd | number | – | – |
No examples provided.
get_pack One pack in detail ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | Pack code from list_packs, lowercase, e.g. pokemon_50, onepiece_250, soccer_100. |
| Name | Type | Req | Description |
|---|---|---|---|
| cards_left | object | – | Cards left per rarity. |
| most_valuable_now | array | – | – |
| note | string | – | – |
| pack | object | yes | – |
No examples provided.
list_packs List the packs ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Only packs of this category. 'Others' covers Lorcana, Riftbound, Dragon Ball and anime. Leave out for all packs. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| packs | array | yes | – |
| rules | string | – | – |
No examples provided.
list_recent_pulls What people just pulled ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| note | string | – | – |
| pulls | array | yes | – |
No examples provided.
search_cards Find a card in the packs ~218
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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'. |
| Name | Type | Req | Description |
|---|---|---|---|
| cards | array | yes | – |
| note | string | – | – |
No examples provided.
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.
remote · ripseek.2cstudio.app
claude mcp add --transport http 2cstudiodev-web-ripseek 'https://ripseek.2cstudio.app/mcp'
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.