# Hilo Studio (remote · hilostudiolab.com)

Madrid studio for branding and interactive 3D web: services, prices, work, Lab demos, quotes.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `hilostudiolab.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-hilostudiolab-studio/hilostudiolab.md), [page](https://verifymcp.io/servers/com-hilostudiolab-studio/hilostudiolab)

## Channel facts

- Endpoint: `https://hilostudiolab.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 73/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1687 tokens (~129/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hilo Studio MCP server?

Hilo Studio is a hosted endpoint at https://hilostudiolab.com/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 com-hilostudiolab-studio 'https://hilostudiolab.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-hilostudiolab-studio": {
      "url": "https://hilostudiolab.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-hilostudiolab-studio": {
      "type": "http",
      "url": "https://hilostudiolab.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-hilostudiolab-studio]
url = "https://hilostudiolab.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-hilostudiolab-studio --url 'https://hilostudiolab.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hilostudiolab-studio:
    url: "https://hilostudiolab.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-hilostudiolab-studio": {
      "Transport": "http",
      "Url": "https://hilostudiolab.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-hilostudiolab-studio -t streamable-http -u 'https://hilostudiolab.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-hilostudiolab-studio": {
      "type": "http",
      "url": "https://hilostudiolab.com/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-04 (score 84, +1)

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

### 2026-11-01 (score 83, +1)

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

### 2026-10-30 (score 82, +1)

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

### 2026-10-28 (score 81, +1)

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

### 2026-10-26 (score 80, +1)

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

### 2026-10-24 (score 79, +1)

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

### 2026-10-22 (score 78, +1)

- [security] Tool “hilo_find_relevant_work” rewrote its description, which is the text the model reads
- [security] Tool “hilo_list_blog_posts” rewrote its description, which is the text the model reads
- [cosmetic] “hilo_get_case_study” reworded the description of “slug”
- [cosmetic] “hilo_get_service” reworded the description of “slug”

### 2026-10-20 (score 77, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “hilo_recommend”
- [cosmetic] “hilo_request_quote” added an optional parameter “lang”
- [cosmetic] “hilo_request_quote” added an optional parameter “objective”
- [cosmetic] “hilo_request_quote” added an optional parameter “price_fit”
- [cosmetic] “hilo_request_quote” added an optional parameter “situation”
- [cosmetic] “hilo_request_quote” added an optional parameter “timing”

## MCP tools (13)

### `hilo_studio_overview` (~74 tokens)

Studio overview

Who Hilo Studio is: what it does, where it is, languages, how it works, awards and how to contact it. Call this first for general questions.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.

### `hilo_list_services` (~66 tokens)

List services

All services Hilo Studio offers, with a short summary, starting price and URL. Use hilo_get_service for the full detail of one.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.

### `hilo_get_service` (~94 tokens)

Get service

Full detail of one service: what it is, how it is done, price, related case studies and FAQ.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.
- `slug` (string, required): Service slug, from hilo_list_services. One of: 3d-web-design, 3d-configurator, conversion-ux

### `hilo_get_pricing` (~69 tokens)

Get pricing

Hilo Studio's packages with starting prices (EUR, VAT not included), what each includes and typical timeline, plus the starting price for custom work.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.

### `hilo_list_projects` (~61 tokens)

List projects

Portfolio of Hilo Studio: each project with sector, type, services involved, live URL and case-study URL.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.

### `hilo_get_case_study` (~104 tokens)

Get case study

Full case study of one project: the challenge, the idea, how it was built (stack, 3D models) and key facts.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.
- `slug` (string, required): Project slug, from hilo_list_projects. One of: tabasco, padel, motor, domingueros, bar, abbey

### `hilo_list_lab_experiments` (~77 tokens)

List Lab experiments

Hilo Studio's Lab: experiments the studio builds to push interactive 3D (WebGL, shaders, AR, interactive courses…), each with a live demo you can open.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.

### `hilo_get_lab_experiment` (~79 tokens)

Get Lab experiment

Full write-up of one Lab experiment: what it is, how to use the demo and what it explores.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.
- `slug` (string, required): Experiment slug, from hilo_list_lab_experiments.

### `hilo_list_blog_posts` (~66 tokens)

List blog posts

Articles from Hilo Studio's blog (3D web costs, WebGL, configurators, AR, interactive training…), newest first.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.

### `hilo_get_blog_post` (~65 tokens)

Get blog post

Full text of one blog article, with its FAQ.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.
- `slug` (string, required): Post slug, from hilo_list_blog_posts.

### `hilo_find_relevant_work` (~119 tokens)

Find relevant work

Given a description of what the user needs (e.g. 'a 3D configurator for furniture', 'a live 3D map for a winery', 'interactive training for engineers'), returns the most relevant Hilo Studio services, case studies, Lab experiments and articles, with URLs.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.
- `need` (string, required): What the user wants to build or solve, in their own words.

### `hilo_recommend` (~238 tokens)

Guided contact: what fits

Hilo Studio's guided contact, in the chat: the same three one-tap questions the website asks (goal, what's holding them back, timing). Call it with whatever the user has answered so far (all optional). It returns the next question with its options or, once all are answered, what fits, its starting price, when they'd have it and a related case. Ask ONE question at a time with its options, in the user's language; never answer for the user. Then you may ask whether the price fits (price_fit). No personal data needed.

Input parameters:

- `lang` (string): Language of the answer: 'en' (English) or 'es' (Spanish). Use the user's language.
- `objective` (string): What the user wants to achieve (question 1).
- `price_fit` (string): Optional: after seeing the recommended price, whether it fits what they had in mind.
- `situation` (string): What's holding them back today (question 2; the valid options depend on the objective, hilo_recommend lists them).
- `timing` (string): When they need it (question 3).

### `hilo_request_quote` (~327 tokens)

Request a quote

Sends a project enquiry to Hilo Studio on behalf of the user (it reaches the team by email; they reply within 24 h and the user gets a confirmation email). ONLY call this after the user has explicitly confirmed they want to contact the studio and has given their name and email. Never invent contact details.

Input parameters:

- `budget` (string): Budget range, if the user mentioned one.
- `company` (string): Company or brand, if given.
- `deadline` (string): Desired timing or deadline, if mentioned.
- `email` (string, required): The user's email, where the studio will reply.
- `interest` (string): Package of interest if the user picked one (from hilo_get_pricing), 'custom' for bespoke work, or 'unsure'.
- `lang` (string): Language of the user: the confirmation email goes out in it.
- `name` (string, required): The user's name.
- `objective` (string): What the user wants to achieve (question 1).
- `price_fit` (string): Optional: after seeing the recommended price, whether it fits what they had in mind.
- `project` (string, required): What they need: goals, context, what it's for. Use the user's own words.
- `situation` (string): What's holding them back today (question 2; the valid options depend on the objective, hilo_recommend lists them).
- `timing` (string): When they need it (question 3).
- `user_confirmed` (boolean, required): Must be true: the user explicitly agreed to send these details to Hilo Studio.

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 79
- 2026-10-24: 79
- 2026-10-23: 78
- 2026-10-22: 78
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74

## Common questions

### What is the Hilo Studio MCP server?

Hilo Studio is an MCP server listed in the public MCP registry as com.hilostudiolab/studio. Madrid studio for branding and interactive 3D web: services, prices, work, Lab demos, quotes. This page covers its hosted endpoint (https://hilostudiolab.com/mcp).

### Is the Hilo Studio MCP server safe to use?

Hilo Studio scores 84 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 Hilo Studio MCP server expose?

Hilo Studio exposes 13 tools: hilo_studio_overview, hilo_list_services, hilo_get_service, hilo_get_pricing, hilo_list_projects, and 8 more. Their descriptions and schemas cost roughly 1,439 tokens of context every time the server is loaded.

### Does the Hilo Studio MCP server require authentication?

No. We connected to Hilo Studio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Hilo Studio MCP server still maintained?

Hilo Studio 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.

### What did VerifyMCP test on the Hilo Studio MCP server?

VerifyMCP ran 13 checks on Hilo Studio, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.

## Links

- Remote endpoint: https://hilostudiolab.com/mcp
- Website: https://hilostudiolab.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-hilostudiolab-studio/hilostudiolab.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hilostudiolab-studio/hilostudiolab/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-hilostudiolab-studio/hilostudiolab.json
- HTML version of this page: https://verifymcp.io/servers/com-hilostudiolab-studio/hilostudiolab