BLACKPROOF Local MCP server
io.github.l0gfr/blackproof·v0.1.0·26 starsLocal read-only cyber evidence integrity checks and aggregate comparison (alpha).
26 stars
Reviews
Write oneNobody has reviewed BLACKPROOF Local MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
BLACKPROOF Local MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How BLACKPROOF Local MCP compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 85/100
- higher than 70% of 48,243 servers
- GitHub stars
- 26
- more than 91% of 28,706 servers
Install BLACKPROOF Local MCP in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the BLACKPROOF Local MCP repository's README, as published. We do not edit it. Read it on GitHub
BLACKPROOF
BLACKPROOF is a free, open-source, local-first cyber evidence app under AGPL-3.0-only. Create, import, encrypt, export and verify dossiers directly in your browser. No account, activation key or application server is required. Use it to prepare cyber reviews, internal audits and supplier questionnaires. Bring your own review checklist, document answers, evidence references and reservations, then track the remaining preparation work. Source documents and audit conclusions still require human assessment; this is not a system scanner or an automated certification service.
Core flow:
questionnaire ou grille d'audit → réponses et références → preuves attendues → points à corriger → dossier interne → export relu facultatif.
Project structure
- apps/web — public website and local-first app
- apps/web/src/content/analyses (sourced Markdown analyses and publication drafts)
- packages/core — ProofGraph, ProofDebt, ProofPack logic
- packages/verifier — standalone Delivery verifier CLI/SDK
- packages/mcp — local, read-only MCP server for minimized verification and comparison
- tests/e2e — Chromium tests for the local-first editor and verification flows
- scripts — schema generation, security checks and deployment tooling
- docs — project context and technical documentation
Development
Requirements: Node.js 22.23.2 (see .nvmrc) and pnpm 10.34.5.
pnpm install --frozen-lockfile
pnpm devThe authoritative local gate is:
pnpm verify:allpnpm verify:all runs schema drift checks, TypeScript/Astro/Svelte validation, unit tests, the static build, CSP generation, local-only artifact checks, the dependency and repository security audits, and the Chromium end-to-end tests.
Local-first boundary
Questionnaires, ProofPacks and Delivery snapshots are processed on the user's device; saved dossiers are encrypted in browser IndexedDB. No server upload is implemented or permitted for import, creation, editing, backup or verification. Downloading an export saves a local file; users transmit it separately, outside BLACKPROOF. See docs/LOCALFIRSTSTORAGE.md and docs/SECURITY_MODEL.md before changing a storage, export or destructive operation.
Local MCP for enterprise agents
Use the local MCP server to check a selected ProofPack before transmission, compare two review snapshots through aggregate changes, and obtain public preparation checklists for cyber reviews, internal audits and questionnaires. It does not expose answers, evidence references or files to the agent. It runs over stdio on the user's device, not on the public website.
See installation, tools, fictional walkthrough and security limits. Private mode requires an end-to-end local client/model. A local transport alone cannot stop a host from forwarding results to a remote model.
Editorial analyses
The /analyses section is generated from a validated Astro content collection. Drafts are excluded from public routes, RSS and the sitemap. The complete authoring and verification workflow is documented in docs/EDITORIAL_ANALYSES.md.
Licence and contributions
The original software, documentation, schemas and standalone verifier are licensed under GNU AGPL version 3 only. See LICENSE and NOTICE. Third-party dependencies retain their own licences in THIRDPARTYNOTICES.md. Contributions are welcome: see CONTRIBUTING.md. Project names and logos are covered separately by TRADEMARKS.md.
Source: https://github.com/l0gfr/BLACKPROOF-AGPL
Self-hosting
pnpm build produces the static site in apps/web/dist/. Serve it over HTTPS (or localhost for development), with the CSP and security headers described in docs/DEPLOY_APACHE.md. Publish the corresponding source of your version and keep the licence/source link visible.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
BLACKPROOF Local MCP: common questions
- Is BLACKPROOF Local MCP server safe?
- Yes, by our scan: it is graded A (85/100). Read the BLACKPROOF Local MCP safety report
- Does BLACKPROOF Local MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is BLACKPROOF Local MCP maintained?
- The last commit was 37 days ago (2026-09-29). The latest release is v0.1.0.
- How does BLACKPROOF Local MCP compare with other MCP servers?
- safety score 85/100 (higher than 70% of 48,243 servers); github stars 26 (more than 91% of 28,706 servers). Full comparison.