R3PLICA AI Connector
REMOTE · MCP.R3PLICA.SPACE · 3 COMPONENTS · SCANNED AUG 3
Catalog of certified digital replicas from premium design brands, for any MCP-compatible AI agent.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability70
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.r3plica.space
claude mcp add --transport http space-r3plica-catalog https://mcp.r3plica.space/mcp
[mcp_servers.space-r3plica-catalog] url = "https://mcp.r3plica.space/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"space-r3plica-catalog": {
"type": "remote",
"url": "https://mcp.r3plica.space/mcp",
"enabled": true
}
}
} openclaw mcp add space-r3plica-catalog --url https://mcp.r3plica.space/mcp --transport streamable-http
mcp_servers:
space-r3plica-catalog:
url: "https://mcp.r3plica.space/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 1 Aug 26 +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.
- 31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 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.
- 28 Jul 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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 57
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 3 Aug 2026 · Probed https://mcp.r3plica.space/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=r3plica.space | CN=WE1,O=Google Trust Services,C=US | 19 Jul 2026 | 17 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 17563af7a8c30f310e729e2956bb0270 |
| SANs: r3plica.space, mcp.r3plica.space, *.mcp.r3plica.space | ||||||
| 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 |
DNSSEC insecure
Validation of mcp.r3plica.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| space. | present | 51168 | 13 | Verified |
| r3plica.space. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.r3plica.space/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.r3plica.space/mcp | HTTPS enforced | 301 | https://mcp.r3plica.space/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.
brand_get ~69
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>'.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | — |
No output schema declared.
No examples provided.
brand_list ~79
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | — | — |
| limit | number | — | — |
No output schema declared.
No examples provided.
brand_search ~77
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>'.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | — |
No output schema declared.
No examples provided.
finish_collection_get ~181
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | — |
No output schema declared.
No examples provided.
finish_collection_list ~272
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| category | string | — | — |
| limit | number | — | — |
| page | number | — | — |
No output schema declared.
No examples provided.
finish_collection_search ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | — |
No output schema declared.
No examples provided.
finish_get ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mongo_id | string | yes | — |
No output schema declared.
No examples provided.
finish_search ~120
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| collection | string | — | — |
| limit | number | — | — |
| query | string | yes | — |
No output schema declared.
No examples provided.
product_collection_list ~118
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>'.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| limit | number | — | — |
| page | number | — | — |
No output schema declared.
No examples provided.
product_collection_search ~57
Search product collections by name substring (product lines, not finish sets). Triggers: 'find the <x> collection', 'cerca la collezione <x>', 'la linea <x>'.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | — |
No output schema declared.
No examples provided.
product_compare ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id1 | string | yes | — |
| id2 | string | yes | — |
No output schema declared.
No examples provided.
product_get ~87
Get detailed information about a specific product. Returns one structured markdown card (heading + `` 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 `` line as-is.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | — |
No output schema declared.
No examples provided.
product_list ~388
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 `` 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| category | string | — | — |
| collection | string | — | — |
| designer | string | — | — |
| hasFinish | string | — | — |
| limit | number | — | — |
| order | string | — | — |
| page | number | — | — |
| sort | string | — | — |
| year | string | — | — |
No output schema declared.
No examples provided.
product_search ~251
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 `` 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.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| category | string | — | — |
| designer | string | — | — |
| hasFinish | string | — | — |
| limit | number | — | — |
| order | string | — | — |
| query | string | yes | — |
| sort | string | — | — |
| year | string | — | — |
No output schema declared.
No examples provided.
product_stats ~94
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'.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | — | — |
| group_by | string | — | — |
No output schema declared.
No examples provided.
style_guide_get ~140
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).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.