io.github.SAIHM-Admin/saihm-mcp
NPM · @SAIHM/MCP-SERVER · SCANNED SEP 20
MCP standards client for your own custodial SAIHM operator. Free start: @saihm/mcp-server-pro
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to SAIHM-Admin/saihm-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 7 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 885 tokens (~110/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (38% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.SAIHM-Admin/saihm-mcp server?
io.github.SAIHM-Admin/saihm-mcp runs locally as an npm package, launched with npx -y @saihm/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @saihm/mcp-server
claude mcp add saihm-admin-saihm-mcp -- npx -y @saihm/mcp-server
{
"mcpServers": {
"saihm-admin-saihm-mcp": {
"command": "npx",
"args": [
"-y",
"@saihm/mcp-server"
]
}
}
} {
"servers": {
"saihm-admin-saihm-mcp": {
"command": "npx",
"args": [
"-y",
"@saihm/mcp-server"
]
}
}
} codex mcp add saihm-admin-saihm-mcp -- npx -y @saihm/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"saihm-admin-saihm-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@saihm/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add saihm-admin-saihm-mcp --command npx --arg -y --arg @saihm/mcp-server
mcp_servers:
saihm-admin-saihm-mcp:
command: "npx"
args: ["-y", "@saihm/mcp-server"] {
"McpServers": {
"saihm-admin-saihm-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@saihm/mcp-server"
]
}
}
} assistant mcp add saihm-admin-saihm-mcp -t stdio -c npx -a -y @saihm/mcp-server
{
"mcpServers": {
"saihm-admin-saihm-mcp": {
"command": "npx",
"args": [
"-y",
"@saihm/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.83 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.3.13 → 0.3.14 functional
- 11 Sept 26 −2
- Stability: pass → 0.83 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@saihm/mcp-server@0.3.14
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | SAIHM-Admin/saihm-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/SAIHM-Admin/saihm-mcp/.github/workflows/release.yml@refs/tags/v0.3.14 |
| Rekor log index | 2810140364 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f7ca579aa18ede007170bc179272918f541d607204965a35c4864eaf1fdb98c11cab42080c9039cb7ec9acd726381c380178ee56e0730ed65550630dc |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
saihm_forget Forget (GDPR erasure) ~81
Cryptographically erase one memory by its cell id (GDPR Art. 17). Destroying the key makes the content unreadable to everyone, the operator included. Irreversible: use it when erasure is the intent, not to tidy a working set.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Memory entry ID (hex cellId) to erase |
No output schema declared.
No examples provided.
saihm_governance_propose Propose (governance) ~154
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 by default. The call is forwarded to the operator endpoint you configured, so expect an error rather than an open vote unless that operator has turned governance on. Where it is enabled it returns a hex proposalId that saihm_governance_vote takes, and it starts a vote rather than changing a setting.
| Name | Type | Req | Description |
|---|---|---|---|
| paramKey | string | – | Parameter key (when scope=emission_param) |
| proposedValue | string | – | Proposed value as string |
| scope | string | yes | Governable scope |
No output schema declared.
No examples provided.
saihm_governance_vote Vote (governance) ~139
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 by default. The call is forwarded to the operator endpoint you configured, so expect an error rather than a recorded vote unless that operator has turned governance on. Where it is enabled, vote weight derives from the governance-token balance held at the proposal snapshot epoch, not the balance at the time of voting.
| Name | Type | Req | Description |
|---|---|---|---|
| approve | boolean | yes | true = approve, false = reject |
| proposalId | string | yes | Hex proposalId returned by saihm_governance_propose |
No output schema declared.
No examples provided.
saihm_recall Recall ~78
Retrieve memories from the SAIHM encrypted store; the operator decrypts and returns plaintext, and this client holds no keys. Use at the start of a session, or whenever past context is needed. Pass a keyword to filter, or leave empty to load all.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Filter by keyword (empty = all) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| memories | array | yes | – |
No examples provided.
saihm_remember Remember ~62
Store information in SAIHM persistent encrypted memory. Use this when a fact, decision, or piece of context should outlive the current session. Returns the cell id that saihm_forget takes.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | Information to remember |
| Name | Type | Req | Description |
|---|---|---|---|
| cellId | string | yes | – |
| cellNonce | string | – | – |
| epoch | string | – | – |
| feeNcoti | string | – | – |
| kekVersion | string | – | – |
| signaturePrefix | string | – | – |
| tier | string | – | – |
No examples provided.
saihm_revoke_share Revoke share ~82
Revoke a sharing contract by its contractId, withdrawing access granted with saihm_share. It applies to future reads and cannot retract what a grantee has already read. Use it to end access; the memory itself remains, and saihm_forget is what erases.
| Name | Type | Req | Description |
|---|---|---|---|
| contractId | string | yes | Sharing contract ID to revoke |
No output schema declared.
No examples provided.
saihm_share Share ~151
Grant other agents access to specific memory shards. Set type to 'temporary', 'permanent' or 'syndicate', and scope to 'read', 'write' or 'readwrite'. Grantees are hex agent-id hashes, not names, and shardIds lists exactly what is shared: nothing outside it is exposed, and sharing does not copy the memory.
| Name | Type | Req | Description |
|---|---|---|---|
| expiryEpoch | string | – | Optional expiry epoch (decimal string) |
| granteeIdHashesHex | array | yes | Hex-encoded grantee agent ID hashes |
| scope | string | yes | Access scope |
| shardIds | array | yes | Shard IDs to include in the contract |
| type | string | yes | Contract type |
No output schema declared.
No examples provided.
saihm_status Status ~80
Show the current SAIHM session: agent identity, tier, the prs and bfsi scores, storage by tier, and sharing state, as far as the operator reports them — a non-custodial operator cannot see stored-byte totals. Use it to check the agent identity, custody mode, and what the operator reports about storage and sharing.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| activeShardCount | number | – | – |
| activeSharingContracts | number | – | – |
| agentIdHash | string | yes | – |
| bfsiScore | number | – | – |
| custody | string | – | – |
| feeDiscountPct | number | – | – |
| phi | number | – | – |
| prsLevel | string | – | – |
| prsScore | string | – | – |
| snapshotEpoch | string | – | – |
No examples provided.
What is the io.github.SAIHM-Admin/saihm-mcp server?
io.github.SAIHM-Admin/saihm-mcp is listed in the public MCP registry as io.github.SAIHM-Admin/saihm-mcp. MCP standards client for your own custodial SAIHM operator. Free start: @saihm/mcp-server-pro. This page covers its npm package (@saihm/mcp-server).
Is the io.github.SAIHM-Admin/saihm-mcp server safe to use?
io.github.SAIHM-Admin/saihm-mcp scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.SAIHM-Admin/saihm-mcp server expose?
io.github.SAIHM-Admin/saihm-mcp exposes 8 tools: saihm_remember, saihm_recall, saihm_forget, saihm_status, saihm_share, and 3 more. Their descriptions and schemas cost roughly 827 tokens of context every time the server is loaded.
Is the io.github.SAIHM-Admin/saihm-mcp server still maintained?
io.github.SAIHM-Admin/saihm-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.SAIHM-Admin/saihm-mcp server under?
io.github.SAIHM-Admin/saihm-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.