Mereka front desk (Reka)
REMOTE · CONTACT.MEREKA.IO
Ask Mereka (Kuala Lumpur): programmes, room prices, courses, and enquiries sent with your say-so.
Available components
Last scanned (19 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Education and Research
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. 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
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1178 tokens (~196/item across 6 items; 3 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “start_enquiry” rewrote its description, which is the text the model reads security
- Schema quality: 177 → 196 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Tool “list_offerings” now declares an output schema ▲ functional
- Tool “search_mereka” now declares an output schema ▲ functional
- Tool “start_enquiry” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- “list_offerings” reworded the description of “category” cosmetic
- “start_enquiry” reworded the description of “person_confirmed” cosmetic
- 2 Nov 26 74
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 4 Nov 2026 · Probed https://contact.mereka.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mereka.io | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 35f1da838cb4fd250e02b7d0b7c00caa |
| SANs: mereka.io, *.mereka.io | ||||||
| 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 contact.mereka.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| mereka.io. | absent | 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=31536000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://contact.mereka.io/mcp | Verified | 200 | |
| http (plaintext) | http://contact.mereka.io/mcp | HTTPS enforced | 301 | https://contact.mereka.io/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 →
list_offerings List what Mereka offers ~145
List what Mereka offers as structured data: spaces and rooms at Mereka @ Publika with published prices, programmes and workshops, corporate services (each with the enquiry_type to use in start_enquiry), published prices, and the course catalogue. Prices are published 'from' prices as of the dates shown; the team confirms the final quote. Information from Mereka's AI front desk (Reka). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Which part to list: spaces (rooms at Mereka @ Publika with prices), programmes, corporate (services, enquiry types and published prices) or courses. Default: all, which is long; pick one when the que… |
| Name | Type | Req | Description |
|---|---|---|---|
| corporate | object | – | – |
| courses | object | – | – |
| note | string | yes | – |
| ok | boolean | yes | – |
| programmes | array | – | – |
| provider | string | yes | – |
| site | string | yes | – |
| spaces | object | – | – |
No examples provided.
search_mereka Search Mereka's public knowledge ~188
Search Mereka's reviewed public knowledge (programmes and courses, corporate training and the AI Lab, the Mereka @ Publika space and its room prices, partnerships, how to contact the team) and return passages with titles, source URLs and as-of dates. Answers come from Mereka's AI front desk (Reka), which reads only public information. Questions can be in English, Bahasa Malaysia, Chinese or Tamil. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | Optional: the part of Mereka the question is about, to rank its pages first, such as space-publika, ai-lab, corporate or mta. Leave out when unsure. |
| limit | integer | – | How many passages to return (default 5, at most 8). |
| query | string | yes | What the person wants to know, in their own words and language (English, Bahasa Malaysia, Chinese, Tamil). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many passages came back; 0 means nothing in the public knowledge answers it. |
| note | string | yes | How to use the passages, and what to do when they do not answer. |
| ok | boolean | yes | – |
| passages | array | yes | – |
| query | string | yes | – |
No examples provided.
start_enquiry Start an enquiry with the Mereka team ~552
Send an enquiry to a person on the Mereka team on behalf of the person you are helping, for example to ask about hiring a room, corporate training or a partnership. It goes through the same form pipeline as Mereka's website: the right team is notified and the person receives a confirmation email. It books, charges and commits nothing. Two steps: call with person_confirmed false to get a preview of exactly what would be sent and to which team (nothing is sent), show it to the person, and call again with the same arguments and person_confirmed true only after they agree. Provide an email or a phone / WhatsApp number so the team can reply. Retrying with the same idempotency_key never sends twice. The front desk is Mereka's AI (Reka); a person on the team replies.
| Name | Type | Req | Description |
|---|---|---|---|
| details | object | – | Optional extra facts as short label and value pairs, such as team_size and preferred_dates. At most 8. |
| string | – | Their email address. Give an email or a phone/WhatsApp number. | |
| enquiry_type | string | – | What the enquiry is about, which decides which Mereka team receives it. One of: contact-team (General question for the team); corporate-training (Corporate training for your team); courses (Courses f… |
| idempotency_key | string | – | A unique value for this one enquiry (a UUID). Retrying with the same value never sends it twice. Strongly recommended. |
| language | string | – | Their language as a BCP 47 tag, for example en, ms, zh-Hans, ta. |
| message | string | yes | What they want, in their own words or a faithful summary. Include team size, dates and place when they gave them. |
| name | string | yes | The person's name. |
| organisation | string | – | Their organisation, if any. |
| person_confirmed | boolean | yes | False returns a preview of exactly what would be sent and to which team, sending nothing: show it to the person. True only when the person has seen those details and agreed that they are sent to the… |
| phone | string | – | Their phone or WhatsApp number. Give an email or a phone/WhatsApp number. |
| preferred_contact | string | – | How they would like to be answered. |
| Name | Type | Req | Description |
|---|---|---|---|
| error | string | – | Why it was not sent: not_confirmed (a preview awaiting the person's yes), needs_contact (no email or phone yet), contact_cap, slow_down, not_saved. |
| message | string | yes | What happened, in words to relay to the person. |
| nextStep | string | – | What to do next. |
| ok | boolean | yes | True only when the enquiry reached the Mereka team. |
| preview | object | – | What would be sent and to which team: show it to the person first. |
| reference | string | – | The enquiry reference (RK-XXXXX), when received. |
| replayed | boolean | – | True when this repeated an enquiry already received: nothing new was sent. |
| replyTo | string | – | Where a person on the team will reply, when received. |
| retryAfterSeconds | number | – | – |
| status | string | yes | – |
No examples provided.
How do I install the Mereka front desk (Reka) MCP server?
Mereka front desk (Reka) is a hosted endpoint at https://contact.mereka.io/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 · contact.mereka.io
claude mcp add --transport http io-mereka-contact-front-desk 'https://contact.mereka.io/mcp'
What is the Mereka front desk (Reka) MCP server?
Mereka front desk (Reka) is an MCP server listed in the public MCP registry as io.mereka.contact/front-desk. Ask Mereka (Kuala Lumpur): programmes, room prices, courses, and enquiries sent with your say-so. This page covers its hosted endpoint (https://contact.mereka.io/mcp).
Is the Mereka front desk (Reka) MCP server safe to use?
Mereka front desk (Reka) scores 75 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 Mereka front desk (Reka) MCP server expose?
Mereka front desk (Reka) exposes 3 tools: search_mereka, list_offerings, start_enquiry. Their descriptions and schemas cost roughly 885 tokens of context every time the server is loaded.
Does the Mereka front desk (Reka) MCP server require authentication?
No. We connected to Mereka front desk (Reka) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Mereka front desk (Reka) MCP server still maintained?
Mereka front desk (Reka) is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.