Agent Verify

Name: Agent Verify
Author: AI-Blockchain-Ventures

作者：AI-Blockchain-Ventures版本 2.0.0i★ –i在你的电脑上运行

注册名称io.github.AI-Blockchain-Ventures/agentverify

安装

概览

作者提供的说明（英文原文）

Security checks for AI agents and MCP configs: 124 tested checks, from your AI coding assistant.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：AGENTVERIFY_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： AGENTVERIFY_API_KEY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "agentverify": {
      "command": "npx",
      "args": [
        "-y",
        "agentverify",
        "mcp"
      ],
      "env": {
        "AGENTVERIFY_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add agentverify --env AGENTVERIFY_API_KEY=your-value -- npx -y agentverify mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentverify": {
      "command": "npx",
      "args": [
        "-y",
        "agentverify",
        "mcp"
      ],
      "env": {
        "AGENTVERIFY_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "agentverify": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "agentverify",
        "mcp"
      ],
      "env": {
        "AGENTVERIFY_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

AGENTVERIFY_API_KEY 机密必填 env
Your Agent Verify API key (dashboard → API / CLI). Free accounts work.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 AI-Blockchain-Ventures 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32680 个服务器的 0%
发布到注册中心的时间比此分类中其他 32680 个服务器的 90% 更新
基础检查结果等于或优于此分类中其他 32680 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Agent Verify 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：AGENTVERIFY_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（2.0.0）于3天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

EmbeddedCI BenchPod

作者：embeddedci-com

Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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 agentverify

agentverify 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 --help

agentverify --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.0

with: 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 install

npm 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.

Agent Verify

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“其他”中的其他服务器比较i

常见问题

替代选择

Spec Driven Development

Remote Desktop Commander

EmbeddedCI BenchPod

作者的 README

Agent Verify

Architecture

What this repo contains — open source vs. proprietary

Quick Start — CLI

GitHub Action

Web App

What Agent Verify analyzes

Verification output

Artifact fingerprinting / signed attestations

Policies

Security model

Privacy & proprietary scanner boundary

Plans

Documentation

Development

Limitations

License