# R3PLICA AI Connector (remote · mcp.r3plica.space)

Catalog of certified digital replicas from premium design brands, for any MCP-compatible AI agent.

- Trust score: 61/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.r3plica.space`: 61/100 (this document), [markdown](https://verifymcp.io/servers/space-r3plica-catalog/mcp.md), [page](https://verifymcp.io/servers/space-r3plica-catalog/mcp)
- remote · `mcp.r3plica.space`: 27/100, [markdown](https://verifymcp.io/servers/space-r3plica-catalog/mcp-2.md), [page](https://verifymcp.io/servers/space-r3plica-catalog/mcp-2)
- npm · `r3plica`: 27/100, [markdown](https://verifymcp.io/servers/space-r3plica-catalog/r3plica.md), [page](https://verifymcp.io/servers/space-r3plica-catalog/r3plica)

## Channel facts

- Endpoint: `https://mcp.r3plica.space/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.3.3`

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

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - 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 2263 tokens (~141/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http space-r3plica-catalog https://mcp.r3plica.space/mcp
```

### Codex

```toml
[mcp_servers.space-r3plica-catalog]
url = "https://mcp.r3plica.space/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add space-r3plica-catalog --url https://mcp.r3plica.space/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  space-r3plica-catalog:
    url: "https://mcp.r3plica.space/mcp"
```

### Other

```json
{
  "mcpServers": {
    "space-r3plica-catalog": {
      "type": "http",
      "url": "https://mcp.r3plica.space/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-08-03 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 59, +2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 57, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 59, +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-07-28 (score 58, +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-07-27 (score 57, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (16)

### `product_list` (~388 tokens)

List R3PLICA products with optional structured filters (brand, category, collection, designer, year). Use this for browsing/filtering by attribute (e.g. 'all Cassina sofas', 'chairs from 2020'); use product_search instead when the user gives a free-text query or keyword. Triggers: 'show me <category>', 'list <brand> products', 'browse the catalog', 'mostrami <categoria>', 'fammi vedere i prodotti di <brand>', 'sfoglia il catalogo'. Default limit is 50 products per call — raise via the `limit` argument if needed. Returns a sequence of structured markdown product cards: each has a `###` heading with name and brand, an inline `![](thumbnail_url)` markdown image, a 2-column markdown table with the spec rows (Designer, Year, Collection, Dimensions, Materials, Category), a blockquote description, and a catalog deep-link. CRITICAL when replying to the user: emit the cards VERBATIM as returned. Keep every `###` heading, the full markdown image line, the markdown table (`| ... |`), the blockquote, and the `[View on R3PLICA catalog →](url)` link untouched. Do NOT flatten the table into a comma-separated paragraph. Do NOT rewrite specs as prose. Do NOT construct alternate URLs from the asset_name — the CDN prefix is `SM_` (Static Mesh) for all products regardless of brand; pattern-matching brand-derived prefixes produces broken links.

Input parameters:

- `brand` (string)
- `category` (string)
- `collection` (string)
- `designer` (string)
- `hasFinish` (string)
- `limit` (number)
- `order` (string)
- `page` (number)
- `sort` (string)
- `year` (string)

### `product_search` (~251 tokens)

Search R3PLICA products by free-text query. Returns structured markdown product cards (heading + thumbnail image + spec table + description + catalog link). Use this when the user gives a keyword or descriptive phrase (e.g. 'find a curved velvet sofa', 'lounge chairs'); use product_list when filtering purely by structured attributes. Triggers: 'find <x>', 'search for <x>', 'do you have <x>', 'I'm looking for <x>', 'cerca <x>', 'trova <x>', 'avete <x>', 'sto cercando <x>'. Default limit is 50. CRITICAL: preserve the markdown structure verbatim — keep the `![](url)` image lines and the tables, do not flatten into prose. NEVER reconstruct image URLs from asset_name yourself — the CDN file prefix is constant (`SM_`), not brand-derived.

Input parameters:

- `brand` (string)
- `category` (string)
- `designer` (string)
- `hasFinish` (string)
- `limit` (number)
- `order` (string)
- `query` (string, required)
- `sort` (string)
- `year` (string)

### `product_get` (~87 tokens)

Get detailed information about a specific product. Returns one structured markdown card (heading + `![](thumbnail_url)` image + spec table + description + catalog link). CRITICAL: preserve the markdown image and table verbatim. Do not flatten into prose. Do NOT reconstruct the thumbnail URL from asset_name — copy the provided `![](url)` line as-is.

Input parameters:

- `id` (string, required)

### `product_compare` (~126 tokens)

Compare two products side by side. Returns two markdown cards under `## Product 1` / `## Product 2`, each with a 2-column spec table. Triggers: 'compare X and Y', 'X vs Y', 'which is bigger/better', 'differenza tra X e Y', 'confronta X e Y', 'meglio X o Y'. CRITICAL: preserve both card structures verbatim — the side-by-side tables are how the user visually compares.

Input parameters:

- `id1` (string, required)
- `id2` (string, required)

### `product_stats` (~94 tokens)

Catalog statistics grouped by category, brand, designer or year. Returns aggregate counts only — small, fixed-size payload. Triggers: 'how many products', 'catalog breakdown', 'how many sofas/chairs', 'products per brand', 'quanti prodotti', 'quanti per brand', 'statistiche catalogo', 'quante sedie avete'.

Input parameters:

- `brand` (string)
- `group_by` (string)

### `brand_list` (~79 tokens)

List all R3PLICA partner brands (default limit 200). Triggers: 'what brands do you have', 'list the brands', 'which brands are on R3PLICA', 'quali brand avete', 'elenca i brand', 'che marche ci sono'.

Input parameters:

- `country` (string)
- `limit` (number)

### `brand_get` (~69 tokens)

Detailed information about a specific brand by name (description, country, designers, catalog presence). Triggers: 'tell me about <brand>', 'info on <brand>', 'who is <brand>', 'parlami di <brand>', 'chi è <brand>'.

Input parameters:

- `name` (string, required)

### `brand_search` (~77 tokens)

Search R3PLICA brands by name substring. Use when the user mentions a brand but you need to resolve the exact catalog name. Triggers: 'find the brand <x>', 'is <x> on R3PLICA', 'cerca il brand <x>', 'avete <x>'.

Input parameters:

- `query` (string, required)

### `product_collection_list` (~118 tokens)

List product collections (a brand's product lines, e.g. 'Eclipse', 'Charisma'). Default limit 100. A product collection is a named product line within a brand — NOT a finish set (use finish_collection_* for those). Triggers: 'what collections does <brand> have', 'list <brand> product lines', 'quali collezioni ha <brand>', 'le linee di <brand>'.

Input parameters:

- `brand` (string)
- `limit` (number)
- `page` (number)

### `product_collection_search` (~57 tokens)

Search product collections by name substring (product lines, not finish sets). Triggers: 'find the <x> collection', 'cerca la collezione <x>', 'la linea <x>'.

Input parameters:

- `query` (string, required)

### `finish_collection_list` (~272 tokens)

List R3PLICA finish collections (e.g. fabric, leather, wood, marble, metal sets sold as one asset). Optional brand/category filters. Default limit 5 collections per call — each can contain 30-50 individual finishes once enriched, so keep limits modest. TERMINOLOGY: a `finish_collection` is the asset sold on the platform; it contains many individual `finishes` inside `finish_details[]`. Do NOT call individual finishes 'variants' — 'variant' is reserved for product dimensional/additional variants. Response shape: { _meta: { terminology, asset_paths, deep_link_routes, thumbnail_rule, catalog_url_rule }, data: [collections] }. Each collection has a `catalog_url` and a flat `finish_directory[]`; each finish in `finish_details[]` carries a `thumbnail_url`. CRITICAL when embedding images: use the `thumbnail_url` field VERBATIM. NEVER construct CDN URLs from `asset_name` yourself — the file prefix is `MI_` (Material Instance) for ALL finishes regardless of brand; agents that infer brand-derived prefixes like `MO_`/`BO_` produce broken links.

Input parameters:

- `brand` (string)
- `category` (string)
- `limit` (number)
- `page` (number)

### `finish_collection_search` (~79 tokens)

Search finish collections by name. Default limit 10. Response includes `_meta.terminology` + `_meta.asset_paths` notes and each finish in `finish_details[]` carries a `thumbnail_url`. CRITICAL: never construct CDN URLs from asset_name yourself — use the `thumbnail_url` field as-is.

Input parameters:

- `query` (string, required)

### `finish_collection_get` (~181 tokens)

Get a finish collection detail with all its individual finishes. Response includes `catalog_url` (deep-link to the collection page on catalog.r3plica.space), `finish_directory[]` (compact flat list with name + mongo_id + asset_name + thumbnail_url — designed to survive context truncation), and `finish_details[]` (full nested data). CRITICAL when generating documents/artifacts: copy the `thumbnail_url` and `catalog_url` fields VERBATIM. Do NOT construct catalog URLs yourself — the route is `/go/finish/<mongo_id>` (singular 'finish', NOT 'finish-collection' or 'finish/collection'). Do NOT construct thumbnail URLs from asset_name. If you need data for a single finish whose parent collection has been pushed out of context, call `finish_get` instead.

Input parameters:

- `id` (string, required)

### `finish_get` (~125 tokens)

Look up a single individual finish by its mongo_id. Returns its exact `name` (e.g. 'Saffron', 'Walnut'), `asset_name`, `thumbnail_url`, `catalog_url` (deep-link to the PARENT collection page — individual finishes don't have their own page), and parent finish collection identity. Use this when composing documents and you need the precise URL for a specific finish without re-fetching the whole collection — avoids the URL-guessing trap when the collection has already been pushed out of your context window.

Input parameters:

- `mongo_id` (string, required)

### `finish_search` (~120 tokens)

Search individual finishes across all collections by finish name (e.g. 'Walnut', 'Saffron') or asset_name substring. Optional `collection` filter narrows by finish collection name. Default limit 50. Returns each match with `asset_name`, `thumbnail_url`, and parent collection identity attached. Use when you know the finish name but not its mongo_id — e.g. 'find me the Walnut finish in the Bolzan Wood collection'.

Input parameters:

- `collection` (string)
- `limit` (number)
- `query` (string, required)

### `style_guide_get` (~140 tokens)

Return the R3PLICA brand and output style guide as markdown. Covers card structure, typography, color palette, image aspect ratio (always square), hierarchy, mandatory link footer, and ready-to-copy empty card scaffolds (product card, finish swatch, both markdown and HTML). CALL THIS FIRST whenever you are about to generate any document, report, artifact or branded output about R3PLICA catalog content. The guide ensures outputs feel consistent across users and align with the platform's visual identity. Costs ~2KB of context but saves the conversation from inconsistent formatting and from inventing fields the platform doesn't expose (prices, lead times, certifications).

## Diagnostics

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

## Score history

- 2026-08-03: 61
- 2026-08-02: 60
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 57
- 2026-07-29: 59
- 2026-07-28: 58
- 2026-07-27: 57
- 2026-07-26: 57

## Links

- Remote endpoint: https://mcp.r3plica.space/mcp
- Website: https://www.r3plica.space/integrations/mcp
- Changelog RSS feed: https://verifymcp.io/servers/space-r3plica-catalog/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/space-r3plica-catalog/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/space-r3plica-catalog/mcp