A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Mereka front desk (Reka) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Ask Mereka (Kuala Lumpur): programmes, room prices, courses, and enquiries sent with your say-so.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mereka-front-desk-reka-mcp https://contact.mereka.io/mcp
# 2 — ask your agent for something these tools do
# search_mereka, list_offerings, start_enquiry
Mereka front desk (Reka) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mereka-front-desk-reka-mcp https://contact.mereka.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What the person wants to know, in their own words and language (English, Bahasa Malaysia, Chinese, Tamil). |
| limit | integer | no | How many passages to return (default 5, at most 8). |
| area | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Which part to list: spaces, programmes, corporate or courses. Default: all. |
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. Before calling: show the person the details, get their agreemen
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | The person's name. |
| string | no | Their email address. Give an email or a phone/WhatsApp number. | |
| phone | string | no | Their phone or WhatsApp number. Give an email or a phone/WhatsApp number. |
| organisation | string | no | Their organisation, if any. |
| message | string | yes | What they want, in their own words or a faithful summary. Include team size, dates and place when they gave them. |
| enquiry_type | string | no | 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 fo |
| preferred_contact | string | no | How they would like to be answered. |
| language | string | no | Their language as a BCP 47 tag, for example en, ms, zh-Hans, ta. |
| details | object | no | Optional extra facts as short label and value pairs, such as team_size and preferred_dates. At most 8. |
| idempotency_key | string | no | A unique value for this one enquiry (a UUID). Retrying with the same value never sends it twice. Strongly recommended. |
| person_confirmed | boolean | yes | True only when the person has seen these details and agreed that they are sent to the Mereka team. Never set it on their behalf. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mereka front desk (Reka) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_mereka | no tags | |
| list_offerings | no tags | |
| start_enquiry | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mereka front desk (Reka) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.