STRIDE
info.stridev1.0.0Updated Oct 7, 2026
Digital-regulation tracking and analysis across jurisdictions; STRIDE access is required.
Overview
AI-generated overview
A remote MCP endpoint for tracking and analyzing digital regulation across jurisdictions, requiring STRIDE access.
- What it does
- STRIDE is a remote MCP server reachable at a hosted endpoint. According to its registry description, it covers digital-regulation tracking and analysis across jurisdictions. No tools are listed in the manifest, so the specific operations an assistant can call are not documented here.
- When to use it
- Consider it when an assistant needs to follow or analyze digital-regulation developments in more than one jurisdiction. It is only relevant if you already have STRIDE access, since the description states that access is required.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. The description states STRIDE access is required; the manifest declares no authentication method, environment variables, or headers, so how access is granted is not specified.
Before you install
The manifest declares no authentication, yet the description says access is required, so confirm with the provider how access and any credentials are handled before connecting. No tool list is published, so what the server can read or change is unclear. Treat any regulation data it returns as third-party content and verify it before relying on it.
Installation
In SourceWeft
- Open STRIDE in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"stride": {
"type": "http",
"url": "https://stride.simmons-simmons.com/mcp/"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestOct 7, 2026


