_ registry / mcp http-sse · checked 39m ago

therapistsnearme

https://mcp.therapistsnearme.in

Registry code: be967f18c55057b3

api record

Search India's credential-verified therapist directory: read-only, public, checkable registrations.

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.therapistsnearme.in/api/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is therapistsnearme live?
Yes — it answered the hub's last check (checked 39m ago). It answered 100% of checks over the last 30 days.
Is therapistsnearme free to use?
Yes — the hub reached it with no key and no payment.
What tools does therapistsnearme have?
3 tools: get_therapist, search_therapists, list_filter_options.
Is therapistsnearme safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
563ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_therapists open 39m ago

    Search India's credential-verified mental-health therapist directory. Every result is a professional whose credentials were verified before listing (NMC/RCI register checks, or degree verification for counsellors). All filters optional; names are matched leniently (e.g. city 'Mumbai', concern 'anxiety').

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "type": "string",
          "description": "City name for in-person sessions, e.g. 'Mumbai'"
        },
        "limit": {
          "type": "number",
          "maximum": 20,
          "minimum": 1,
          "description": "Max results (default 6)"
        },
        "gender": {
          "enum": [
            "female",
            "male",
            "nonbinary"
          ],
          "type": "string",
          "description": "Therapist gender preference"
        },
        "concerns": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Issues to get help with, e.g. ['anxiety', 'grief']"
        },
        "language": {
          "type": "string",
          "description": "Practice language, e.g. 'Hindi'"
        },
        "online_only": {
          "type": "boolean",
          "description": "Only therapists offering online sessions"
        },
        "budget_max_inr": {
          "type": "number",
          "description": "Max fee per session in INR"
        }
      }
    }
    arguments 44 lines
  • list_filter_options open 39m ago

    The directory's available filter values: concerns/specialisations, practice languages, and cities with in-person therapists. Useful for grounding a search.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • get_therapist unknown 39m ago

    Full public profile of one verified therapist by profile slug (the last path segment of a profile_url), including bio, credentials, and publicly displayed registration numbers that can be checked against the NMC/RCI registers.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "slug"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Profile slug, e.g. 'shaswatee-behera'"
        }
      }
    }
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id be967f18c55057b3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/be967f18c55057b3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/be967f18c55057b3/badge.svg)](https://brick.blue/agent/be967f18c55057b3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.