CrashStory MCP vs North Dakota Code

A side-by-side look at the CrashStory MCP and North Dakota Code MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

C
CrashStory MCPLegal · Remote HTTP/SSE
Colorado personal injury attorney directory, AI-analyzed review intelligence, and crash data42FairAuth: not declared
North Dakota Code logoNorth Dakota CodeLegal · Local subprocess (stdio)North Dakota Century Code — state statutes by citation and by topic.45FairAuth: no auth required

Verdict: choose CrashStory MCP for legal work over a hosted endpoint; choose North Dakota Code for legal as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

C
Choose CrashStory MCP when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a remote HTTP/SSE transport.
Explore CrashStory MCP

North Dakota Code logoChoose North Dakota Code when

  • You need dedicated capabilities in the Legal domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore North Dakota Code

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
C
CrashStory MCP
North Dakota Code logoNorth Dakota Code
CategoryLegalLegal
Quality signal42/100 · Fair45/100 · Fair
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—0
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

CrashStory MCP tools

No tool names declared yet. Check the project README from the listing page.

North Dakota Code tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

CrashStory MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "crashstory-mcp": {
      "url": "https://crashstory.com/mcp"
    }
  }
}

North Dakota Code

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "north-dakota-code": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-north-dakota-code"
      ]
    }
  }
}

Frequently asked questions

CrashStory MCP is categorized under Legal and uses a remote HTTP/SSE transport. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick CrashStory MCP for legal work and North Dakota Code for legal.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

CrashStory MCP has no declared pricing — check the project's own site. North Dakota Code is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add crashstory-mcp and north-dakota-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CrashStory MCP has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. North Dakota Code has 45/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.