Mayorana
REMOTE · MAYORANA.CH
Search mayorana.ch: desktop apps, release notes, plans, and the Rust, LLM and Azure blog.
Available components
Last scanned (3 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
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 Security77
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 523 tokens (~74/item across 7 items; 7 tools + 0 resources), lean.Pass
- 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 2 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.
- 30 Oct 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.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 70
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 5 Nov 2026 · Probed https://mayorana.ch/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mayorana.ch | CN=YE1,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 631df39894bc9a5f38a9d4d7eb9c4134819 |
| SANs: mayorana.ch, www.mayorana.ch | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mayorana.ch. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ch. | present | 58745 | 13 | Verified |
| mayorana.ch. | present | 27070 | 8 | Verified |
| mayorana.ch. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | 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://mayorana.ch/mcp | Verified | 200 | |
| http (plaintext) | http://mayorana.ch/mcp | HTTPS enforced | 301 | https://mayorana.ch/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 →
get_app Read an app page ~69
The full page for one app, as markdown: overview, features, requirements, downloads, one-line install, MCP setup, FAQ.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | App id from list_apps, e.g. "gitagent". |
| locale | string | – | Language of the content: en or fr. |
No output schema declared.
No examples provided.
get_learning_path Read a learning path ~74
Without a track: the learning paths (ordered reading lists through the blog). With one: its articles in reading order.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the content: en or fr. |
| track | string | – | Track id, e.g. "rust" or "llm". Omit to list them. |
No output schema declared.
No examples provided.
get_post Read a blog article ~62
One blog article as markdown, with its title, date, tags and URL. Get the slug from search.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the content: en or fr. |
| slug | string | yes | The article slug, the last part of its URL. |
No output schema declared.
No examples provided.
get_pricing Plans and prices ~44
The plans on sale: price per month, monthly AI credits, and which apps each unlocks.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the content: en or fr. |
No output schema declared.
No examples provided.
get_release_notes Read release notes ~44
An app's recent releases: version, date and what changed, newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | App id from list_apps. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_apps List the apps ~45
Every Mayorana desktop app: id, name, what it does, platforms, latest version and page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the content: en or fr. |
No output schema declared.
No examples provided.
search Search mayorana.ch ~82
Search the apps, blog articles, learning paths and pages of mayorana.ch. Returns titles, URLs and one-line summaries, best match first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| locale | string | – | Language of the content: en or fr. |
| query | string | yes | Words to look for, e.g. "borrow checker" or "correlation id". |
No output schema declared.
No examples provided.
How do I install the Mayorana MCP server?
Mayorana is a hosted endpoint at https://mayorana.ch/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 · mayorana.ch
claude mcp add --transport http bennekrouf-mayorana 'https://mayorana.ch/mcp'
What is the Mayorana MCP server?
Mayorana is an MCP server listed in the public MCP registry as io.github.bennekrouf/mayorana. Search mayorana.ch: desktop apps, release notes, plans, and the Rust, LLM and Azure blog. This page covers its hosted endpoint (https://mayorana.ch/mcp).
Is the Mayorana MCP server safe to use?
Mayorana scores 73 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 Mayorana MCP server expose?
Mayorana exposes 7 tools: search, list_apps, get_app, get_release_notes, get_post, and 2 more. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.
Does the Mayorana MCP server require authentication?
No. We connected to Mayorana without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mayorana MCP server still maintained?
Mayorana 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.