R3PLICA AI Connector
REMOTE · MCP.R3PLICA.SPACE · 3 COMPONENTS
Catalog of certified digital replicas from premium design brands, for any MCP-compatible AI agent.
Available components
Last scanned (21 hours ago)
Scores higher than 19% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
Checks we ran (5)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
Checks we could not complete (6)
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.
- Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.
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.
- 6 Nov 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
- 25 Oct 26 −43
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → pass ▲ security
- First check of Authorization: partial security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 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
- 25 Sept 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
- 7 Sept 26 0
- Injection markers: unverified → pass ▲ security
- Stability: fail → pass ▲ security
- Authorization: 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. security
- Schema quality: unverified → fail ▼ functional
- Schema quality: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → good ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 6 Sept 26 0
- Tool safety: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- Schema quality: good → unverified ▼ functional
- Schema quality: fail → unverified ▼ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
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://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 | 14 Nov 2026 | 12 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 4331efc369308c860e0fa874a28575cf |
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.r3plica.space. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| space. | DS published | 51168 | 13 | Verified |
| r3plica.space. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://mcp.r3plica.space/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://mcp.r3plica.space/.well-known/oauth-protected-resource/mcp" | Header | Value |
|---|---|
| www-authenticate | Bearer realm="OAuth", resource_metadata="https://mcp.r3plica.space/.well-known/oauth-protected-resource/mcp" |
Protected resource metadata
| Document | https://mcp.r3plica.space/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.r3plica.space/mcp |
| Authorisation server | https://mcp.r3plica.space |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.r3plica.space/mcp | Auth required | 401 | |
| 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. 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 →
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.
How do I install the R3PLICA AI Connector MCP server?
R3PLICA AI Connector is a hosted endpoint at https://mcp.r3plica.space/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 · mcp.r3plica.space
claude mcp add --transport http space-r3plica-catalog 'https://mcp.r3plica.space/mcp'
What is the R3PLICA AI Connector MCP server?
R3PLICA AI Connector is an MCP server listed in the public MCP registry as space.r3plica/catalog. Catalog of certified digital replicas from premium design brands, for any MCP-compatible AI agent. This page covers its hosted endpoint (https://mcp.r3plica.space/mcp).
Is the R3PLICA AI Connector MCP server safe to use?
R3PLICA AI Connector scores 36 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 R3PLICA AI Connector MCP server expose?
R3PLICA AI Connector exposes 16 tools: product_list, product_search, product_get, product_compare, product_stats, and 11 more. Their descriptions and schemas cost roughly 2,263 tokens of context every time the server is loaded.
Does the R3PLICA AI Connector MCP server require authentication?
Yes. R3PLICA AI Connector asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the R3PLICA AI Connector MCP server still maintained?
R3PLICA AI Connector 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 R3PLICA AI Connector MCP server?
VerifyMCP ran 5 checks on R3PLICA AI Connector, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about R3PLICA AI Connector: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.