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.

com.ellomind/therapy-booking

REMOTE · MCP.ELLOMIND.COM · SCANNED SEP 28

Check live availability and book therapy sessions with a Malayalam-speaking psychologist.

Available components

+4 this week 70 Trust /100
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 Security60
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 383 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 58% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.ellomind/therapy-booking MCP server?

com.ellomind/therapy-booking is a hosted endpoint at https://mcp.ellomind.com/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 · mcp.ellomind.com

# add to Claude Code
claude mcp add --transport http com-ellomind-therapy-booking 'https://mcp.ellomind.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-ellomind-therapy-booking": {
      "url": "https://mcp.ellomind.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-ellomind-therapy-booking": {
      "type": "http",
      "url": "https://mcp.ellomind.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-ellomind-therapy-booking]
url = "https://mcp.ellomind.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-ellomind-therapy-booking": {
      "type": "remote",
      "url": "https://mcp.ellomind.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-ellomind-therapy-booking --url 'https://mcp.ellomind.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-ellomind-therapy-booking:
    url: "https://mcp.ellomind.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-ellomind-therapy-booking": {
      "Transport": "http",
      "Url": "https://mcp.ellomind.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-ellomind-therapy-booking -t streamable-http -u 'https://mcp.ellomind.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-ellomind-therapy-booking": {
      "type": "http",
      "url": "https://mcp.ellomind.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

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

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 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.

  • 22 Sept 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 Sept 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.

  • 18 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Sept 26 +31
    • Authorization: fail → unverified ▼ security
    • Transport: unverified → pass ▲ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → pass ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Tool coverage: 58 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
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 28 Sept 2026 · Probed https://mcp.ellomind.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ellomind.com CN=YE1,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 6e01b458c0fbaa8cca7dd8d1421c3c23945
SANs: *.ellomind.com, ellomind.com
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 mcp.ellomind.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
ellomind.com. present 2371 13 Verified
mcp.ellomind.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.ellomind.com/mcp Verified 200
http (plaintext) http://mcp.ellomind.com/mcp HTTPS enforced 301 https://mcp.ellomind.com/mcp
MCP tools · 4 exposed · ~383 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
check_availability ~63

Real open time slots (IST) for a session type over a date range. Dates are YYYY-MM-DD.

NameTypeReqDescription
fromstringyesstart date YYYY-MM-DD
session_typestringyes–
tostringyesend date YYYY-MM-DD

No output schema declared.

No examples provided.

create_booking_draft ~152

Hold a specific slot and return a single-use pay link to hand the customer. Call check_availability first and use one of its times. Collect the customer's name, phone, and email first. The price is server-set; you cannot set an amount. Payment and consent stay with the customer.

NameTypeReqDescription
emailstringyes–
namestringyes–
phonestringyeswith country code, e.g. +91 98xxxxxxxx
plan_codestringyes–
session_typestringyes–
slot_datestringyesYYYY-MM-DD from check_availability
slot_timestringyesHH:MM 24h IST from check_availability

No output schema declared.

No examples provided.

get_booking_status ~131

Retrieve a booking's status and Meet link to show the customer in chat. The booking already confirms automatically on payment (the customer is emailed the invite + link) — this tool does NOT lock in or create anything, it only reads the current state. Call it when the customer asks. REQUIRES the poll_key from create_booking_draft; a ref on its own will not release the Meet link.

NameTypeReqDescription
poll_keystringyesthe poll_key returned by create_booking_draft; required to retrieve the Meet link
refstringyesthe booking ref, e.g. EM-XXXX

No output schema declared.

No examples provided.

list_services ~37

List session types and prices for booking therapy with ElloMind. Call before creating a booking so you use a valid session_type and plan_code.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the com.ellomind/therapy-booking MCP server?

com.ellomind/therapy-booking is an MCP server listed in the public MCP registry as com.ellomind/therapy-booking. Check live availability and book therapy sessions with a Malayalam-speaking psychologist. This page covers its hosted endpoint (https://mcp.ellomind.com/mcp).

Is the com.ellomind/therapy-booking MCP server safe to use?

com.ellomind/therapy-booking scores 70 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 com.ellomind/therapy-booking MCP server expose?

com.ellomind/therapy-booking exposes 4 tools: list_services, check_availability, create_booking_draft, get_booking_status. Their descriptions and schemas cost roughly 383 tokens of context every time the server is loaded.

Does the com.ellomind/therapy-booking MCP server require authentication?

No. We connected to com.ellomind/therapy-booking without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.ellomind/therapy-booking MCP server still maintained?

com.ellomind/therapy-booking is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.