BackBond Agent Scan

Name: BackBond Agent Scan
Author: BackBond

제작자: BackBond버전 0.6.3i★ –i내 컴퓨터에서 실행

레지스트리 이름io.github.BackBond/agent-scan

설치

개요

제작자가 쓴 설명(영어 원문)

Vet MCP tool manifests before attachment; returns block, review, or no blocking finding.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
사용 정도i아직 측정 안 함★ –

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

연결 방식: 내 컴퓨터에서 실행
전송 방식: stdio
카테고리: 기타

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

기본 점검: 1개 중 1개 통과
내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
레지스트리에 입력해야 할 키가 나와 있지 않아요.

필요한 것

npmNode.js 설치(npx 명령어용)

어떤 앱을 쓰세요?

ClaudeClaude CodeCursorVS CodeChatGPT

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요

{
  "mcpServers": {
    "agent-scan": {
      "command": "npx",
      "args": [
        "-y",
        "@backbond/agent-scan",
        "mcp"
      ]
    }
  }
}

터미널에서 이 명령어를 실행하세요

claude mcp add agent-scan -- npx -y @backbond/agent-scan mcp

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "agent-scan": {
      "command": "npx",
      "args": [
        "-y",
        "@backbond/agent-scan",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "agent-scan": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@backbond/agent-scan",
        "mcp"
      ]
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검

✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 BackBond 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
… 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
… 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
– 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
– 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
… 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요

기타 카테고리의 다른 서버와 비교i

이 카테고리의 다른 서버 32398개 중 0%보다 스타가 많아요
이 카테고리의 다른 서버 32398개 중 45%보다 최근에 레지스트리에 공개됐어요
기본 점검 결과가 이 카테고리의 다른 서버 32398개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

BackBond Agent Scan, 안전한가요?

해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.6.3)은 2개월 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, AI Deprecations

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ 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어제 업데이트

설치

AI Deprecations

제작자: aideprecations.com

AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.

클라우드에서 실행오늘 업데이트

설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

BackBond Agent Scan

BackBond Agent Scan is published as the exact scoped package @backbond/agent-scan@0.6.3. Static only: it inspects tool metadata and agent configuration already on your machine. It does not run tools, probe a live agent, upload traces, contact a hosted service, or execute a second binary.

If a result from this scanner or from a BackBond publication looks wrong, open a correction through the false-positive form. We respond within 72 hours.

Try the browser preview

Watch the 50-second synthetic walkthrough, then try the synthetic example. The silent video has on-screen text and a transcript. It shows a verified scanner 0.6.3 result for supplied metadata, not runtime behavior.

Try Agent Scan in your browser: three synthetic MCP examples, followed by a local check of your own tools/list JSON. No account or installation is required. The page processes the manifest in memory without uploading it.

The browser preview uses Agent Scan 0.6.3 and checks supplied MCP tool metadata only, up to 200 tools and 256 KiB. It does not assess runtime behavior, and a non-blocking result is not a safety determination or insurance decision. Use the pinned CLI below for other supported formats, larger inputs, or offline workflows.

Static MCP tool manifest inspection

BackBond Agent Scan helps operators vet MCP tools before attachment through local, deterministic static MCP tool manifest inspection. It reports findings and missing evidence without executing proposed tools. Results do not establish runtime safety.

Vet MCP tools before attachment

Export the proposed server's real tools/list response, then inspect that supplied manifest with the pinned vet-tools instructions below. A block result stops automatic attachment; review requires operator review; no_blocking_finding means no configured blocking rule fired on the supplied metadata. The scanner itself does not enforce attachment or create insurance coverage.

Install from a trusted host first

For operator-enforced checks on an existing stdio MCP connection, see the separate Agent Scan stdio gate. It starts the authorized server and gates tool attachment and calls; it is not included in the scanner npm package, does not sandbox startup, and does not verify runtime behavior. The checksum-verified standalone scanner and pinned npm paths below remain available for manual checks.

For a hardened or network-isolated agent, an operator should download the single-file release asset and checksum on a network-enabled trusted host, verify it, and transfer the verified file through the organization's approved software path:

curl -fLO https://github.com/BackBond/agent-scan/releases/download/v0.6.3/agent-scan.cjs

