eCommerce
holoring.eu
Provides information about HoloRing's brand, founder, technology, and product recommendations, directing shoppers to Shopify for purchases.
ENDPOINT 1
https://agents.holoring.eu/mcp
MCP server metadata
- Name
- holoring-expertise
- Version
- 0.1.1
Known tools 8
get_brand_profileReturn the public HoloRing identity, categories, technology summary, founder link and canonical commerce sources.
Inferred read-onlyget_founder_profileReturn source-cited public information about HoloRing founder Petr Hauschwitz without implying institutional endorsement.
Inferred read-onlyexplain_holographic_technologyExplain the holographic optical effect, classic engraving or durability boundary using approved wording.
Inferred read-onlyget_recommendation_guidanceMap a shopper's intent to a HoloRing product family, state caveats and hand current commerce lookup to Shopify.
Inferred read-onlyget_claim_evidenceReturn approved wording and public sources for a known founder claim.
Inferred read-onlylist_authoritative_sourcesList canonical Shopify, technology and independent founder-evidence sources by category.
Inferred read-onlycompare_engraving_methodsCompare classic precision laser engraving with holographic femtosecond laser nanostructuring.
Inferred read-onlyresolve_storefront_for_marketReturn the Czech or international Shopify storefront and commerce MCP endpoint.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.holoring-expertise]
url = "https://agents.holoring.eu/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"holoring-expertise": {
"type": "http",
"url": "https://agents.holoring.eu/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: holoring-expertise
Remote MCP URL: https://agents.holoring.eu/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"holoring-expertise": {
"url": "https://agents.holoring.eu/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"holoring-expertise": {
"type": "http",
"url": "https://agents.holoring.eu/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "holoring-expertise",
"transport": "streamable-http",
"url": "https://agents.holoring.eu/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.