@saihm/mcp-server

MCPcommunity
v0.3.16io.github.SAIHM-AdminApache-2.0Updated 19d agonpmGitHub

MCP standards client for your own custodial SAIHM operator. Free start: @saihm/mcp-server-pro

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
347Downloads/wk
1GitHub stars
1Forks
19d agoLast update
Needs 1 credential before it runs
  • SAIHM_AUTH_HEADERAPI keyrequired

    Authorization header (typically 'Bearer <token>') issued by your operator.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.SAIHM-Admin
LicenseApache-2.0
Version0.3.16
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
ProvenanceAttested · unverified by Forge
Dependencies60 resolved · 1 with advisories
Tool surface8 tools · none privileged
Security scan⚠ Warnings (1)v0.3.10 · 2mo agoHow well does this scan work?
EvalsNone
IndexedJul 1, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev0.3.10 · 2mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

saihm_rememberNo description published

This tool published no description. Forge does not invent one.

saihm_recallNo description published

This tool published no description. Forge does not invent one.

saihm_forgetNo description published

This tool published no description. Forge does not invent one.

saihm_statusNo description published

This tool published no description. Forge does not invent one.

saihm_shareNo description published

This tool published no description. Forge does not invent one.

saihm_revoke_shareNo description published

This tool published no description. Forge does not invent one.

saihm_governance_proposeNo description published

This tool published no description. Forge does not invent one.

saihm_governance_voteNo description published

This tool published no description. Forge does not invent one.

0 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP standards client for your own custodial SAIHM operator. Free start: @saihm/mcp-server-pro

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.