Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Brelio

REMOTE · BRELIO.EU · 2 COMPONENTS

Beauty salon management: appointments, clients, services and stats for your Brelio salon

74 Trust /100

Last scanned (15 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 411 tokens (~82/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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 →

Changelog

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.

  • 21 Nov 26 +1

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

  • 19 Nov 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.

  • 17 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 16 Nov 26 71

    First indexed and scored.

Diagnostics

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://brelio.eu/api/mcp/help

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brelio.eu CN=YR1,O=Let's Encrypt,C=US 1 Nov 2026 30 Jan 2027 RSA 2048 SHA256-RSA 5cb5a7f1a2ea6405ef9751660e5d7ea87f8
SANs: brelio.eu
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of brelio.eu. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
eu. DS published 35926 8 Verified
brelio.eu. No DS 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
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://brelio.eu/api/mcp/help Verified 200
http (plaintext) http://brelio.eu/api/mcp/help HTTPS enforced 308 https://brelio.eu/api/mcp/help
MCP tools · 5 exposed · ~298 tokens

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 →

Tool Tokens
brelio_get_article ~59

A blog article in full as plain text, with its page.

NameTypeReqDescription
languagestring–Article language: pl or en; pl when left out
slugstringyesThe article's slug, as the article list gives it

No output schema declared.

No examples provided.

brelio_get_help ~54

A help page in full as Markdown (written in Russian): what a feature does or the steps in the web and mobile app.

NameTypeReqDescription
slugstringyesThe page's slug, as the help search gives it

No output schema declared.

No examples provided.

brelio_get_plans ~45

Brelio's plans (Solo, Salon, Pro): monthly and yearly price, who each is for, the stylist limit, included message credits and the free trial.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

brelio_list_articles ~60

Brelio's blog for salon owners (running a salon, reminders and no-shows, client loyalty, software comparisons): titles, short summaries and pages.

NameTypeReqDescription
languagestring–Article language: pl or en; pl when left out

No output schema declared.

No examples provided.

brelio_search_help ~80

Searches Brelio's help pages (features, how-to guides and troubleshooting for salon owners) by words, e.g. "online booking", "stripe" or "reminders". The pages are written in Russian; each result has its slug and title.

NameTypeReqDescription
querystringyesWords to look for, in Russian or English product terms

No output schema declared.

No examples provided.

Install

How do I install the Brelio MCP server?

Brelio is a hosted endpoint at https://brelio.eu/api/mcp/help, 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 · brelio.eu

# add to Claude Code
claude mcp add --transport http eu-brelio-brelio 'https://brelio.eu/api/mcp/help'
Common questions

What is the Brelio MCP server?

Brelio is an MCP server listed in the public MCP registry as eu.brelio/brelio. Beauty salon management: appointments, clients, services and stats for your Brelio salon. This page covers its hosted endpoint (https://brelio.eu/api/mcp/help).

Is the Brelio MCP server safe to use?

Brelio scores 74 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 Brelio MCP server expose?

Brelio exposes 5 tools: brelio_search_help, brelio_get_help, brelio_list_articles, brelio_get_article, brelio_get_plans. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

Does the Brelio MCP server require authentication?

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

Is the Brelio MCP server still maintained?

Brelio 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 Brelio MCP server?

VerifyMCP ran 13 checks on Brelio, 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.