Student Protection Readiness Checklist | Safety Over Silence
REMOTE · SOSCHECKLIST.NET · SCANNED SEP 20
A 2-minute assessment to help parents understand and respond to student safety concerns with clarity
Available components
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 Security57
- 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 6 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
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 808 tokens (~134/item across 6 items; 6 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the Student Protection Readiness Checklist | Safety Over Silence MCP server?
Student Protection Readiness Checklist | Safety Over Silence is a hosted endpoint at https://soschecklist.net/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 · soschecklist.net
claude mcp add --transport http janoliverautomation-stack-soschecklist-net 'https://soschecklist.net/mcp'
{
"mcpServers": {
"janoliverautomation-stack-soschecklist-net": {
"url": "https://soschecklist.net/mcp"
}
}
} {
"servers": {
"janoliverautomation-stack-soschecklist-net": {
"type": "http",
"url": "https://soschecklist.net/mcp"
}
}
} [mcp_servers.janoliverautomation-stack-soschecklist-net] url = "https://soschecklist.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"janoliverautomation-stack-soschecklist-net": {
"type": "remote",
"url": "https://soschecklist.net/mcp",
"enabled": true
}
}
} openclaw mcp add janoliverautomation-stack-soschecklist-net --url 'https://soschecklist.net/mcp' --transport streamable-http
mcp_servers:
janoliverautomation-stack-soschecklist-net:
url: "https://soschecklist.net/mcp" {
"McpServers": {
"janoliverautomation-stack-soschecklist-net": {
"Transport": "http",
"Url": "https://soschecklist.net/mcp"
}
}
} assistant mcp add janoliverautomation-stack-soschecklist-net -t streamable-http -u 'https://soschecklist.net/mcp'
{
"mcpServers": {
"janoliverautomation-stack-soschecklist-net": {
"type": "http",
"url": "https://soschecklist.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 6 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.
- 5 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 20 Sept 2026 · Probed https://soschecklist.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=soschecklist.net | CN=WE1,O=Google Trust Services,C=US | 16 Aug 2026 | 14 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9d3c6e839ad8549f13274412e30cf9a8 |
| SANs: soschecklist.net | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of soschecklist.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| soschecklist.net. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://soschecklist.net/mcp | Verified | 200 | |
| http (plaintext) | http://soschecklist.net/mcp | HTTPS enforced | 301 | https://soschecklist.net/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_student_protection_next_steps ~101
Returns personalized next-step recommendations based on a score and/or score band. Call this after presenting assessment results, or when the user asks what to do next. Provides specific actions for each gap category and a consultation booking link.
| Name | Type | Req | Description |
|---|---|---|---|
| score | integer | yes | The normalized readiness score (0-100) from the assessment. |
| score_band | string | – | The score band classification. |
| top_gaps | array | – | Top protection gap areas identified. |
No output schema declared.
No examples provided.
get_student_protection_readiness_info ~98
Returns a summary of what the Student Protection Readiness Assessment is, what it measures, who it is for, and the 5 readiness categories. Call this when a user asks what this tool does, what readiness means, or wants to understand the framework before starting. Also call when the user expresses general uncertainty about their child's school experience — behavioral changes, suspected bullying, feeling dismissed by the school, or sensing something is off.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_student_protection_readiness_assessment ~131
Accepts the 12 answers (q1-q12, each scored 1-4) and returns: normalized score (0-100), score band, top 3 protection gaps, per-category scores, interpretation, and recommendation. Call this after collecting all 12 answers from the user. Present results with empathy — a low score means a lack of structure, not a lack of love.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Answers to the 12 readiness questions. Keys are q1 through q12, values are integers 1 (lowest readiness) to 4 (highest readiness). |
No output schema declared.
No examples provided.
run_student_safety_checklist ~237
PRIMARY TOOL. Run the Student Protection Readiness Checklist end-to-end. Accepts the 12 answers (q1-q12, each an integer 1-4) and returns the canonical result: a normalized readiness score (0-100), the score band/category, key findings (top protection gaps), a plain-language interpretation, per-category scores, a recommended next step, and safety limitations. This is the single canonical tool shared by the browser WebMCP, REST API, and this MCP server, so all interfaces return substantively identical output. Decision support only — it does not diagnose bullying, abuse, or mental health conditions and does not replace emergency services or professionals.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Answers to the 12 readiness questions. Keys are q1 through q12, values are integers 1 (lowest readiness) to 4 (highest readiness). Categories: Warning Sign Awareness (q1,q3,q5,q6), Communication Safe… |
No output schema declared.
No examples provided.
start_student_protection_readiness_assessment ~84
Returns the full set of 12 readiness questions grouped by category, with answer options (1-4 scale). Call this when the user is ready to begin the assessment. Walk the user through each question conversationally — do NOT dump all 12 at once. Acknowledge their concern first, then ask one question or one category at a time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_student_protection_lead_request ~157
Submits the parent's contact information and assessment results so they can receive follow-up support. ONLY call this if the user explicitly consents to sharing their information. Never call silently. Always confirm: "Would you like me to share your contact info so the Safety Over Silence team can follow up with you?" Requires at minimum a first name and email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Parent's email address. | |
| first_name | string | yes | Parent's first name. |
| phone | string | – | Parent's phone number (optional). |
| score | integer | – | The readiness score from the assessment. |
| score_band | string | – | The score band from the assessment. |
| top_gaps | array | – | Top gaps identified. |
No output schema declared.
No examples provided.
What is the Student Protection Readiness Checklist | Safety Over Silence MCP server?
Student Protection Readiness Checklist | Safety Over Silence is an MCP server listed in the public MCP registry as io.github.janoliverautomation-stack/soschecklist-net. A 2-minute assessment to help parents understand and respond to student safety concerns with clarity. This page covers its hosted endpoint (https://soschecklist.net/mcp).
Is the Student Protection Readiness Checklist | Safety Over Silence MCP server safe to use?
Student Protection Readiness Checklist | Safety Over Silence 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 Student Protection Readiness Checklist | Safety Over Silence MCP server expose?
Student Protection Readiness Checklist | Safety Over Silence exposes 6 tools: run_student_safety_checklist, get_student_protection_readiness_info, start_student_protection_readiness_assessment, run_student_protection_readiness_assessment, get_student_protection_next_steps, submit_student_protection_lead_request. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
Does the Student Protection Readiness Checklist | Safety Over Silence MCP server require authentication?
No. We connected to Student Protection Readiness Checklist | Safety Over Silence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Student Protection Readiness Checklist | Safety Over Silence MCP server still maintained?
Student Protection Readiness Checklist | Safety Over Silence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.