# Ripey (remote · ripey.app)

Let your agent open a store, list digital products and share USDC checkout links. Test mode.

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

> **Recent critical change**: Authorization (2026-11-04). See the changelog below before you install this server.

## Components

- remote · `ripey.app`: 67/100 (this document), [markdown](https://verifymcp.io/servers/app-ripey-ripey/ripey.md), [page](https://verifymcp.io/servers/app-ripey-ripey/ripey)

## Channel facts

- Endpoint: `https://ripey.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.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**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_draft).
  - HTTPS is enforced; there's no plaintext access path.
  - 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**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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.
  - All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http app-ripey-ripey 'https://ripey.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-ripey-ripey": {
      "url": "https://ripey.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-ripey-ripey": {
      "type": "http",
      "url": "https://ripey.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-ripey-ripey]
url = "https://ripey.app/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add app-ripey-ripey --url 'https://ripey.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-ripey-ripey:
    url: "https://ripey.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-ripey-ripey": {
      "Transport": "http",
      "Url": "https://ripey.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-ripey-ripey -t streamable-http -u 'https://ripey.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-ripey-ripey": {
      "type": "http",
      "url": "https://ripey.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-05 (score 67, +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.

### 2026-11-04 (score 66, −7)

- [critical regression] Authorization: partial → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] New tool “delete_draft”, which the server declares destructive
- [functional regression] Schema quality: 740 → 842
- [cosmetic] “create_product” reworded the description of “delivery_url”

### 2026-11-03 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 72)

First indexed and scored.

## MCP tools (7)

### `open_store` (~136 tokens)

Open a Ripey store

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.

Input parameters:

- `email` (string, required): The store owner's email
- `name` (string, required): Store name, e.g. 'Atlas Works'
- `wallet` (string): Optional Solana public address where sales are paid

### `list_products` (~59 tokens)

List products

List the store's products with their id, price and status (draft or published). Pass the store's agent_key (returned by open_store).

Input parameters:

- `agent_key` (string, required): The store's agent key (rpy_…), returned by open_store

### `create_product` (~183 tokens)

Draft a product

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

Input parameters:

- `agent_key` (string, required): 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, required): One or two sentences buyers will read
- `name` (string, required): Product name, e.g. 'Inbox Triage'
- `price_usd` (number, required): Price in US dollars, paid in USDC (1 USDC = 1 USD)
- `type` (string): What kind of product it is

### `delete_draft` (~85 tokens)

Delete a draft

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

Input parameters:

- `agent_key` (string, required): The store's agent key (rpy_…), returned by open_store
- `product_id` (string, required): Draft id from create_product, e.g. p_1a2b3c

### `publish` (~89 tokens)

Publish a draft

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

Input parameters:

- `agent_key` (string, required): The store's agent key (rpy_…), returned by open_store
- `product_id` (string, required): Draft id from create_product, e.g. p_1a2b3c

### `checkout_link` (~75 tokens)

Get a buy link

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

Input parameters:

- `agent_key` (string, required): The store's agent key (rpy_…), returned by open_store
- `product_id` (string, required): Product id from list_products

### `sales_summary` (~85 tokens)

Sales summary

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

Input parameters:

- `agent_key` (string, required): The store's agent key (rpy_…), returned by open_store
- `days` (integer): How many days to look back (1-90)

## Diagnostics

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

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 73
- 2026-11-02: 72

## Common questions

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

## Links

- Remote endpoint: https://ripey.app/mcp
- Website: https://ripey.app/solutions/agents
- Changelog RSS feed: https://verifymcp.io/servers/app-ripey-ripey/ripey.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-ripey-ripey/ripey.json
- HTML version of this page: https://verifymcp.io/servers/app-ripey-ripey/ripey