Log inSubmit server
Nemesis Shield logo

Nemesis Shield

MCP tools for adding Nemesis Shield protection, scanning sites, explaining coverage, and screening identities.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Nemesis Shield

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "nemesis-shield": {
      "command": "npx",
      "args": [
        "-y",
        "@nemesis-shield-autogon/learn"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y @nemesis-shield-autogon/learn

Process exited before answering initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

The nemesis-shield MCP server gives Cursor, Claude Code, Claude Desktop, and Windsurf callable tools for Nemesis Shield security workflows. It lets an AI agent add SDK-based application protection, scan a site, explain security coverage, score fraud risk, and perform identity or AML screening. Reach for it when you want an editor-based agent to configure runtime security or inspect an application without switching tools. The repository also provides SDKs for multiple backend stacks, browser applications, WordPress, and edge runtimes.

Use cases

  • Add Nemesis Shield middleware while building an application
  • Scan a deployed site for security issues
  • Explain an application’s Nemesis Shield coverage
  • Score fraud risk with Omniguard
  • Screen identities for identity and AML checks

Key features

  • 17 callable MCP tools
  • Application protection setup
  • Site scanning
  • Security coverage explanations
  • Omniguard fraud scoring
  • Identity and AML screening

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 57d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · @nemesis-shield-autogon/learn (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads34Package downloads in the last 30 days.
Last commit1mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.

How Nemesis Shield works

What nemesis-shield does

The nemesis-shield MCP server exposes Nemesis Shield actions to AI coding assistants through 17 callable tools. Its documented tool set includes nemesis_protect for adding security protection, nemesis_scan for scanning a site, and nemesis_explain for describing coverage. It also includes Omniguard fraud scoring and standalone identity and AML screening through nemesis_omniguard_verify.

The server is intended for agents working inside Cursor, Claude Code, Claude Desktop, or Windsurf. An agent can use the tools while building an application, rather than requiring the developer to perform each security setup step manually in a separate console.

How it works

Nemesis Shield uses a positive-security model based on an application’s observed behavior. Its SDKs learn a per-application baseline, then can flag or block requests that do not match approved behavior when enforcement is enabled. The default operating mode is observe, allowing the application to build a baseline before enforcement is turned on.

The SDKs compute request shape locally and make enforcement decisions in the application process before the request reaches the handler. They report behavioral metadata such as HTTP method, normalized path shape, response status, and authentication state. SDKs fail open if Nemesis is unreachable.

Tools and capabilities

The nemesis-shield MCP server supports these documented workflows:

  • Add Nemesis Shield protection while building an application.
  • Scan a website.
  • Explain the security coverage applied to an application.
  • Perform Omniguard fraud scoring.
  • Verify identities with standalone identity and AML screening.

The broader repository includes SDK integrations for Node.js, Python, Go, Ruby, PHP, WordPress, Java, .NET, Rust, edge runtimes, Supabase direct database APIs, and browser front ends. Those integrations are separate from the MCP tool interface but provide the runtime components an agent may add to an application.

Setup and configuration

The repository places the MCP implementation in the mcp/ directory.

Using Nemesis Shield requires an account at shield.nemesislabs.xyz and an application install token. The documented SDK setup uses tokens beginning with nsk_, supplied through application configuration such as NEMESIS_TOKEN. For SDK-based protection, the developer adds the package or middleware for the target stack, deploys in observe mode, reviews learned behavior in the console, and then enables enforcement there.

Limitations and notes

Confirm those details in the repository’s mcp/ directory before automating installation or configuration.

MCP access does not by itself describe the runtime protection of an application. The relevant SDK or plugin still needs to be added to the target stack. Browser protection, WordPress scanning features, edge middleware, and Supabase proxy protection are separate repository integrations with their own setup paths.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Nemesis Shield

nemesis-shield is an MCP server that connects AI coding assistants to Nemesis Shield security workflows. Its tools can add application protection, scan a site, explain coverage, score fraud risk through Omniguard, and perform standalone identity and AML screening.

It places the implementation in the repository’s `mcp/` directory and names Cursor, Claude Code, Claude Desktop, and Windsurf as supported environments, so consult that directory for the current setup instructions.

Yes, the README names Cursor as a supported client. The MCP tools let a Cursor agent add Nemesis Shield protection, scan a site, explain coverage, and use the documented Omniguard fraud and identity/AML screening workflows.

Nemesis Shield uses an application install token obtained after signing up and protecting an app at `shield.nemesislabs.xyz`.

Related MCP servers

All in Security All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNemesis Shield AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nemesis-shield?style=directory)](https://allmcps.com/mcp/nemesis-shield)
HTML Embed
<a href="https://allmcps.com/mcp/nemesis-shield"><img src="https://allmcps.com/api/badge/nemesis-shield?style=directory" alt="Nemesis Shield on AllMCPs" /></a>