Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Agent Verify
Overview
Description from the maker (original English)
Security checks for AI agents and MCP configs: 124 tested checks, from your AI coding assistant.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: AGENTVERIFY_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
AGENTVERIFY_API_KEY
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"agentverify": {
"command": "npx",
"args": [
"-y",
"agentverify",
"mcp"
],
"env": {
"AGENTVERIFY_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add agentverify --env AGENTVERIFY_API_KEY=your-value -- npx -y agentverify mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agentverify": {
"command": "npx",
"args": [
"-y",
"agentverify",
"mcp"
],
"env": {
"AGENTVERIFY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"agentverify": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentverify",
"mcp"
],
"env": {
"AGENTVERIFY_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Your Agent Verify API key (dashboard → API / CLI). Free accounts work.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account AI-Blockchain-Ventures, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32678 servers in this category
- Published to the registry more recently than 90% of the other 32678 servers in this category
- Basic checks equal to or better than 100% of the other 32678 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Agent Verify safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: AGENTVERIFY_API_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.0) reached the registry 3 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Starreel
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
Starreel
by starreel
Turn a script into a finished, downloadable short-drama episode — via MCP or REST.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Agent Verify
Know what your AI agent can do before you deploy it.
Agent Verify inspects an AI agent or agent package — its permissions, tools, MCP connections, execution controls, secrets, runtime configuration, and dependencies — and issues a VERIFIED or NOT VERIFIED result with evidence, before the agent reaches production.
Traditional security tools scan software. Agent Verify also examines what an AI agent is *connected to* and what those connections may let it actually *do* — a legitimate credential, valid API access, and an approved tool can still combine into an action the agent should never be able to take.
Agent Verify provides open-source CLI, CI, web integration, and API tooling backed by a proprietary verification engine — see Privacy & proprietary scanner boundary.
Architecture
Dashboard ─┐CLI ───────┼──► Worker API ──► server-side entitlement & scan quota ──► private scanner engine API ───────┘ │ └──► D1 (billing/quota) · Firestore (reports, orgs, audit log)
Every scan — from the dashboard, the CLI, or a direct API call — goes through the same authenticated Worker route and the same server-owned monthly quota; there is no client-only or local-storage-based scan counter anywhere in the product, and no browser code ever runs the detection engine directly. See Web App and Privacy & proprietary scanner boundary for how that boundary is enforced and verified.
What this repo contains — open source vs. proprietary
| Component | Location | License |
|---|---|---|
| Web app (dashboard, reports, landing page) | apps/web | Open source (this repo, MIT) |
CLI / SDK (agentverify on npm) | packages/cli | Open source (this repo, MIT) |
| Cloudflare Worker API | workers/api | Open source (this repo, MIT) |
Detection engine (@agentverify/scanner) | packages/scanner | Proprietary — not in this repository |
Quick Start — CLI
npm install -g agentverifyagentverify scan ./agents --key av_your_key
Get an API key from Dashboard → API access after signing in at https://aimodularity.com/agentverify/. Full docs, including the API contract, CI/CD integration, and JSON output shape: https://aimodularity.com/agentverify/docs/
agentverify --helpagentverify --version agentverify scan ./agents --key av_your_key # scan a directory agentverify scan --file agent.json --key av_your_key # scan a single file agentverify scan ./agents --key av_your_key --ci # CI mode, strict exit codes agentverify scan ./agents --key av_your_key --ci --policy standard # + policy evaluation
CI exit codes distinguish a real security failure from an execution problem:
| Code | Meaning |
|---|---|
0 | All scanned files verified |
1 | NOT_VERIFIED — a real security/verification failure |
2 | NOT_ASSESSED — insufficient evidence for a verdict |
3 | Execution error — bad/missing API key, network failure, missing file (not a security finding) |
GitHub Action
- uses: AI-Blockchain-Ventures/agentverify@v1.4.0with: path: ./agents api-key: ${{ secrets.AGENTVERIFY_API_KEY }}
See docs/github-action.md for the full reference — Markdown/JSON output modes, PR comment posting, branch protection, and policy evaluation in CI.
Web App
The dashboard (apps/web) provides scan history, report sharing, a check catalog, policy profiles, and organization/team management (roles: Owner/Admin/Member/Viewer) on top of the same Worker API the CLI uses — every dashboard scan is server-metered exactly like a CLI or API scan, never run or counted client-side.
What Agent Verify analyzes
Permissions and tool access, MCP server connections and what they expose, execution/authorization controls, secrets and credential handling, runtime configuration, and dependencies — static analysis of submitted content, not a live sandbox execution.
Verification output
- VERIFIED — sufficient execution context was assessed and the required trust controls passed.
- NOT VERIFIED — sufficient execution context was assessed and one or more security or protocol controls failed.
- NOT ASSESSED — the submitted content didn't contain enough agent execution context to make a decision. This is not a security failure, and it must never be read as VERIFIED.
Every finding is also labeled by how it was derived: definite (a concrete pattern was matched), heuristic (inferred from context — could be a false positive/negative), or informational (a neutral observation). Agent Verify does static analysis — it never executes submitted code — so it is honest about what it cannot see: see Limitations below.
Artifact fingerprinting / signed attestations
Every scan computes a SHA-256 artifact fingerprint over the exact scanned content — identical content always produces the same fingerprint, independent of when it ran or whether the ruleset changed since. When server-side signing is configured, a scan result can carry a signed attestation (ECDSA P-256 / ES256) over the verdict, score, and fingerprint — independently verifiable by any third party with nothing more than the published public key, with no shared secret and no need to trust Agent Verify's API at verification time.
Policies
Built-in policy profiles (standard, high-security, financial-agent, production-infrastructure) can be evaluated against a scan's evidence in addition to — never instead of — the base verdict: a scan can be VERIFIED and still fail a stricter policy, but a policy can never turn a NOT_VERIFIED scan into a pass. Pass --policy on the CLI or the policy input on the GitHub Action.
Security model
Billing, quota, and authentication are server-authoritative — see docs/billing-setup.md for the full architecture. Webhook payloads are signature-verified and processed idempotently, organization mutations are RBAC-enforced server-side (never trusting a client-supplied role), and Firestore Security Rules enforce per-user access control independently of the UI. Full detail and how to report an issue: SECURITY.md.
Privacy & proprietary scanner boundary
The detection engine — the actual rules that decide what's risky — is Agent Verify's core IP and is intentionally not tracked in this git repository (packages/scanner/ is gitignored). The CLI and Worker call it over HTTPS or via a private build; nothing in this public repo bundles or exposes its source, and no browser-shipped code ever imports it — only Worker-side (server-only) code does. A permanent CI check (npm run check:private-boundary) builds the web app and statically inspects every emitted client bundle for known proprietary markers on every change, so this boundary can't silently regress. Public CI validates the web app, CLI, and Worker against a type-compatible stub of the scanner (see scripts/create-ci-scanner-stub.mjs) so the public build is verifiable without the private engine ever being present.
Plans
Free (10 scans/month, basic findings, private report history), Pro ($19.99/month — full remediation guidance, corrected snippets, A2SPA implementation guidance, PDF export, 100 scans/month), Team (coming soon), Enterprise (contact us). Pricing is defined once in apps/web/src/lib/pricing.ts and mirrored in the Worker's quota table (workers/api/src/billing.ts) — see those files for the current source of truth.
Documentation
- App docs: https://aimodularity.com/agentverify/docs/
- GitHub Action reference: docs/github-action.md
- Billing/entitlement architecture: docs/billing-setup.md
- Proprietary scanner boundary: docs/private-scanner-boundary.md
- Roadmap: ROADMAP.md
- Changelog: CHANGELOG.md
Development
npm installnpm run dev # apps/web dev server npm run build # apps/web production build npm run build:cli # packages/cli npm run build:worker # workers/api npm run lint # apps/web npm run check:web # apps/web typecheck npm run check:worker # workers/api typecheck npm run test:worker # workers/api tests npm run test --workspace=packages/cli npm run test:rules # Firestore Security Rules against the real emulator npm run check:private-boundary # proprietary-boundary regression check
See CONTRIBUTING.md for the full contributor guide, including what you can and cannot modify and PR expectations.
Limitations
Agent Verify performs static analysis of submitted content. It does not execute your agent and cannot see: runtime-only behavior, permissions/credentials granted dynamically at deploy time, remote policy enforced outside the codebase, production network ACLs, external identity provider policy, or runtime secrets injected outside the source. Every report includes a "What Agent Verify Could Not Determine" section stating this explicitly for that scan. Findings are evidence-based and heuristic, not a formal proof of security — a clean report is not a guarantee of safety, and a finding is not proof of exploitation.
License
MIT — AI Blockchain Ventures LLC — hello@aiblockchainventures.com
MIT applies to the components in this repository (web app, CLI, Worker API) as listed above. The detection engine is proprietary, is not distributed under this license, and is not included in this repository.