A
ankush1982/ai-secure-by-design
The same security and privacy checks, whichever AI wrote the code.
★ 4·updated 2026-11-05
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 →
- Star count
- 4 ★ · ankush1982/ai-secure-by-design · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- 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 · 4 ★ · 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
ankush1982/ai-secure-by-design;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 →
The same security and privacy checks, whichever AI wrote the code.
Excerpted from the repository README (abridged)
A deterministic engine, plus editable scaffolds for consent, audit logs, data rights and AI oversight.
Quick start ·
What it covers ·
What it detects ·
How it works ·
Platforms ·
What this is not ·
Roadmap ·
Contributing
AI coding tools write code quickly and forget rules quietly. Secure & Private by Design moves the rules out of the prompt and into an engine that gives the same answer every time, then runs that engine in your editor, your git hooks and your CI.
Tell it what your product does and which regimes you target. It profiles your codebase, asks you to classify your data, and deploys dev-loop controls (hooks, skills, slash commands, subagents, an MCP server) and product-code scaffolds tailored to your stack.
## Why use it
Secrets and personal data get blocked. Hardcoded keys, Aadhaar numbers, PAN, mobile numbers and emails are stopped in Claude Code, at commit and in CI, and reports never repeat the value.
Checks are code, not prompts. Claude, GPT, Gemini and a human running the CLI all see the same findings, each with a stable rule ID, a severity and a location.
Your manifest is the source of truth. One YAML file records your data categories, regimes, retention and consent. Only the regimes you list are enforced, and the tool never classifies a field for you.
You own the scaffolds. Consent, data rights, audit logging, RBAC, PHI redaction and AI decision logs land in your repo as ordinary code you can edit or delete.
Everything runs locally. No telemetry and no hosted service.
## See it run
sbd check on the sample app in mcp-server/test/fixtures/clinic-app (trimmed):
text
Manifest: privacy-security-manifest.yaml (schemaVersion 0.2)
Regimes: nist-ssdf-1.1, iso-27001-2022, dpdp-2023
1. [CRITICAL] SBD-SCAF-001 Missing src/privacy/consent. (Consent scaffold).
→ Copy templates/typescript-express/consent.ts to src/privacy/consent.ts, or run sbd deploy.
10. [HIGH] SBD-FIELD-001 prisma/schema.prisma:5 — Field dateOfBirth looks personal or sensitive but no dataCategory lists it.
12. [HIGH] SBD-CODE-002 src/routes/patients.ts:19 — Log call references a field the manifest classifies as personal or sensitive.
console.log('loaded patient', patient.email);
→ Route the value through the redacting logger in src/security/audit_log.
13. [HIGH] SBD-CODE-003 src/services/triage.ts:6 — Model inference call with no decision-log call within 15 lines.
16. [MEDIUM] SBD-CODE-001 src/routes/patients.ts:12 — Handler mutates data without an auditLog() call within 40 lines.
17 finding(s): 2 critical, 11 high, 3 medium, 1 low, 0 info.
This report lists control gaps. It is not a compliance determination.
## What it covers
| Regime | Scope |
| NIST SSDF 1.1 | Secure SDLC baseline — applies to every project |
| ISO 27001:2022 | Annex A controls relevant to the dev/SDLC slice (A.5.15, A.5.34, A.8.5, A.8.10–.12, A.8.15, A.8.24–.32) |
| DPDP Act 2023 (India) | Notice, consent, data principal rights, retention, breach notification, children's data gate, Significant Data Fiduciary flagging |
| AI Security Wiki (optional) | The community AI Security Wiki control library (46 AI controls) plus AI-specific checks on model output, model loading, MCP servers and agent permissions. A practitioner reference, not a law. See AI Security Wiki integration |
Quick start ·
What it covers ·
What it detects ·
How it works ·
Platforms ·
What this is not ·
Roadmap ·
Contributing
AI coding tools write code quickly and forget rules quietly. Secure & Private by Design moves the rules out of the prompt and into an engine that gives the same answer every time, then runs that engine in your editor, your git hooks and your CI.
Tell it what your product does and which regimes you target. It profiles your codebase, asks you to classify your data, and deploys dev-loop controls (hooks, skills, slash commands, subagents, an MCP server) and product-code scaffolds tailored to your stack.
## Why use it
Secrets and personal data get blocked. Hardcoded keys, Aadhaar numbers, PAN, mobile numbers and emails are stopped in Claude Code, at commit and in CI, and reports never repeat the value.
Checks are code, not prompts. Claude, GPT, Gemini and a human running the CLI all see the same findings, each with a stable rule ID, a severity and a location.
Your manifest is the source of truth. One YAML file records your data categories, regimes, retention and consent. Only the regimes you list are enforced, and the tool never classifies a field for you.
You own the scaffolds. Consent, data rights, audit logging, RBAC, PHI redaction and AI decision logs land in your repo as ordinary code you can edit or delete.
Everything runs locally. No telemetry and no hosted service.
## See it run
sbd check on the sample app in mcp-server/test/fixtures/clinic-app (trimmed):
text
Manifest: privacy-security-manifest.yaml (schemaVersion 0.2)
Regimes: nist-ssdf-1.1, iso-27001-2022, dpdp-2023
1. [CRITICAL] SBD-SCAF-001 Missing src/privacy/consent. (Consent scaffold).
→ Copy templates/typescript-express/consent.ts to src/privacy/consent.ts, or run sbd deploy.
10. [HIGH] SBD-FIELD-001 prisma/schema.prisma:5 — Field dateOfBirth looks personal or sensitive but no dataCategory lists it.
12. [HIGH] SBD-CODE-002 src/routes/patients.ts:19 — Log call references a field the manifest classifies as personal or sensitive.
console.log('loaded patient', patient.email);
→ Route the value through the redacting logger in src/security/audit_log.
13. [HIGH] SBD-CODE-003 src/services/triage.ts:6 — Model inference call with no decision-log call within 15 lines.
16. [MEDIUM] SBD-CODE-001 src/routes/patients.ts:12 — Handler mutates data without an auditLog() call within 40 lines.
17 finding(s): 2 critical, 11 high, 3 medium, 1 low, 0 info.
This report lists control gaps. It is not a compliance determination.
## What it covers
| Regime | Scope |
| NIST SSDF 1.1 | Secure SDLC baseline — applies to every project |
| ISO 27001:2022 | Annex A controls relevant to the dev/SDLC slice (A.5.15, A.5.34, A.8.5, A.8.10–.12, A.8.15, A.8.24–.32) |
| DPDP Act 2023 (India) | Notice, consent, data principal rights, retention, breach notification, children's data gate, Significant Data Fiduciary flagging |
| AI Security Wiki (optional) | The community AI Security Wiki control library (46 AI controls) plus AI-specific checks on model output, model loading, MCP servers and agent permissions. A practitioner reference, not a law. See AI Security Wiki integration |
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/ankush1982-ai-secure-by-design/)
- Source
- awesome · https://github.com/ankush1982/ai-secure-by-design
- Browse by field
- MCP servers
- Traction
- 4 ★
- 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.