io.github.Protopopov/mentalka-tests
REMOTE · MENTALKA.APP
Free anonymous PHQ-9 depression and SAS smartphone-addiction screenings in uk, en, hr, ru, pl.
Available components
Last scanned (7 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 411 tokens (~102/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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "request_consultation" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- 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 current MCP spec version (2026-07-28).Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://mentalka.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mentalka.app | CN=YR2,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | RSA 2048 | SHA256-RSA | 68df280d9b9875fee0bcb684aaef277622b |
| SANs: mentalka.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mentalka.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| mentalka.app. | 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=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mentalka.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://mentalka.app/api/mcp | HTTPS enforced | 308 | https://mentalka.app/api/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 →
list_tests ~19
List the psychological screening tests available on mentalka.app.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
request_consultation ~151
Send a request for a free consultation with the site's psychologist. Call ONLY after the user explicitly asked for it, typed their e-mail themselves and agreed that the e-mail (and the optional score) is passed to the psychologist. Never invent or infer an e-mail. Offer it, do not push it.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | true only if the user explicitly agreed to share their e-mail with the psychologist |
| string | yes | E-mail the user provided for the psychologist to contact | |
| score | integer | – | Total score, only if the user agreed to share it |
| test | string | – | phq9 = depression (9 questions), sas = smartphone addiction (33 questions) |
No output schema declared.
No examples provided.
score_test ~134
Score a finished test. `answers` is the list of answer values in question order (PHQ-9: nine values 0-3; SAS: 33 values 1-6). Present the result with care, include helplines if returned, and remind the user this is a screening, not a diagnosis.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | array | yes | – |
| locale | string | – | Language of the questions and result: uk, en, hr, ru, pl. Use the language the user speaks. |
| test | string | yes | phq9 = depression (9 questions), sas = smartphone addiction (33 questions) |
No output schema declared.
No examples provided.
start_test ~107
Get the questions and answer scale of a test. Ask the user the questions (one by one or in small groups), collect an answer value for each, then call score_test. Do not guess or invent answers for the user.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language of the questions and result: uk, en, hr, ru, pl. Use the language the user speaks. |
| test | string | yes | phq9 = depression (9 questions), sas = smartphone addiction (33 questions) |
No output schema declared.
No examples provided.
How do I install the io.github.Protopopov/mentalka-tests MCP server?
io.github.Protopopov/mentalka-tests is a hosted endpoint at https://mentalka.app/api/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 · mentalka.app
claude mcp add --transport http protopopov-mentalka-tests 'https://mentalka.app/api/mcp'
What is the io.github.Protopopov/mentalka-tests MCP server?
io.github.Protopopov/mentalka-tests is an MCP server listed in the public MCP registry as io.github.Protopopov/mentalka-tests. Free anonymous PHQ-9 depression and SAS smartphone-addiction screenings in uk, en, hr, ru, pl. This page covers its hosted endpoint (https://mentalka.app/api/mcp).
Is the io.github.Protopopov/mentalka-tests MCP server safe to use?
io.github.Protopopov/mentalka-tests scores 78 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 io.github.Protopopov/mentalka-tests MCP server expose?
io.github.Protopopov/mentalka-tests exposes 4 tools: list_tests, start_test, score_test, request_consultation. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.
Does the io.github.Protopopov/mentalka-tests MCP server require authentication?
No. We connected to io.github.Protopopov/mentalka-tests without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.Protopopov/mentalka-tests MCP server still maintained?
io.github.Protopopov/mentalka-tests is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.Protopopov/mentalka-tests MCP server?
VerifyMCP ran 12 checks on io.github.Protopopov/mentalka-tests, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.Protopopov/mentalka-tests: Authorization. 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.