{"report":"{\"v\":1,\"package\":\"@nodatachat/mcp\",\"version\":\"1.6.57\",\"ranAt\":\"2026-11-16T11:33:13.407Z\",\"install\":{\"ok\":true,\"integrity\":\"sha512-9Qu0z/a/3kWYMFJ4wOKhgd3hw5bCqp7v/UY6yqMN2tnpKVMbdHLX2FjYQ+neltXeyM7St5WyfViCsSPCmReCtw==\",\"deps\":105,\"scripts\":[],\"bins\":[\"nodata-mcp\"],\"license\":\"FSL-1.1-ALv2\",\"engines\":\"node >=20.19.0\",\"bin\":\"nodata-mcp\"},\"start\":{\"ok\":true,\"ms\":398,\"serverName\":\"NoData (setup)\",\"serverVersion\":\"1.6.57\",\"protocol\":\"2025-06-18\",\"stderr\":\"nodata-mcp: no credential given — running in setup mode (data tools disabled).\\nCall nodata_connect (opens signup, enrolls this device), or pass --api-key / --grant-token. See --help.\\n\"},\"tools\":[{\"name\":\"nodata_terms\",\"description\":\"Show NoData's terms of use (current version) and, on the user's explicit approval, accept them. Data tools stay off until the current version is accepted. ASKS FIRST: without confirm:true it only shows the terms summary and link — show it to the user and call again with confirm:true only if they say they accept. Records operational identity only (organisation, agent, version, time, hash), never content. LANGUAGE: if the user has not chosen one, ask them — עברית or English — and pass it as `language`; it is kept for every later session and every agent on this machine.\",\"params\":[\"confirm\",\"language\"]},{\"name\":\"nodata_node\",\"description\":\"Register THIS MACHINE as a Capsule node of the organisation — so \\\"this machine is guarded\\\" is something the organisation can verify, not only the user. One node per machine; every agent here (Claude Code, Cursor …) is a workload on it; billing stays per decision, a node is not a billing unit. Uses the Capsule agent's own enrolment and signed heartbeat. The heartbeat reports only: a machine id (a salted hash, never the host name), the agents' names, whether the read gate is on, and the accepted terms version — never content. ASKS FIRST: without confirm:true it shows the status, or what registering would send. Call with confirm:true only after the user approves.\",\"params\":[\"confirm\"]},{\"name\":\"nodata_get_started\",\"description\":\"Call this FIRST (no arguments). NoData in one line: what you can achieve — an agent that cannot leak, a look at what is already exposed, a secret we cannot read — with the single next step for each, and how to recover if the tools or MCP seem stuck. If the user asks what NoData can do, how to start, what is missing, which version runs, or why the tools are missing, call this and relay it — it re-checks this machine each time. For ANY question about NoData pass it as `question`: the answer comes from NoData's answer bank and is recorded — answer only from it.\",\"params\":[\"question\"]},{\"name\":\"nodata_plan\",\"description\":\"RECOMMEND a policy after a scan, per file, and apply it only once the user approves. For every file with findings it proposes a tier (Restricted / Confidential / Internal) and an action: \\\"both\\\" (clean copy to work on + lock the original), \\\"protect\\\" (lock), \\\"redact\\\" (clean copy) or \\\"keep\\\"; credentials also get a rotate-at-source step. ASKS FIRST: without confirm:true it only shows the plan. The user may change any action — pass them as `actions` {\\\"relative/path\\\": \\\"protect\\\"|\\\"redact\\\"|\\\"both\\\"|\\\"keep\\\"} — then call again with the same path, the same actions and confirm:true. Proposing is not accepting: never confirm on the user's behalf. Content-free: paths and counts only. SCOPE: this decides the files on this computer only; what may cross to a partner or an AI agent is nodata_choose, a separate decision this plan does not set. An approved plan runs in ROUNDS of up to 50 files: when the result says CONTINUE, call again with exactly the same path, actions and confirm:true (the user already approved; do not ask again) until it says ALL DONE. Finished files are never redone.\",\"params\":[\"path\",\"actions\",\"remove_originals\",\"confirm\"]},{\"name\":\"nodata_scan_feedback\",\"description\":\"REPORT a wrong scan result so NoData's detectors improve: files the scan flagged that are NOT actually sensitive (`not_sensitive`: relative paths or patterns from the scan), and kinds of data it MISSED (`missed`: {\\\"phone\\\": 2}). Send only what the user said — never guess on their behalf. Content-free: only kind labels and counts leave this machine (e.g. \\\"not_sensitive:ID×2 · missed:phone×1\\\"), never a value, a file name or free text. It does not change any file or any plan; to leave a file alone use nodata_plan with \\\"keep\\\".\",\"params\":[\"path\",\"not_sensitive\",\"missed\"]},{\"name\":\"nodata_scan_folder\",\"description\":\"SEE what's sensitive. Scans a LOCAL folder for hardcoded secrets and unencrypted PII (checksum-validated Israeli ID, Luhn credit card, IBAN, phones), entirely on this machine. It sorts every file by what it is and reads it: Office (2007+ and 97-2003), OpenDocument, RTF, PDF, Outlook mail with its attachments, files inside ZIP archives, and pictures by OCR on this computer (Tesseract when installed, otherwise a built-in reader fetched once from npm — nothing to install by hand). Every file NOT read is counted and named with why (COVERAGE) — relay that to the user; never say everything was checked while a row says NOT. Returns the WHOLE result — counts by type, by folder and by file — and writes a full content-free HTML report (every finding) to ~/.nodata/reports, with a link to open it. A folder of more than 200 files is MAPPED first (parts, file counts, types) and scanned part by part in rounds: on CONTINUE call again with the same path, without asking, until ALL PARTS DONE; the last round gives the whole result. Ends with the IRON CHAIN block: the scan's QUALITY, a VERDICT computed from it (READY / NOT READY / NOT PROVEN / UNKNOWN) and the one mandatory NEXT step: relay it as it is. When the verdict is NOT READY the same answer carries the recommended policy and its PATH TO READY (STEP 5): show it and ask for approval. Do not list, count or glob the folder yourself before it: its first answer is the map. GUIDED: when the client can show dialogs, call it with NO path when the user did not name a folder: it asks the person which folder, and after a NOT READY verdict it asks the person what to do (a clean copy preselected, explained in one sentence) and runs that choice itself. Relay its answer; do not ask the same questions yourself. Every scan leaves a receipt (counts only). Call this FIRST when the user asks to scan/audit/check a folder, and whenever they ask whether a folder or file is safe, sensitive, or may be given to an AI agent, an API or a partner: the verdict is the answer, not your own reading of the folder.\",\"params\":[\"path\",\"max_files\",\"include_tool_dirs\",\"git_history\",\"restart\"]},{\"name\":\"nodata_clean_folder\",\"description\":\"DELIVER a clean folder: builds \\\"<folder> (clean)\\\" NEXT to the user's folder and changes nothing in theirs. A file with nothing sensitive is copied as it is; a file with findings goes in as its verified clean copy (values replaced with tokens, a workbook stays a workbook); a scanned PDF goes in as a PDF with its values and the user's terms painted black on the page images (checked by reading it again with OCR); a file NoData cannot vouch for (not read, PDF readers disagreed, a picture read by OCR, holds one of the user's terms) is held back and named with why. The clean folder is then scanned again by the same scan and anything still found is taken out. Call it right after nodata_scan_folder when the verdict is NOT READY or NOT PROVEN, without asking: it is the first thing the user gets. Lead your reply with the folder, then ask the one question its answer gives. Calling it again rebuilds the folder (after new terms or the amounts dial).\",\"params\":[\"path\"]},{\"name\":\"nodata_protect\",\"description\":\"LOCK files: seal each one as <file>.ndc (AES-256-GCM, sealed to this device's key, which never leaves this machine). Every seal belongs to someone: it is registered at NoData under this computer's approved identity, NoData keeps only a key half it cannot open, and every opening is receipted and revocable. Refuses when this computer is not connected (nodata_connect): there is no anonymous local seal. Given a folder, seals only the files the scan finds exposure in; given a file, seals that file. ASKS FIRST: without confirm:true it only lists what would be sealed and changes nothing — show that list to the user and call again with confirm:true only after they approve. Writes a local receipt (hashes, seal ids) under <folder>/.nodata/receipts. remove:true also deletes the plaintext originals. For a file ONLY the person should hold (Holder Lock: their own code opens it; the organisation recovers it only through a request, an approver and their window to refuse), tell them to run `npx -y @nodatachat/mcp@latest hold <file>` in their own terminal: the code is typed hidden there. Never ask for that code in the chat.\",\"params\":[\"path\",\"confirm\",\"remove\"]},{\"name\":\"nodata_open\",\"description\":\"RELEASE a sealed file: open <file>.ndc back to its original next to it (never overwrites), and check its hash matches what was sealed. NoData hands the key half back only to the device the seal belongs to, or to another computer of the same person it was sealed for (each opens its own copy with its own key), in the same organisation, after a signed proof, and never after a revoke. A PERSON approves every opening: the call asks NoData, a page opens in the browser, and the file opens only after someone signed in to the organisation clicks Approve (the agent cannot approve; one approval opens once, within 5 minutes). If the call returns WAITING FOR A PERSON, tell the user to approve, then call again. Refuses when this computer is not connected. ASKS FIRST: without confirm:true it only says what would be opened. Writes a local receipt.\",\"params\":[\"path\",\"confirm\"]},{\"name\":\"nodata_redact\",\"description\":\"WORK on the rest: make a clean copy of a file with every sensitive value replaced by a typed token ([CARD], [ID], [IBAN], [PHONE], [EMAIL]); in CSV/TSV and Excel a column whose header names personal data (name, address, account number…) is replaced whole with one stable token per value ([NAME-1], [NAME-2] … — the same person keeps the same token), so rows and columns still line up and still group by person. Columns of amounts stay whole. Same detectors as the scan. The copy keeps the file's type: in Excel (.xlsx) the same column rule applies per sheet and the copy stays a workbook with its formatting; a Word document (.docx) or a deck (.pptx) stays one, with its tables, headings and slides, and its pictures blanked. The original is untouched; the copy is written next to it as <name>.clean.<ext> (a PDF with a text layer, or a document with charts or embedded files → .clean.txt, and the answer says why). A SCANNED PDF (no text layer) stays a PDF: every page is read by OCR on this computer, each value the detectors find and each of the user's terms (nodata_scan_terms) is painted black on the page image, and the copy is a new PDF of page images only, checked by reading it again with OCR. Never black out a PDF with a script of your own: this is the copy that carries the proof. The answer holds counts, kinds, the path and the proof, never the document's text: work from the clean copy at that path. ON SCREEN: someone may be sitting next to the user. Answer with totals, counts and summaries by default; ask before printing rows or individual values, even from the clean copy (a value the detectors did not recognise is still in it).\",\"params\":[\"path\",\"return_text\",\"near_miss\"]},{\"name\":\"nodata_run\",\"description\":\"Run a command on this machine (tests, a migration, a deploy script) WITH the project's secrets from the NoData vault as environment variables — without you seeing them. The secrets are pulled into memory only (no .env is written); you get back the exit code and the output with every secret value blanked. EVERY command needs the user's approval, as written. When a key's policy says a person approves each use, or the client cannot ask the user itself, NoData asks the person: a page opens in their browser (or give them the link this returns), they sign in, check the command and the code, and approve it there — you cannot approve it, and there is no code for you to send back. Then call nodata_run again with the same command, folder and project; it resumes the same request. Never embed a secret value in the command, never try to print or encode one, and never confirm on the user's behalf. Uses this computer's NoData connection (`npx -y @nodatachat/mcp connect`, approved once in the browser) — no separate token; a project-limited CLI token saved with `secrets-login` is used first if present. Never ask the user for a key in the chat.\",\"params\":[\"command\",\"cwd\",\"project\",\"timeout_seconds\",\"approval\",\"partner_of\",\"cost_usd\"]},{\"name\":\"nodata_rules\",\"description\":\"The RULES BOARD for files, folders and web sites on this computer: what an AI agent may do with each one — allowed, ask the user, clean copy only, or not allowed — optionally only for certain agents (claude-code, cursor …) or sub-agents, at certain times, or for certain actions (read, search, run, write; on a site: browse, interact) or file types. A web site rule (site:'example.com', its subdomains too; site:'*' = every site) holds an agent that drives a browser over MCP or fetches a page: browse = open or read a page, interact = click, type, submit. e.g. {action:'add', site:'bank.example.com', effect:'ask', actions:'interact'} = the user approves every click there (the human checkpoint: a CAPTCHA, a login, a payment is the user's to pass, never the agent's). An allowed site is also a TRUSTED DESTINATION: after the session read a web page, an API answer or a partner's command, a network step waits for a person, except a curl / wget whose every address is a named allowed site (https, no proxy, no -k; site:'*' does not count). e.g. {action:'add', site:'api.elevenlabs.io', effect:'allow', actions:'run'} trusts only commands to it. Several rules per file or folder; the most specific path decides, and among its rules the first whose conditions hold. Enforced by NoData's read gate on every read, search, command and write, and on every page an agent opens or acts on through a browser tool or WebFetch, whatever the agent. Plain fields, no condition syntax needed: folder (or path), effect, agent (\\\"cursor\\\", [\\\"cursor\\\",\\\"windsurf\\\"] or \\\"all but cursor\\\"), sub_agent (\\\"main\\\" = the main conversation, \\\"all but main\\\" = only sub-agents), actions (\\\"write\\\", [\\\"read\\\",\\\"search\\\"] or \\\"all but read\\\"), hours ([18,8] or \\\"18-8\\\", this computer's clock, wraps overnight), days ([0,1,2,3,4] or \\\"sun-thu\\\"). e.g. {action:'add', folder:'~/Finance', effect:'deny', agent:'cursor', actions:'write', hours:'18-8'} = cursor may not write in Finance at night. action 'list' shows every rule. 'add' adds one (tightening asks for confirm:true; ALLOW needs the user's own approval). 'remove' removes rule n (removing a restriction needs the user's approval). action 'level' with level:'strict'|'routine'|'production' = APPROVAL LEVELS, how often an agent stops for the user: strict = every stop; routine = also lets an install of what the project already pins pass after outside content, and lets nodata_run run a command to trusted sites without a dialog when its keys allow an agent; production = also an answer from a trusted site does not mark the session (closed on an organisation's computers until an admin opens it). Writes to what runs the gate, NoData's keys, credentials in the chat and an agent approving itself stop at every level. Raising a level needs the user's approval; lowering it does not. Every step a level lets through is counted. A rule may name a kind of step: {action:'add', step:'install', effect:'deny'} = no installs at all; {action:'add', step:'push', effect:'ask'} = every git push asks\",\"params\":[\"action\",\"level\",\"step\",\"set\",\"checkpoint\",\"path\",\"folder\",\"site\",\"agent\",\"sub_agent\",\"actions\",\"hours\",\"days\",\"effect\",\"when\",\"note\",\"n\",\"confirm\",\"approval\"]},{\"name\":\"nodata_choose\",\"description\":\"CHOOSE WHAT CROSSES from a folder, per kind of detail the last nodata_scan_folder found (ID numbers, names, emails, bank details, secrets, the user's own terms, files not read): each kind crosses or is withheld. A part of the folder holding a withheld kind goes out only as a clean copy, or stays closed when very sensitive; the rest goes as the folder is. The same choice as the site's \\\"Choose what crosses\\\" panel. Without changes it shows the panel (\\\"May cross · N of M\\\"): show it to the user as it is and let THEM choose. cross / withhold change kinds (by name, as shown); all:'cross' selects all, all:'withhold' withholds all. approve:true makes it policy: this computer's owner approves it in the browser (opened for them), then it is recorded in a signed receipt and applied as rules on the rules board. You only propose: never approve for the user, and call approve only when the user asked for it. Counts and kinds only, never a value. An approved policy puts the folder on AUTOPILOT: the read gate answers by the policy instead of asking on each file (a kind it never saw still asks). autopilot:false takes the folder off it. coverage:true answers \\\"is everything covered, and is there anything new to enforce?\\\" for every project and scanned folder on this computer: new projects not scanned yet, folders without a policy, files changed since the scan, kinds the policy never saw, and the one next step for each. Use it when the user starts a new project, adds a folder or files, or asks whether they are protected.\",\"params\":[\"path\",\"cross\",\"withhold\",\"all\",\"approve\",\"approval_id\",\"autopilot\",\"coverage\"]},{\"name\":\"nodata_scan_terms\",\"description\":\"The SCAN TERMS: words, phrases or symbols that make a file sensitive in nodata_scan_folder and nodata_plan, each with a label and a tier (1 public · 2 internal · 3 confidential · 4 restricted). The organisation's terms come from NoData when this computer is connected (cached here); the user's own are kept on this computer. A file holding a term is reported with the term's label, tier and count (never the text around it) and is raised to that tier in the plan. action 'search' answers \\\"would the scan catch X?\\\": how a column named X is judged, whether X is in the built-in list, in the user's or the organisation's terms, and (with path) how many files in a folder hold it, counts only; when nothing covers it, it gives the add call. Use it when the user names something sensitive the scan did not report. action 'amounts' with on:true treats money amounts as sensitive (the scan reports them, a clean copy replaces them with [AMOUNT]); off by default, because a clean copy is for working with the numbers. Turning it on asks for confirm:true; turning it off needs the user's own approval. Use it when the amounts ARE the secret (holdings, a family office). action 'list' shows both lists. 'add' adds one of the user's terms (asks for confirm:true). 'remove' removes one of the user's terms by id (needs the user's own approval). The organisation's terms are changed only at NoData.\",\"params\":[\"action\",\"on\",\"query\",\"path\",\"match\",\"label\",\"tier\",\"id\",\"confirm\",\"approval\"]},{\"name\":\"nodata_connect\",\"description\":\"Connect this computer to the user's NoData organisation. Call with NO arguments: it opens a page in the browser where the user signs in (or creates a free account) and clicks Approve — nothing is copied; then /mcp. Other ways, only if that cannot work: step:\\\"key\\\" opens a private window for an org key (never typed into the chat); step:\\\"signup\\\" only opens the signup page. Never ask the user to paste a key into the chat.\",\"params\":[\"api_key\",\"step\"]}],\"toolsHash\":\"097ddce439a41ec7aba3dbf4b4b512cb3f7b3519e0be74374bfddf2b49b0e400\",\"wrote\":[\"/tmp/.nodata/connection.json\"],\"host\":{\"commit\":\"eaaffffaf52255d1b77dc4aacffdfaf353f0c12c\",\"run\":\"https://github.com/itsHaddad/bragproof/actions/runs/43857070216\"},\"network\":{\"names\":[\"registry.npmjs.org\"],\"conns\":[]}}","token":"eyJhbGciOiJSUzI1NiIsImtpZCI6IjM4ODI2YjE3LTZhMzAtNWY5Yi1iMTY5LThiZWI4MjAyZjcyMyIsInR5cCI6IkpXVCIsIng1dCI6InlrTmFZNHFNX3RhNGsyVGdaT0NFWUxrY1lsQSJ9.eyJhY3RvciI6Iml0c0hhZGRhZCIsImFjdG9yX2lkIjoiMTE0NzMyNjEiLCJhdWQiOiJicmFncHJvb2YtcmVwb3J0OjJhOTZhZWJmMjM5NWUzOTE0ZGIwYjQ5NjYxZWM0OTI1MWIwZWJmNmRkM2YwNDhkZTA3OGNiZGUxMTgyNDY3ODciLCJiYXNlX3JlZiI6IiIsImNoZWNrX3J1bl9pZCI6IjEzMzI2Mzk5NTQ0MiIsImV2ZW50X25hbWUiOiJzY2hlZHVsZSIsImV4cCI6MTc5NDgyOTEwMSwiaGVhZF9yZWYiOiIiLCJpYXQiOjE3OTQ4Mjg4MDEsImlzcyI6Imh0dHBzOi8vdG9rZW4uYWN0aW9ucy5naXRodWJ1c2VyY29udGVudC5jb20iLCJqb2Jfd29ya2Zsb3dfcmVmIjoiaXRzSGFkZGFkL2JyYWdwcm9vZi8uZ2l0aHViL3dvcmtmbG93cy9yZXBvcnQueW1sQHJlZnMvaGVhZHMvbWFpbiIsImpvYl93b3JrZmxvd19zaGEiOiJlYWFmZmZmYWY1MjI1NWQxYjc3ZGM0YWFjZmZkZmFmMzUzZjBjMTJjIiwianRpIjoiNTg4MThjNzMtMGMyNC00N2U0LThkMzctZmRjYjViYzVkMGVjIiwibmJmIjoxNzk0ODI4NTAxLCJyZWYiOiJyZWZzL2hlYWRzL21haW4iLCJyZWZfcHJvdGVjdGVkIjoiZmFsc2UiLCJyZWZfdHlwZSI6ImJyYW5jaCIsInJlcG9zaXRvcnkiOiJpdHNIYWRkYWQvYnJhZ3Byb29mIiwicmVwb3NpdG9yeV9pZCI6IjE0NTQ2MjExODMiLCJyZXBvc2l0b3J5X293bmVyIjoiaXRzSGFkZGFkIiwicmVwb3NpdG9yeV9vd25lcl9pZCI6IjExNDczMjYxIiwicmVwb3NpdG9yeV92aXNpYmlsaXR5IjoicHVibGljIiwicnVuX2F0dGVtcHQiOiIxIiwicnVuX2lkIjoiNDM4NTcwNzAyMTYiLCJydW5fbnVtYmVyIjoiMjQiLCJydW5uZXJfZW52aXJvbm1lbnQiOiJnaXRodWItaG9zdGVkIiwic2hhIjoiZWFhZmZmZmFmNTIyNTVkMWI3N2RjNGFhY2ZmZGZhZjM1M2YwYzEyYyIsInN1YiI6InJlcG86aXRzSGFkZGFkQDExNDczMjYxL2JyYWdwcm9vZkAxNDU0NjIxMTgzOnJlZjpyZWZzL2hlYWRzL21haW4iLCJ3b3JrZmxvdyI6InJlcG9ydCIsIndvcmtmbG93X3JlZiI6Iml0c0hhZGRhZC9icmFncHJvb2YvLmdpdGh1Yi93b3JrZmxvd3MvcmVwb3J0LnltbEByZWZzL2hlYWRzL21haW4iLCJ3b3JrZmxvd19zaGEiOiJlYWFmZmZmYWY1MjI1NWQxYjc3ZGM0YWFjZmZkZmFmMzUzZjBjMTJjIn0.KZjGv54Vvow0RcZ-o9ogNUXhJatrAI4WaL51zP0qgUv5j6acTMIxKdgnQoJcOm9o9Xn8qufuMTCFAVHI6nLzua1ERR3abDl1lak5rJM68W8qL4TpZs6J9T_zQXTDgx4Yx_lE_os9PBWmiRuxaoDHG9yg1v4m3EffUovMy8ouE4fWkmpTdkwBN_4RgwYLgcwnMG3VG2k01wfm0Jmy4otMnOZcT8Dd0NhclXpv04UoMtFxRjVnZkWqpI0N_Huv8BkI9wUrmbx8TxQoxCX5qmuvm1MuVc8UXvpFSYV5UXdhCjp44a5i_47QiOcnUDLH1FFIPM2c3HHjXp6hOjccjuFebg"}