Bragproof

← Reports

@saihm/mcp-server-pro

Starts with no setup0.14.4npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 0 of 1 tool tried
Contacts while installing and starting: nothing

9tools listed
0hosts contacted
0files written
0.2 sto start
103dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @saihm/mcp-server-pro@0.14.4

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

1 tool that takes no input and looks read-only was called once with nothing. 0 returned a result.

saihm_statusNo usable answer tool reported an error: No SAIHM memory yet on this device. Checked SAIHM_IDENTITY, SAIHM_MASTER_SECRET_FILE and SAIHM_MASTER_SECRET_HEX (none set) and /tmp/.sa

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

saihm_remember content, cellId, warmStart, coversThrough, token
Store information in SAIHM persistent memory. Encryption happens in this process and the key never leaves it, so the server holds ciphertext it cannot read. Use this when a fact, decision, or piece of context should outlive the current session. Pass an existing cellId to update that cell instead of adding a new one; when the endpoint reports that the update left shares of the cell on the previous version, they are re-issued for the new version and the result counts them, and a share that was not re-issued needs saihm_share again. Returns the cell id that saihm_forget takes. With warmStart "put", it instead stores an encrypted warm-start snapshot of the payload file named by token.
saihm_recall query, sharerPinnedAgentIdHashHex, sharerRecord, cellId, shareEntries, listOnly, sharesOnly, after, warmStart, token
Retrieve your memories from SAIHM and decrypt them in this process; the server never sees plaintext. Use this at the start of a session, or whenever past context is needed. Pass query to filter by keyword, or leave it out to load everything. Pass cellId alone to read one of your own cells. To read a single cell another agent shared with you, pass their agent ID as sharerPinnedAgentIdHashHex together with the cellId, taking that ID from your user, not from a shared pointer; that path is read-only. Pass listOnly to list your cells' versions without their content. Pass sharesOnly to list every pointer shared with you, a page at a time, where the endpoint offers it. With warmStart "latest", it instead restores the newest encrypted warm-start snapshot into the payload file named by token; "list" lists them.
saihm_forget id, warmStart, snapshotId, token
Cryptographically erase one memory by its cell id (GDPR Art. 17). Destroying the wrapped key leaves the content unreadable to everyone, the operator included. Irreversible: use it when erasure is the intent, not to tidy a working set. With warmStart "delete", it instead destroys one encrypted warm-start snapshot, its key first.
saihm_status
Show the current SAIHM session: the agent identity, which this client derives locally, plus the tier, custody mode, shard and sharing counts, and bfsi score the server reports. No plaintext appears, because the server holds none. Use it to check which identity is active and what is stored and shared.
saihm_share cellId, recipientRecordFile, recipientRecord, recipientPinnedAgentIdHashHex, scope, expiryEpoch
Grant one other agent access to a single memory cell, named by cellId. Identify the recipient by the identity record file their identity-record command wrote: pass its path, in full, as recipientRecordFile (a relative path is read from the server's working directory), and the server reads the record and agent ID from it (no need to open the file). Or pass their recipientRecord with their recipientPinnedAgentIdHashHex, pinned out-of-band. With the file, pass recipientPinnedAgentIdHashHex too when the user has the agent ID from their colleague another way: it must match the agent ID in the file. Set scope to 'read', 'write' or 'readwrite'. Only that one cell is exposed, and sharing re-wraps its key rather than copying the memory.
4 more tools
saihm_revoke_share cellId, recipientHex
Withdraw a grant made with saihm_share, naming the same cellId and the recipient's recipientHex. It applies to future reads and cannot retract what the recipient has already read. Use it to end access; the memory itself remains, and saihm_forget is what erases.
saihm_governance_propose scope, paramKey, proposedValue
Open a protocol governance proposal: set scope to 'emission_param' or 'protocol_upgrade', and for 'emission_param' also pass paramKey and proposedValue. Protocol governance is not enabled for this client yet — the tool is present so the surface stays stable, and calling it returns a 'governance unavailable' error rather than opening a vote.
saihm_governance_vote proposalId, approve
Cast a vote on an open protocol governance proposal by its proposalId, with approve set to true to approve or false to reject. Protocol governance is not enabled for this client yet — the tool is present so the surface stays stable, and calling it returns a 'governance unavailable' error rather than recording a vote.
saihm_join newIdentity
Activate free SAIHM persistent memory for this agent. Call this when the user asks to join, sign up for, or set up SAIHM. Where no identity is configured, a join creates a NEW, EMPTY memory, so the first call answers with a question instead: whether they already have a SAIHM identity (from another machine or an earlier session). Put it to them once; if they do, do not join: they bring it with export-identity instead. In a hosted or cloud session that starts fresh each time, or in a CI job, do not join there either: they join on their own computer, then bring that identity in the same way. Once they confirm they want a new one here, call again with newIdentity: true. It self-generates a sovereign memory key on this device and starts a one-time human approval — the tool returns a URL and short code for the user to open and enter. After the user approves, the join finishes by itself and the memory tools work; there is no need to call saihm_join again. No payment.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseApache-2.0
Needsnode >=20.19
Sourcegithub.com/SAIHM-Admin/saihm-mcp-server-pro
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-Lr9d24UnECaA2rkOmpHw5zff5OaRWnpdWN0qS1TuYvEqkAM1BjzI2Yf7LSgXXlwSSFpkXQG/eclXq+byePxENg==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@saihm/mcp-server-pro.svg)](https://bragproof.smaverk.com/r/%40saihm/mcp-server-pro)

New version out? Ask for a fresh report.