Sherah
REMOTE · MCP.MYSHERAH.COM
Online personal assistant for busy parents: home, kids, meals, admin and more
Available components
Last scanned (20 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Productivity and Notes
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 Security80
- 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
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 422 tokens (~211/item across 2 items; 2 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 Management17
- Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 1 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.
- 10 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 13.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17.
- 8 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 13.
- 6 Nov 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
- 4 Nov 26 0
- Tool “get_task_categories” rewrote its description, which is the text the model reads security
- Tool “request_sign_up_with_task” rewrote its description, which is the text the model reads security
- The server no longer declares the “prompts” capability functional
- The server no longer declares the “resources” capability functional
- Schema quality: excellent → good functional
- MCP protocol: Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. functional
- MCP protocol version: 2026-07-28 → 2025-11-25 functional
- Tool “get_task_categories” changed its title: get_task_categories → Get Task Categories cosmetic
- Tool “request_sign_up_with_task” changed its title: request_sign_up_with_task → Request Sign-Up With a Task cosmetic
- 30 Oct 26 −3
- Stability: pass → fail ▼ security
- Tool “get_available_task_types” was removed ▼ security
- Tool “request_sign_up” was removed ▼ security
- Authorization: unverified → partial ▲ security
- HSTS header: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: sherah → Sherah security
- Tool “request_sign_up_with_task” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “request_sign_up_with_task” added a required parameter “needed_by”, so existing callers break ▼ functional
- “request_sign_up_with_task” dropped the required parameter “neededBy” ▼ functional
- Resource “tasks-we-help-with” was removed ▼ functional
- Tool coverage: 50% → 100% ▲ functional
- The server now declares the “prompts” capability functional
- Schema quality: good → excellent functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.1.0 → 1.0.0 functional
- New tool “get_task_categories” functional
- “request_sign_up_with_task” reworded the description of “city” cosmetic
- “request_sign_up_with_task” reworded the description of “email” cosmetic
- “request_sign_up_with_task” reworded the description of “state” cosmetic
- “request_sign_up_with_task” reworded the description of “task” cosmetic
- Tool “request_sign_up_with_task” changed its title: Request sign up with task → request_sign_up_with_task cosmetic
- 10 Oct 26 0
- Stability: 0.93 → pass security
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://mcp.mysherah.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.mysherah.com | CN=YE2,O=Let's Encrypt,C=US | 29 Oct 2026 | 27 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d264a6f14eafc9e471b188bec8df7e63fa |
| SANs: mcp.mysherah.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcp.mysherah.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| mysherah.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 |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.mysherah.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.mysherah.com/mcp | HTTPS enforced | 301 | https://mcp.mysherah.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 →
get_task_categories Get Task Categories ~76
Lists the kinds of everyday tasks Sherah's personal assistants handle for families in the US, as category and example-task pairs (for example Pets: Dog Walking, Kids: Camps, Home: Electrician), plus a link to Sherah's page about the tasks it helps with. The examples are a sample, not a complete list.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_sign_up_with_task Request Sign-Up With a Task ~234
Submits a request for Sherah's help with one task, on behalf of a person in the US and with details that person provides: the task in their own words, the date they need it done by, their email address, city and two-letter US state. Sherah is a personal-assistant service for families. If the email address is new to Sherah, Sherah emails the person an invitation to create an account, and the task is waiting for them after sign-up. Returns whether the request was submitted and a message for the person.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | The person's city. |
| string | yes | The person's own email address. The invitation is sent here. | |
| needed_by | string | yes | The date the person needs it done by, as YYYY-MM-DD, for example 2026-12-01. No time and no timezone. |
| state | string | yes | The person's US state, as a two-letter USPS code (for example TX). |
| task | string | yes | What the person needs done, in their own words (up to 2,000 characters). |
No output schema declared.
No examples provided.
How do I install the Sherah MCP server?
Sherah is a hosted endpoint at https://mcp.mysherah.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.mysherah.com
claude mcp add --transport http com-mysherah-sherah 'https://mcp.mysherah.com/mcp'
What is the Sherah MCP server?
Sherah is an MCP server listed in the public MCP registry as com.mysherah/sherah. Online personal assistant for busy parents: home, kids, meals, admin and more. This page covers its hosted endpoint (https://mcp.mysherah.com/mcp).
Is the Sherah MCP server safe to use?
Sherah 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 Sherah MCP server expose?
Sherah exposes 2 tools: get_task_categories, request_sign_up_with_task. Their descriptions and schemas cost roughly 310 tokens of context every time the server is loaded.
Does the Sherah MCP server require authentication?
No. We connected to Sherah without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sherah MCP server still maintained?
Sherah 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 Sherah MCP server?
VerifyMCP ran 13 checks on Sherah, 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.