# Mereka front desk (Reka) (remote · contact.mereka.io)

Ask Mereka (Kuala Lumpur): programmes, room prices, courses, and enquiries sent with your say-so.

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `contact.mereka.io`: 76/100 (this document), [markdown](https://verifymcp.io/servers/io-mereka-contact-front-desk/contact.md), [page](https://verifymcp.io/servers/io-mereka-contact-front-desk/contact)

## Channel facts

- Endpoint: `https://contact.mereka.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - 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**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 5 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 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.

### Claude

```bash
claude mcp add --transport http io-mereka-contact-front-desk 'https://contact.mereka.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-mereka-contact-front-desk": {
      "url": "https://contact.mereka.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-mereka-contact-front-desk": {
      "type": "http",
      "url": "https://contact.mereka.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-mereka-contact-front-desk]
url = "https://contact.mereka.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-mereka-contact-front-desk": {
      "type": "remote",
      "url": "https://contact.mereka.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-mereka-contact-front-desk --url 'https://contact.mereka.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-mereka-contact-front-desk:
    url: "https://contact.mereka.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-mereka-contact-front-desk": {
      "Transport": "http",
      "Url": "https://contact.mereka.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-mereka-contact-front-desk -t streamable-http -u 'https://contact.mereka.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-mereka-contact-front-desk": {
      "type": "http",
      "url": "https://contact.mereka.io/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-05 (score 76, +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.

### 2026-11-03 (score 75, +1)

- [security] 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
- [functional regression] Schema quality: 177 → 196
- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “list_offerings” now declares an output schema
- [functional improvement] Tool “search_mereka” now declares an output schema
- [functional improvement] 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
- [cosmetic] “list_offerings” reworded the description of “category”
- [cosmetic] “start_enquiry” reworded the description of “person_confirmed”

### 2026-11-02 (score 74)

First indexed and scored.

## MCP tools (3)

### `search_mereka` (~188 tokens)

Search Mereka's public knowledge

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.

Input parameters:

- `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, required): What the person wants to know, in their own words and language (English, Bahasa Malaysia, Chinese, Tamil).

Output parameters:

- `count` (integer): How many passages came back; 0 means nothing in the public knowledge answers it.
- `note` (string): How to use the passages, and what to do when they do not answer.
- `ok` (boolean)
- `passages` (array)
- `query` (string)

### `list_offerings` (~145 tokens)

List what Mereka offers

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.

Input parameters:

- `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…

Output parameters:

- `corporate` (object)
- `courses` (object)
- `note` (string)
- `ok` (boolean)
- `programmes` (array)
- `provider` (string)
- `site` (string)
- `spaces` (object)

### `start_enquiry` (~552 tokens)

Start an enquiry with the Mereka team

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.

Input parameters:

- `details` (object): Optional extra facts as short label and value pairs, such as team_size and preferred_dates. At most 8.
- `email` (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, required): What they want, in their own words or a faithful summary. Include team size, dates and place when they gave them.
- `name` (string, required): The person's name.
- `organisation` (string): Their organisation, if any.
- `person_confirmed` (boolean, required): 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.

Output parameters:

- `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): What happened, in words to relay to the person.
- `nextStep` (string): What to do next.
- `ok` (boolean): 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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-mereka-contact-front-desk/contact#diagnostics

## Score history

- 2026-11-05: 76
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74

## Common questions

### 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 76 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://contact.mereka.io/mcp
- Website: https://contact.mereka.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-mereka-contact-front-desk/contact.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-mereka-contact-front-desk/contact.json
- HTML version of this page: https://verifymcp.io/servers/io-mereka-contact-front-desk/contact