E
eobi/nemesis_shield_sdks
Official, open-source SDKs for Nemesis Shield - the unified
updated 2026-10-09
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
eobi/nemesis_shield_sdks;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# Nemesis Shield - SDKs
Excerpted from the repository README (abridged)
Official, open-source SDKs for Nemesis Shield - the unified
runtime security platform (application/API/LLM shield, telemetry correlation, network/DNS, response,
and compliance). Drop one into your app and Nemesis learns your app's normal behavior, then
flags - and, in enforce mode, blocks - anything that deviates. It's a positive-security (allow-list)
model: instead of guessing at generic attack signatures, it enforces "this app only ever behaves
in these ways."
> Building with an AI assistant? Two ways to make your agent add Nemesis Shield as it builds:
> 1. MCP server - gives Cursor, Claude Code/Desktop and Windsurf 17 callable tools
> (nemesis_protect, nemesis_scan, nemesis_explain, plus Omniguard fraud scoring and standalone
> identity/AML screening via nemesis_omniguard_verify) so the agent adds security, scans a site,
> screens identities, and explains coverage without leaving the editor.
> 2. AI editor rule pack (AGENTS.md, Cursor, Windsurf, Claude Code) - drop-in rules
> that tell the agent to add the one-line SDK by default.
> Both are one line per stack, safe by default (observe mode). Full verified reference:
> ai-rules/AGENTS.md.
Privacy by design: the SDKs ship only behavioral metadata - HTTP method, the shape of the
path (/orders/123 → /orders/{int}), status code, and whether the caller was authenticated. They
never send your request bodies, responses, secrets, or source code. Every SDK is fail-open: if
Nemesis is unreachable, your app is completely unaffected.
> New app? Finish learning in minutes with Nemesis Learn. Drop in an SDK (observe mode),
> then run one command and the agent exercises every route of your app in dev/staging - endpoints,
> forms, uploads, CRUD flows - so the baseline completes without waiting on real traffic. It's
> language- and framework-agnostic (drives your app over HTTP), runs offline, can read your repo to
> find routes, and reports coverage back so the console shows exactly when you're ready to enforce.
> bash
> npx @nemesis-shield-autogon/learn --target http://localhost:3000 --app-token nsk_… --repo .
| Language | Package | Integration |
| Node.js | @nemesis-shield-autogon/sentinel | One-line Express/Connect middleware → node/ |
| Python | nemesis-shield | ASGI/WSGI middleware (FastAPI/Starlette/Flask) → python/ |
| Go | github.com/eobi/nemesis_shield_sdks/go | net/http middleware → go/ |
| Ruby | nemesis_shield.rb | Rack middleware (Rails/Sinatra) → ruby/ |
| PHP | composer require nemesislabs/sentinel | Laravel auto-discovery / register_shutdown_function → php/ |
| WordPress | drop-in plugin | Behavioral firewall (front end, REST & admin-ajax) + brute-force lockout, malware / file-integrity scan & vulnerability alerts → wordpress/ |
| Java | io.github.eobi:sentinel | Servlet filter / Spring Boot (JDK 11+) → java/ |
| .NET / C# | dotnet add package NemesisShield | ASP.NET Core middleware (net8.0 + netstandard2.0) → dotnet/ |
| Rust | cargo add nemesis-shield | axum (tower) / actix-web middleware → rust/ |
| Edge / Supabase (Deno TS) | @nemesis-shield-autogon/edge (npm) · @nemesis-shield/edge (JSR) | withShield() for Supabase Edge / Deno / CF Workers / Vercel Edge / Next.js → edge/ |
runtime security platform (application/API/LLM shield, telemetry correlation, network/DNS, response,
and compliance). Drop one into your app and Nemesis learns your app's normal behavior, then
flags - and, in enforce mode, blocks - anything that deviates. It's a positive-security (allow-list)
model: instead of guessing at generic attack signatures, it enforces "this app only ever behaves
in these ways."
> Building with an AI assistant? Two ways to make your agent add Nemesis Shield as it builds:
> 1. MCP server - gives Cursor, Claude Code/Desktop and Windsurf 17 callable tools
> (nemesis_protect, nemesis_scan, nemesis_explain, plus Omniguard fraud scoring and standalone
> identity/AML screening via nemesis_omniguard_verify) so the agent adds security, scans a site,
> screens identities, and explains coverage without leaving the editor.
> 2. AI editor rule pack (AGENTS.md, Cursor, Windsurf, Claude Code) - drop-in rules
> that tell the agent to add the one-line SDK by default.
> Both are one line per stack, safe by default (observe mode). Full verified reference:
> ai-rules/AGENTS.md.
Privacy by design: the SDKs ship only behavioral metadata - HTTP method, the shape of the
path (/orders/123 → /orders/{int}), status code, and whether the caller was authenticated. They
never send your request bodies, responses, secrets, or source code. Every SDK is fail-open: if
Nemesis is unreachable, your app is completely unaffected.
> New app? Finish learning in minutes with Nemesis Learn. Drop in an SDK (observe mode),
> then run one command and the agent exercises every route of your app in dev/staging - endpoints,
> forms, uploads, CRUD flows - so the baseline completes without waiting on real traffic. It's
> language- and framework-agnostic (drives your app over HTTP), runs offline, can read your repo to
> find routes, and reports coverage back so the console shows exactly when you're ready to enforce.
> bash
> npx @nemesis-shield-autogon/learn --target http://localhost:3000 --app-token nsk_… --repo .
| Language | Package | Integration |
| Node.js | @nemesis-shield-autogon/sentinel | One-line Express/Connect middleware → node/ |
| Python | nemesis-shield | ASGI/WSGI middleware (FastAPI/Starlette/Flask) → python/ |
| Go | github.com/eobi/nemesis_shield_sdks/go | net/http middleware → go/ |
| Ruby | nemesis_shield.rb | Rack middleware (Rails/Sinatra) → ruby/ |
| PHP | composer require nemesislabs/sentinel | Laravel auto-discovery / register_shutdown_function → php/ |
| WordPress | drop-in plugin | Behavioral firewall (front end, REST & admin-ajax) + brute-force lockout, malware / file-integrity scan & vulnerability alerts → wordpress/ |
| Java | io.github.eobi:sentinel | Servlet filter / Spring Boot (JDK 11+) → java/ |
| .NET / C# | dotnet add package NemesisShield | ASP.NET Core middleware (net8.0 + netstandard2.0) → dotnet/ |
| Rust | cargo add nemesis-shield | axum (tower) / actix-web middleware → rust/ |
| Edge / Supabase (Deno TS) | @nemesis-shield-autogon/edge (npm) · @nemesis-shield/edge (JSR) | withShield() for Supabase Edge / Deno / CF Workers / Vercel Edge / Next.js → edge/ |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/eobi-nemesis-shield-sdks-tree-main-mcp/)
- Source
- awesome · https://github.com/eobi/nemesis_shield_sdks/tree/main/mcp
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.