Kareverse
REMOTE · WWW.KAREVERSE.COM
Elder care at home in Bangalore, India: services, prices, Care Plan, areas and callback requests.
Available components
Last scanned (19 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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 Security74
- 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability73
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 875 tokens (~125/item across 7 items; 7 tools + 0 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 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.
- 18 Nov 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.
- 16 Nov 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.
- 14 Nov 26 +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.
- 13 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “submit_enquiry” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- Destructive annotations: 100 → pass functional
- “submit_enquiry” reworded the description of “consent” cosmetic
- 12 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Nov 26 71
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 21 Nov 2026 · Probed https://www.kareverse.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.kareverse.com | CN=YE1,O=Let's Encrypt,C=US | 27 Oct 2026 | 25 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5ba96da983981d1c7f48d437e22bc417598 |
| SANs: kareverse.com, www.kareverse.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 insecure
Validation of www.kareverse.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| kareverse.com. | No DS | 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 |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.kareverse.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.kareverse.com/mcp | HTTPS enforced | 301 | https://www.kareverse.com/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 →
check_service_area Check service area ~64
Check whether Kareverse covers a locality or pincode in Bangalore (e.g. 'Whitefield', 'HSR Layout', '560066'), or list all service areas when locality is empty.
| Name | Type | Req | Description |
|---|---|---|---|
| locality | string | – | Locality, area or pincode in Bangalore. |
No output schema declared.
No examples provided.
get_care_plan Get the Kareverse Care Plan ~60
The monthly Kareverse Care Plan (a dedicated Care Manager, monthly home visit, weekly check-in, 24/7 emergency support): what it includes, monthly/quarterly/annual prices, and condition programmes such as dementia and Parkinson's care.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_contact_info Get contact details ~30
Kareverse's phone/WhatsApp, email, working hours and office address, plus the service categories.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_service Get service details ~59
Full details of one Kareverse service by id (from search_services): what is included and not included, price options, notice needed, FAQs and how to book.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Service id, e.g. 'hospital-accompaniment'. |
No output schema declared.
No examples provided.
search_guides Search care guides ~80
Search Kareverse's published guides for families caring for elderly parents (costs, caretakers, dementia, falls, hospital discharge, NRI care, Karnataka schemes). Returns titles, summaries and URLs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | – | Topic, e.g. 'caretaker cost' or 'dementia at home'. |
No output schema declared.
No examples provided.
search_services Search Kareverse services ~120
Search Kareverse's elder-care services in Bangalore by need (for example 'hospital visit', 'injection at home', 'night caretaker', 'physiotherapy after stroke'). Returns matching services with price, Care Plan member price and page URL. Leave query empty to list a category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category: genie (accompaniment and errands), nursing, caretakers, doctor-therapy, health-checks, condition-care. |
| limit | integer | – | – |
| query | string | – | What the family needs, in plain words. |
No output schema declared.
No examples provided.
submit_enquiry Request a callback from Kareverse ~249
Record a callback request for the Kareverse team. The result contains a WhatsApp link the person must open and send to confirm; Kareverse only contacts people who confirm. Use only after the person has seen Kareverse's privacy notice (https://www.kareverse.com/privacy), explicitly agreed to be contacted, and given their OWN name and phone number; set consent to true to confirm that. Never use it for someone else's number or for emergencies. May be temporarily unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | True only if the person saw the privacy notice and agreed that Kareverse may contact them about this enquiry. |
| string | – | Optional email address. | |
| message | string | – | Short background, in the person's words. |
| name | string | yes | Name of the person Kareverse should contact. |
| parent_area | string | – | Where the parent lives in Bangalore. |
| phone | string | yes | Their phone or WhatsApp number, with country code (e.g. +91 98765 43210 or +1 415 555 0100). |
| service_interest | string | – | What they need, e.g. 'Care Plan', 'Hospital accompaniment', 'Night caretaker'. |
No output schema declared.
No examples provided.
How do I install the Kareverse MCP server?
Kareverse is a hosted endpoint at https://www.kareverse.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 · www.kareverse.com
claude mcp add --transport http com-kareverse-kareverse 'https://www.kareverse.com/mcp'
What is the Kareverse MCP server?
Kareverse is an MCP server listed in the public MCP registry as com.kareverse/kareverse. Elder care at home in Bangalore, India: services, prices, Care Plan, areas and callback requests. This page covers its hosted endpoint (https://www.kareverse.com/mcp).
Is the Kareverse MCP server safe to use?
Kareverse 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 Kareverse MCP server expose?
Kareverse exposes 7 tools: search_services, get_service, get_care_plan, check_service_area, search_guides, and 2 more. Their descriptions and schemas cost roughly 662 tokens of context every time the server is loaded.
Does the Kareverse MCP server require authentication?
No. We connected to Kareverse without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Kareverse MCP server still maintained?
Kareverse is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Kareverse MCP server?
VerifyMCP ran 13 checks on Kareverse, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.