curl -fLO https://github.com/BackBond/agent-scan/releases/download/v0.6.3/agent-scan.cjs.sha256 sha256sum --check agent-scan.cjs.sha256 node agent-scan.cjs scan

Before attaching a proposed MCP or supported function-tool list, first save the real exported manifest as tools-list.json in the current directory. vet-tools reads that file; it does not create it:

node agent-scan.cjs vet-tools --stdin < tools-list.json

agent-scan.cjs is an unminified, auditable, dependency-free build of the same tagged CLI. It runs scan, vet-tools, and the mcp stdio entrypoint without npm installation or network access.

Verify the published bytes

The protected release workflow publishes package-registry provenance and attaches the registry-authoritative tarball, its SHA-256, the deterministic standalone file, and its SHA-256 to the matching source tag. A reviewer can rebuild both artifacts from public source:

git clone --depth 1 --branch v0.6.3 https://github.com/BackBond/agent-scan.git

cd agent-scan npm pack sha256sum backbond-agent-scan-0.6.3.tgz node scripts/build-standalone.js agent-scan.cjs sha256sum agent-scan.cjs

Compare both computed digests with the .sha256 files on the official v0.6.3 release. A mismatch is a stop condition. Provenance describes the protected build; byte-for-byte reproduction independently connects the public tag to the released artifacts. Neither is a runtime attestation or insurance decision.

Network-isolated agent

If the agent shell has PrivateNetwork=true, only loopback, no routes, or AF_INET disabled, remote package, source, and server registries cannot deliver software into that shell. Do not weaken the sandbox for this scanner. Stage the pinned agent-scan.cjs and its checksum outside the sandbox, verify it there, transfer it through an approved shared path or image, and run it locally with node. A failed download means scan_not_run, never a zero-finding result.

Developer-laptop convenience

On a network-enabled development machine, the exact npm version remains a convenient equivalent:

npx -y @backbond/agent-scan@0.6.3 scan

npx -y @backbond/agent-scan@0.6.3 vet-tools --stdin < tools-list.json npx -y @backbond/agent-scan@0.6.3 vet-tools --stdin --summary-only < tools-list.json

The second and third commands require an existing tools-list.json. If you have not exported a live tool manifest yet, run the first scan command; do not pipe a missing or invented file into vet-tools.

Install the version-pinned Agent Skill

Compatible agents can install the standard skill directly from the immutable release tag:

npx -y skills@1.5.18 add https://github.com/BackBond/agent-scan/tree/v0.6.3 --skill agent-scan --yes

That installer is separate software that fetches the tagged public repository; review its own network and telemetry behavior before using it in a restricted environment. Installing the skill does not run a scan. The repository is also a skill-only Agent Plugin with no hooks, commands, or plugin-level MCP configuration.

For manual installation, copy the entire skills/agent-scan folder to:

.agents/skills/agent-scan/

The installed file must be .agents/skills/agent-scan/SKILL.md. It keeps commands pinned to 0.6.3, treats coverage gaps as unknown rather than safe, and tells agents never to post raw manifests, traces, prompts, full JSON reports, or path-bearing receipts. It permits the identity-free summary-only output for aggregate work. See the plugin notes and the reusable AGENTS.md policy block.

The distribution directory contains the canonical launch message, cross-platform install cards, sanitized demos, privacy-safe outreach, and the first-five-runs launch gate. Public copy should come from that kit rather than being rewritten with @latest or stronger claims.

vet-tools returns block (exit 1), review when a medium finding or incomplete/ambiguous evidence requires operator review (exit 3), or no_blocking_finding (exit 0). It checks supplied tool identities, descriptions, input schemas, and same-manifest composition. A non-blocking result requires unambiguous tool names, a description or title, and one analyzable object input schema per tool; opaque branches, conflicting schema aliases, mixed manifest dialects, non-ASCII identities, confusable-name collisions, directive-like text framed as an example, or schemas beyond the bounded local analysis budget cannot produce a non-blocking result. Full JSON includes a canonical profile digest and an actionable review_items array. Each item gives a stable code, affected-tool count when observable, reason, evidence needed, and next step without changing the decision or applying a fix. It does not assess runtime enforcement, approvals, audit behavior, traces, or actual execution. no_blocking_finding is not a safety determination or runtime attestation.

