Ripey
REMOTE · RIPEY.APP
Let your agent open a store, list digital products and share USDC checkout links. Test mode.
Available components
Last scanned (3 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
Recent critical change
Authorization (4 Nov 2026). See the changelog before you install this server.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_draft). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 842 tokens (~120/item across 7 items; 7 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 Management10
- Stability observed for 3 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
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 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.
- 4 Nov 26 −7
- Authorization: partial → fail ▼ critical
- The server rewrote its instructions, which are the text every model session reads security
- New tool “delete_draft”, which the server declares destructive security
- Schema quality: 740 → 842 ▼ functional
- “create_product” reworded the description of “delivery_url” cosmetic
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 72
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 5 Nov 2026 · Probed https://ripey.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ripey.app | CN=YR2,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 510a6b6983bafc3ab325f9de92293786182 |
| SANs: ripey.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ripey.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ripey.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'none'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ripey.app/mcp | Verified | 200 | |
| http (plaintext) | http://ripey.app/mcp | HTTPS enforced | 308 | https://ripey.app/mcp |
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 →
checkout_link Get a buy link ~75
Return a link where a buyer can purchase a published product (opens the store with the product selected). Pass the store's agent_key (returned by open_store).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | The store's agent key (rpy_…), returned by open_store |
| product_id | string | yes | Product id from list_products |
No output schema declared.
No examples provided.
create_product Draft a product ~183
Create a DRAFT product in the store. Nothing goes live: show the user the draft (name, description, price) and ask them to approve before calling publish. Pass the store's agent_key (returned by open_store).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | The store's agent key (rpy_…), returned by open_store |
| delivery_url | string | – | Optional https link buyers get after paying (file, repo, Notion page, ...). The owner can instead upload the file itself in the dashboard. |
| description | string | yes | One or two sentences buyers will read |
| name | string | yes | Product name, e.g. 'Inbox Triage' |
| price_usd | number | yes | Price in US dollars, paid in USDC (1 USDC = 1 USD) |
| type | string | – | What kind of product it is |
No output schema declared.
No examples provided.
delete_draft Delete a draft ~85
Delete an unpublished draft the user doesn't want. Published products can't be deleted this way. Pass the store's agent_key (returned by open_store).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | The store's agent key (rpy_…), returned by open_store |
| product_id | string | yes | Draft id from create_product, e.g. p_1a2b3c |
No output schema declared.
No examples provided.
list_products List products ~59
List the store's products with their id, price and status (draft or published). Pass the store's agent_key (returned by open_store).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | The store's agent key (rpy_…), returned by open_store |
No output schema declared.
No examples provided.
open_store Open a Ripey store ~136
Open a new Ripey store for the user. Ask for the store name and the user's email first. Optionally takes the user's Solana wallet address (public address only, never a secret key); in test mode a demo address is used if omitted. Returns the store URL, a private dashboard link, and an agent_key: pass it to the other Ripey tools on this same connection to manage the store.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The store owner's email | |
| name | string | yes | Store name, e.g. 'Atlas Works' |
| wallet | string | – | Optional Solana public address where sales are paid |
No output schema declared.
No examples provided.
publish Publish a draft ~89
Put an approved draft on the store so buyers can purchase it. Only call this after the user approves the draft. Pass the store's agent_key (returned by open_store).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | The store's agent key (rpy_…), returned by open_store |
| product_id | string | yes | Draft id from create_product, e.g. p_1a2b3c |
No output schema declared.
No examples provided.
sales_summary Sales summary ~85
Summarize the store's sales over the last N days (default 7): revenue, orders, customers and top products. Pass the store's agent_key (returned by open_store).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_key | string | yes | The store's agent key (rpy_…), returned by open_store |
| days | integer | – | How many days to look back (1-90) |
No output schema declared.
No examples provided.
How do I install the Ripey MCP server?
Ripey is a hosted endpoint at https://ripey.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 · ripey.app
claude mcp add --transport http app-ripey-ripey 'https://ripey.app/mcp'
What is the Ripey MCP server?
Ripey is an MCP server listed in the public MCP registry as app.ripey/ripey. Let your agent open a store, list digital products and share USDC checkout links. Test mode. This page covers its hosted endpoint (https://ripey.app/mcp).
Is the Ripey MCP server safe to use?
Ripey scores 67 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 Ripey MCP server expose?
Ripey exposes 7 tools: open_store, list_products, create_product, delete_draft, publish, and 2 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.
Does the Ripey MCP server require authentication?
No. We connected to Ripey without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Ripey MCP server still maintained?
Ripey 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.