Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

StremAI

NPM · AIAGENTSBAY-MCP · 2 COMPONENTS · SCANNED SEP 21

StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio.

0 this week 84 Trust /100
Trust breakdown (7 categories)

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
  • 52 of 131 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 182 tokens (~45/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
  • Stability observed for 29 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Install

How do I install the StremAI MCP server?

StremAI runs locally as an npm package, launched with npx -y aiagentsbay-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · aiagentsbay-mcp

# add to Claude Code
claude mcp add thomasjumper-stremai -- npx -y aiagentsbay-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "thomasjumper-stremai": {
      "command": "npx",
      "args": [
        "-y",
        "aiagentsbay-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "thomasjumper-stremai": {
      "command": "npx",
      "args": [
        "-y",
        "aiagentsbay-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add thomasjumper-stremai -- npx -y aiagentsbay-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "thomasjumper-stremai": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "aiagentsbay-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add thomasjumper-stremai --command npx --arg -y --arg aiagentsbay-mcp
# ~/.hermes/config.yaml
mcp_servers:
  thomasjumper-stremai:
    command: "npx"
    args: ["-y", "aiagentsbay-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "thomasjumper-stremai": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "aiagentsbay-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add thomasjumper-stremai -t stdio -c npx -a -y aiagentsbay-mcp
// mcp.json
{
  "mcpServers": {
    "thomasjumper-stremai": {
      "command": "npx",
      "args": [
        "-y",
        "aiagentsbay-mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +1
    • Security disclosure: unverified → fail functional
  • 19 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail functional
  • 14 Sept 26 0
    • Security disclosure: fail → unverified functional
  • 13 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.

  • 12 Sept 26 0
    • Security disclosure: unverified → fail functional
Diagnostics

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 21 Sept 2026 · Analysed npm/aiagentsbay-mcp@1.2.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 131 packages
Packages resolved 131
Deprecated 1
Stale 51
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~182 tokens

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 →

Tool Tokens
agentbay_capabilities ~31

Introspect this AgentBay MCP connection: surface, available tools, and how to restore local memory.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

agentbay_local_unavailable ~100

Diagnostic: local AgentBay memory is OFF in this session because no SQLite driver loaded (better-sqlite3 native binary missing and Node < 22.5 has no built-in node:sqlite). The memory tools are hidden until this is fixed. Call this tool for the exact reason and the fixes: upgrade Node to >= 22.5, rebuild better-sqlite3, or set AGENTBAY_API_KEY for cloud mode.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

agentbay_signup ~34

Start the signup flow. Cloud mode needs no local SQLite, so signing up also fixes the unavailable local memory on this machine.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

agentbay_whoami ~17

Show your current authentication status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the StremAI MCP server?

StremAI is an MCP server listed in the public MCP registry as io.github.thomasjumper/stremai. StremAI MCP: shared memory for AI coding agents. Connected agents can recall. OAuth + local stdio. This page covers its npm package (aiagentsbay-mcp).

Is the StremAI MCP server safe to use?

StremAI scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 StremAI MCP server expose?

StremAI exposes 4 tools: agentbay_local_unavailable, agentbay_signup, agentbay_capabilities, agentbay_whoami. Their descriptions and schemas cost roughly 182 tokens of context every time the server is loaded.

Is the StremAI MCP server still maintained?

StremAI is still listed as active in the MCP registry. We last reached this channel on 21 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 StremAI MCP server under?

StremAI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.