Cursor apps, checked against your rules
Your teams build in Cursor, inside the repository they already use. NEKOD checks those apps against your own rules and shows the evidence.
Findings and fix prompts come back into the editor through MCP. When the rules pass, the approval stays on record.
Book a DemoWhy Cursor apps need your rules
Cursor edits the repository directly: several files, a config, and a test can change in one session. A domain expert can land a working change without waiting on a backlog.
One accepted change can touch an access key, an auth path, or a database rule. NEKOD checks the app against your rules. Data stays read-only by default, and the fix prompt comes back into Cursor through MCP.

Stacks Cursor projects often use
TypeScript / Python
Full-stack languages
React / Next.js
Frontend frameworks
Supabase / Postgres
Database & auth
GitHub repos
Connect read-only
Node / FastAPI
API backends
Vercel / AWS
Deployment targets
Cursor in your company
- What it is
- An AI code editor. It edits the repository directly, across files, with an agent.
- Who builds with it
- Technical business users and engineers who work inside a repository every day.
- What gets built
- Internal tools, integrations and services, from a config change to a full app.
- Where it lives
- A Git repository on the builder's machine, usually synced to GitHub.
Why use Cursor with NEKOD
Cursor gives your teams
- Several files, a config and a test changed in one session
- An agent that works inside the repository you already use
- A fast loop between idea and working change
NEKOD gives your company
- Your written rules checked on the app, with the evidence
- Findings, controls and fix prompts in the editor through NEKOD MCP
- An owner, a risk level and a recorded approval for each app
How NEKOD works with Cursor
- 01
Connect the repository
Connect the repositories read-only. Data stays read-only by default, and NEKOD lists the apps.
- 02
Check against your rules
NEKOD checks the app against your rules, including access keys, sign-in paths and database rules.
- 03
Fix in Cursor
NEKOD MCP brings the finding and the fix prompt into the editor, so the builder fixes it in the same session.
- 04
Approve with a record
When the rules pass, the app goes to the right approver. The decision and the evidence behind it stay on record.
What We Check
Checks against your rules, with fix prompts back in Cursor

Repo-wide AI edits
Cursor changes span files, configs, and tests in one session. We verify architecture coherence, dead code, unsafe patterns, and unintended side effects.
Secrets & API keys
Hard-coded tokens, leaked .env values, exposed service keys, and insecure credential handling across the branches Cursor touched.
Auth, data & access
RLS policies, API route guards, session handling, and database access patterns introduced during AI-assisted refactors.
Dependencies & deploy readiness
Vulnerable packages, missing env examples, broken CI checks, and production gaps before you release what Cursor helped you build.
A check against your rules, and a fix in the tool your team already uses.

Critical · Security
Admin export route has no role check
Fixed · Security
Admin export route has no role check
Prioritized fix list
Every finding comes with its severity, a plain-English explanation and what to fix next. The builder pastes the fix prompt back into Cursor.

Applications
- Approved
Supplier onboarding
Owner: Procurement
- Fixes needed
Expense checker
Owner: Finance
- In review
Shift planner
Owner: Operations
Approved by Risk
Supplier onboarding · all checks passed · evidence attached
Approval on record
Approvers see every application with its owner and status. Each decision is recorded with the evidence behind it.

The line that failed
Admin export route has no role check in app/api/admin/export/route.ts:9
Any signed-in user can export admin data
The route checks that someone is logged in, not that they are an admin. Add a role check.
Plain language
Every issue comes with a plain-English title, why it matters, and what to fix, so approvers can follow it too.

Critical · Security
Any signed-in user can export admin data
The route checks that someone is logged in, not that they are an admin. Add a role check.
Report assessment
Each check leaves a record: the findings that matter, and a fix prompt in plain language.
Frequently Asked Questions
No. Cursor builds in the repository. NEKOD holds your rules, checks the app, and keeps the approval on record. It works next to Cursor.
NEKOD MCP brings findings, controls and fix prompts into Cursor. The builder stays in the editor and applies the fix there. Access is read-only.
No. NEKOD reads repositories through a GitHub App, and you choose which repositories to share. Access is read-only. NEKOD does not change the code when it checks an app.
NEKOD checks the app against your written policy and shows the evidence. One change in Cursor can touch an access key, an auth path, or a database rule. NEKOD names what failed.
Yes. NEKOD does not replace your engineers or your security team. It checks first against your rules and records the approval, so reviewers see a prepared app.
Start with the Cursor apps your teams already build
NEKOD checks each app against your rules and brings findings back into Cursor through MCP.


