@aispace-sh/cli

Name: @aispace-sh/cli
Author: sh.aispace

MCPattested

v0.4.1sh.aispaceMITUpdated 15d agonpm GitHub

Secure, expiring artifact storage and handoff for AI agents.

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.

Attested build

A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.

308Downloads/wk

13GitHub stars

2Forks

15d agoLast update

Needs 1 credential before it runs

AISPACE_KEYAPI keyrequired
Scoped aispace bot key (ask_...).

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

Authorsh.aispace

LicenseMIT

Version0.4.1

Sourcenpm+mcp-registry

npm@aispace-sh/cli

GitHubaispace-sh/aispace-client

SBOMCycloneDX 1.6 ↓

Trust Status

85/100Trusted

✓Listed in Forge index+10/10

✓Identity verified · attested build+20/20

—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)+5/5

—npm maintainer match+0/5

→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)

✓CVE scan · clean+30/30

✓Static analysis · clean+20/20

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusIdentity verified

PublisherUnverified

SignatureUnsigned

Domain—

Provenance✓ Sigstore-verified · 7a54e28

Dependencies✓ 0 resolved · none vulnerable

Tool surface—

Security scan✓ Cleanv0.4.1 · 11d agoHow well does this scan work?

EvalsNone

IndexedSep 13, 2026

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

Tools

No tool declarations found in the source11d ago

Forge read 2 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

Secure, expiring artifact storage and handoff for AI agents.

Keywords

mcp

Alternatives

Comparing tool surfaces…

@aispace-sh/cli

Tools

Dependency tree