For large operator-staged runs, --summary-only emits one compact backbond-vet-summary/v1 JSON object per invocation, suitable for JSONL collection. It includes the decision, version tuple, finding counts, rule and coverage-code histograms, actionable review items, and prompt-template multiplicity. It preserves the normal 0/1/3 decision exits while omitting tool and server identities, tool descriptions, artifact names, evidence pointers, and template hashes. It cannot be combined with --json, --sarif, or --suggest-policy. Because template identifiers are omitted, summary-only rows cannot establish that the same template appeared in different manifests; their multiplicity is within one supplied manifest. The scanner still accepts only a local manifest and does not collect from a Registry or call scanned tools.

From this repository, prove the whole rule pack with the two fixtures:

node bin/agent-scan.js scan --tool-schema fixtures/vulnerable/tool-schema.json --permissions fixtures/vulnerable/permissions.json --trace fixtures/vulnerable/trace.json

node bin/agent-scan.js scan --tool-schema fixtures/hardened/tool-schema.json --permissions fixtures/hardened/permissions.json --trace fixtures/hardened/trace.json

The vulnerable case exits 1 with BB001–BB013. The hardened case exits 0 with no findings and complete coverage.

Scanner execution is local and makes no network requests. First-time npx installation must reach the configured npm registry unless this exact version is already cached.

If npm is unavailable

EAI_AGAIN, ENETUNREACH, and registry timeouts happen before the scanner starts. Stop after one failed installation attempt and report that no scan ran. Do not switch to @latest, change npm registries, disable TLS checks, or accept a package path sent in chat.

The standalone asset above is the simplest offline path. An operator may instead download backbond-agent-scan-0.6.3.tgz and its .sha256 file from the official v0.6.3 source release and transfer both through the organization's trusted software path. Verify the transferred bytes at the destination immediately before running them:

sha256sum --check backbond-agent-scan-0.6.3.tgz.sha256

npm exec --yes --offline --package=./backbond-agent-scan-0.6.3.tgz -- agent-scan scan

On Windows PowerShell, compare (Get-FileHash .\backbond-agent-scan-0.6.3.tgz -Algorithm SHA256).Hash with the first value in the .sha256 file and stop on any mismatch.

The source-release tarball is the same tarball published to the package registry. If neither the pinned package nor a verified operator-provided tarball is available, the honest result is scan_not_run, not a zero-finding report.

Zero-config first run

scan with no artifact arguments performs bounded discovery. It checks project ancestors and known user paths for supported desktop and coding-agent MCP settings, portable .mcp.json files, and nearby AGENTS.md or SKILL.md instruction files. Instruction files are listed but never interpreted as security controls.

Discovery reads exact known files; it does not recursively crawl the home directory. A configured MCP server without an exported live tool list produces BB-COV-MCP-TOOLS-NOT-EXPORTED, not a silent pass.

Config adapters also derive coarse capabilities from MCP server names, commands, and arguments without launching them. Common shell, fetch/browser, filesystem, database, and credential-server identities therefore remain visible even when tools/list is missing. Recognized wildcard rules for command execution, root file access, and unrestricted web fetches are mapped to derived permission scopes. These are heuristic observations and remain labeled [derived].

When a zero-argument scan has not received the live r

앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요

BackBond Agent Scan

개요

PopNx MCP의 세 기둥

할 수 있는 일

설치

설치하기 전에

할 수 있는 일

기본 점검i

제작자와 저장소 일치

계속 관리되고 있음

라이선스 있음

엔드포인트 응답

OAuth로 로그인

도구 설명에 숨겨진 지시 없음

기타 카테고리의 다른 서버와 비교i

자주 묻는 질문

대안

Spec Driven Development

Remote Desktop Commander

AI Deprecations

제작자의 README

BackBond Agent Scan

Try the browser preview

Static MCP tool manifest inspection

Vet MCP tools before attachment

Install from a trusted host first

Verify the published bytes

Network-isolated agent

Developer-laptop convenience

Install the version-pinned Agent Skill

If npm is unavailable

Zero-config first run