Skip to content

STRIDE MCP server

info.stride/stridestride.infostreamable-httpv1.0.0Scanned

Digital-regulation tracking and analysis across jurisdictions; STRIDE access is required.

5 tools: 1 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 1 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 3 findings

Tools listed without sign-in. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Its sign-in does not let Anlyon set up an OAuth client on its own, so there is no link to it here.

What the STRIDE MCP server can do

The STRIDE MCP server is published by stride.info, a domain the MCP Registry verified. It has 5 tools. It can create or change data (1 tool: about_this_server), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 3 findings (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Changes things 1Claude Code: ask
  • about_this_serverWhat this MCP server is, what each access tier includes, and how to obtain access.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...ier costs and what it adds. Requires no credentials."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
Only reads 4Show 4 read-only tools
  • get_changesWhat changes the law across the whole corpus in a window of dates: what has entered into force, started applying, been replaced by a new version or reached a deadline in the last m…No findings

    Why it is in this group

    • The name "get_changes" says "get": a word for reading.
    Description, as the server wrote it
    What changes the law across the whole corpus in a window of dates: what has entered into force, started applying, been replaced by a new version or reached a deadline in the last months, and what will in the next ones. Each event says whether it is an entry into force or an application, and its act's position on as_at. Window with since/until or last_months/next_months (left out: the last 6 and the next 12 months, echoed); filter by kind, jurisdiction (eu, uk), subject_matter or instrument (regulation, directive, decision). Paged by cursor, with the total and the coverage: how many acts have no resolved date, are held, or are not indexed yet. `answerable` is false when too much of the scope is not indexed yet for the list to be read as complete: an empty list is then not "nothing changes". A uk-only query is read on London's legal day. Answers "what starts applying in the next 12 months" and "what changed in the last 6".

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • get_legislationRetrieve one act by CELEX ID, Lex-Ray ID, nickname, or uk-/eu- prefix.1 finding

    Why it is in this group

    • The name "get_legislation" says "get": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...lationships to other acts) and needs no credentials. 'data' adds the parsed legal content —..."

      What this check looks for
    Description, as the server wrote it
    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 web_url, the act's Lex-Ray page, and 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • get_timelineEvery dated event of one act, past and future, each classified: entry_into_force and application (kept apart, with their scope: the whole act, a staged tranche or a set of provisio…No findings

    Why it is in this group

    • The name "get_timeline" says "get": a word for reading.
    Description, as the server wrote it
    Every dated event of one act, past and future, each classified: entry_into_force and application (kept apart, with their scope: the whole act, a staged tranche or a set of provisions), deadline (an obligation due date inside the act, never a state of any provision), transposition_deadline (directives; the subject is member_states), new_version (a change in the words, with the consolidated version), end_of_validity, and proposal (labelled proposed, never law). Each event states its date, kind, axis, subject and reach, scope, source, whether its date is held, and when it falls relative to as_at. The act's position (status and whom it is about) on as_at comes with it, with the coverage of what we hold. Answers "what is the full dated history and future of this act".

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
  • search_instrumentsFind 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 …1 finding

    Why it is in this group

    • The name "search_instruments" says "search": a word for reading.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...re calling the other tools. Requires no credentials."

      What this check looks for
    Description, as the server wrote it
    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, and web_url, the act's Lex-Ray page. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:55 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://stride.simmons-simmons.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://stride.simmons-simmons.com
Legacy HTTP+SSE transport
no
Dynamic client registration
no
Client ID metadata documents
no
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://stride.simmons-simmons.com/mcp/: tools/list returned 5 tools to an anonymous client, including about_this_server (write)

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • RFC 9728 protected resource metadata: https://stride.simmons-simmons.com/.well-known/oauth-protected-resource to https://stride.simmons-simmons.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: https://login.simmons-simmons.com/ to https://stride.simmons-simmons.com

Findings

Matches of fixed checks, with the text they matched.

3 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. RFC 9728 protected resource metadata: https://stride.simmons-simmons.com/.well-known/oauth-protected-resource -> https://stride.simmons-simmons.com/.well-known/oauth-protected-resource/mcp; Authorization servers: htt…View diff
    • RFC 9728 protected resource metadata: https://stride.simmons-simmons.com/.well-known/oauth-protected-resource to https://stride.simmons-simmons.com/.well-known/oauth-protected-resource/mcp
    • Authorization servers: https://login.simmons-simmons.com/ to https://stride.simmons-simmons.com
  2. Tools2 added, 2 changed.+2 added~2 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http stride https://stride.simmons-simmons.com/mcp/
claude mcp add --transport http stride https://stride.simmons-simmons.com/mcp/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__stride__search_instruments",
      "mcp__stride__get_legislation",
      "mcp__stride__get_timeline",
      "mcp__stride__get_changes"
    ],
    "ask": [
      "mcp__stride__about_this_server"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as stride. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/info.stride/stride/verify?hash=d1cf6bd349d299be4736c0d7cb1ae2a70a01722939adb66e4d4c52b23074282b" | jq -e '.changed == false'

Pinned hash d1cf6bd349d2, from Nov 15, 2026, 13:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/info.stride/stride/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for info.stride/stride
[![Anlyon Radar](https://radar.anlyon.com/badge/info.stride/stride.svg)](https://radar.anlyon.com/servers/info.stride/stride)

Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.

STRIDE MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the STRIDE MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 1 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the STRIDE MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the STRIDE MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the STRIDE MCP server have?

5 tools: 1 write, 4 read. about_this_server, search_instruments, get_legislation, get_timeline and get_changes.

Does the STRIDE MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the STRIDE MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the STRIDE MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.