Skills/Glama/mcp-hyperspace-memory

mcp-hyperspace-memory@4.2.0

VERIFIED· install only

Publisher claims: "Enables AI agents to store, semantically recall, update, forget, consolidate, and verify persistent memories with session isolation and hyperbolic concept navigation. It also supports knowledge-graph linking and claim verification for anti-hallucination workflows." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry GlamaPublisher yarlabs · publishing for 16 daysInstalls 0Last detonated 45 h ago
$npx skills add mcp-hyperspace-memory
WatchReport an issue

Coverage

Nothing executable in the bundle ran; the trace covers the install step only.
Tested
every file read, file written and host contacted by what ran
Not tested
use of the skill by an agent

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
CDE_API_KEYHYPERSPACE_API_KEYYAR_API_KEYConfiguration, not credentials: HYPERSPACE_ENCRYPTION_KEY, HYPERSPACE_HOST, HYPERSPACE_LOCAL_ADMIN_KEY, MEMORY_COLLECTION
Where it talks to
yar.ink (its own)
What the honeypot saw
no credential files read · no network
What we could not test
use of the skill by an agent

Connect it with a scoped credential, under the guard. It asks for CDE_API_KEY, HYPERSPACE_API_KEY, YAR_API_KEY and talks to yar.ink. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets CDE_API_KEY=yar.ink,HYPERSPACE_API_KEY=yar.ink,YAR_API_KEY=yar.ink -- <the server's command>

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-12 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 1 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessscript backend runs setup only
0.0sprocessscript backend runs setup only
0.0sprocessno install scripts to re-run

Static findings

HIGH
Credential pass-through configurationsrc/test_memory_stress.ts:153 · Credential pass-through configuration — agent relays sensitive credentialsconst niahQuery = "Where is the secret bypass token for Chimera vault stored?";Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST02
MEDIUM
File type combined with upload actionsrc/test_memory_stress.ts:366 · File type combined with upload action — agent may exfiltrate local data filesconsole.log(` Ingestion Throughput: ${benchmarkStats.ingest?.throughputOpsPerSec} ops/sec`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
File type combined with upload actionsrc/test_memory_stress.ts:140 · File type combined with upload action — agent may exfiltrate local data filesconsole.log(` Throughput: ${throughput} ops/sec | p50: ${p50}ms | p95: ${p95}ms`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07

Cost to the agent

Instructions loaded
≈42 tok
1 file · 10 in bundle

Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.

Known vulnerabilities

Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.