Log inSubmit server

AFMR Discovery vs North Dakota Code

A side-by-side look at the AFMR Discovery 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.

A
AFMR DiscoveryLegalRead AFMR failure modes and discover scoped attestation and lift-evidence contracts.37FairAuth: not declaredNorth 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 AFMR Discovery for legal work; 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?

A
Choose AFMR Discovery when

  • You need dedicated capabilities in the Legal domain.
Explore AFMR Discovery

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
A
AFMR Discovery		North Dakota Code logoNorth Dakota Code
CategoryLegalLegal
Quality signal37/100 · Fair45/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—0
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed
Full listingView AFMR Discovery View North Dakota Code

Tools & capabilities

AFMR Discovery 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.

AFMR Discovery

No confirmed install command for AFMR Discovery yet — follow the setup steps linked from its listing page rather than a guessed package name.

North Dakota Code

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

Frequently asked questions

AFMR Discovery is categorized under Legal and uses an install path we have not confirmed yet. North Dakota Code belongs to Legal and uses a local stdio subprocess. Pick AFMR Discovery 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. AFMR Discovery has no confirmed install command yet — follow its own setup instructions.

AFMR Discovery 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 afmr-discovery and north-dakota-code as separate keys in the same mcpServers object, and your assistant will call tools from either one.

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

Popular comparisons with AFMR Discovery

Popular comparisons with North Dakota Code