STRIDE
REMOTE · STRIDE.SIMMONS-SIMMONS.COM
Digital-regulation tracking and analysis across jurisdictions; STRIDE access is required.
Available components
Last scanned (2 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Education and Research
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 Security83
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 718 tokens (~239/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
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.
- 24 Oct 26 +2
- DNSSEC: fail → pass ▲ security
- 22 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.
- 20 Oct 26 0
- DNSSEC: pass → fail ▼ security
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 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.
- 15 Oct 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.23 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 14 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 13 Oct 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.
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 24 Oct 2026 · Probed https://stride.simmons-simmons.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=stride.simmons-simmons.com,O=SIMMONS & SIMMONS LLP,L=Bristol,C=GB | CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US | 4 Feb 2026 | 3 Feb 2027 | RSA 2048 | SHA256-RSA | d7123010347ad5dde22b369eb2e83b8 |
| SANs: stride.simmons-simmons.com | ||||||
| CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 30 Mar 2021 | 29 Mar 2031 | RSA 2048 | SHA256-RSA | cf5bd062b5602f47ab8502c23ccf066 |
| CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 1 Aug 2013 | 15 Jan 2038 | RSA 2048 | SHA256-RSA | 33af1e6a711a9a0bb2864b11d09fae5 |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of stride.simmons-simmons.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| simmons-simmons.com. | present | 53783 | 13 | Verified |
| stride.simmons-simmons.com. | Verified address RRset verified with the apex keys |
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; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' https://cdn.jsdelivr.net https://js.monitor.azure.com; style-src 'self' 'unsafe-inline' https:; img-src 'self' data: https:; font-src 'self' data: https:; connect-src 'self' https://*.europa.eu https://*.in.applicationinsights.azure.com https://*.monitor.azure.com; media-src 'self' https:; object-src 'none'; frame-src 'self' blob:; frame-ancestors 'none'; worker-src 'self'; manifest-src 'self'; |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://stride.simmons-simmons.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://stride.simmons-simmons.com/mcp/ | HTTPS enforced | 307 | https://stride.simmons-simmons.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 →
about_this_server ~69
What this MCP server is, what each access tier includes, and how to obtain access. Call this first if you are unsure what the server offers, or after any tool refuses you — the refusal names a tier, and this tool explains what that tier costs and what it adds. Requires no credentials.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_legislation ~285
Retrieve one act by CELEX ID, Lex-Ray ID, nickname, or uk-/eu- prefix. 'meta' is the bibliographic record (titles, dates, Official Journal reference, EuroVoc concepts, amendments and relationships to other acts) and needs no credentials. 'data' adds the parsed legal content — recitals, articles, annexes, definitions — and 'full' adds the rendered HTML. Every level carries a currency block: the day the answer was computed for, the commencement state on that day, and which version of the act is in force. Every answer also carries `pending_amendments`: proposals that propose to amend this act, each labelled in_flight / concluded / unknown, stamped with the reading date it was resolved against. These are PROPOSED, not enacted — never quote one as law.
| Name | Type | Req | Description |
|---|---|---|---|
| celex_id | string | yes | The CELEX ID, Lex-Ray ID, nickname, or jurisdiction-prefixed nickname (e.g., '32016R0679', 'FCA-TS-s140', 'gdpr', 'uk-gdpr') |
| detail | string | – | Level of detail: 'meta' (titles, dates, OJ reference, classifications) |
| fetch_if_missing | boolean | – | Live fetch fallback: false only for this caller; unknown acts return structured not_found without an outbound EUR-Lex fetch |
No output schema declared.
No examples provided.
search_instruments ~283
Find EU legislation and UK legislation by keyword, acronym (GDPR, DORA, AIA), the common name practitioners use ('Market Abuse Regulation', 'MLRs', 'UK GDPR'), CELEX ID or Lex-Ray id. Matching is case-insensitive and an exact name ranks ahead of partial title matches. Returns an envelope whose 'matches' array carries the bibliographic record for each match — titles, id, jurisdiction (eu/uk), Official Journal reference, dates — plus a currency block giving the commencement state as at today, so a match that is expired or not yet applying says so rather than reading as current law. When several instruments share the exact name searched, 'ambiguous' is true and 'disambiguation' lists them: choose by jurisdiction and title rather than taking the first. When a curated common name settles it, 'preferred' names that act and 'alternatives' the others sharing the name. Use this to resolve a name to an id before calling the other tools. Requires no credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results (1-50, default 10) |
| query | string | yes | Search term - can be a keyword (e.g., 'artificial intelligence'), acronym (e.g., 'GDPR', 'AIA'), or CELEX ID (e.g., '32016R0679') |
No output schema declared.
No examples provided.
How do I install the STRIDE MCP server?
STRIDE is a hosted endpoint at https://stride.simmons-simmons.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 · stride.simmons-simmons.com
claude mcp add --transport http info-stride-stride 'https://stride.simmons-simmons.com/mcp/'
What is the STRIDE MCP server?
STRIDE is an MCP server listed in the public MCP registry as info.stride/stride. Digital-regulation tracking and analysis across jurisdictions; STRIDE access is required. This page covers its hosted endpoint (https://stride.simmons-simmons.com/mcp/).
Is the STRIDE MCP server safe to use?
STRIDE scores 81 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 STRIDE MCP server expose?
STRIDE exposes 3 tools: about_this_server, search_instruments, get_legislation. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Does the STRIDE MCP server require authentication?
No. We connected to STRIDE without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the STRIDE MCP server still maintained?
STRIDE is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.