memory-search-mcp@1.0.9
VERIFIED· startup onlyPublisher claims: "MCP server for memory search. Features record memory, search memory, add knowledge. From MEOK AI Labs." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
MEOK_API_KEYConfiguration, not credentials: MEOK_ATTEST_KEY, MEOK_PAYG_KEY, MEOK_VERIFY_TIMEOUT, MEOK_VERIFY_URL- Where it talks to
- no vendor host named in the codeAlso proofof.ai, stripe.com, meok.ai, smithery.ai, mcpize.com, councilof.ai — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names proofof.ai, stripe.com, meok.ai, smithery.ai, mcpize.com, councilof.ai as well as its own vendor. The guard injects MEOK_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
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 (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 92/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 · 20 s · 2 scenarios · 0 deviationsStatic findings
npx @smithery/cli mcp publish "https://github.com/${{ github.repository }}" -n nicholastempleman/${{ github.event.repository.name }} --jsonFix: Pin versions and sources; vendor anything fetched at install time.mcp_server.run(transport="streamable-http")Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for memory-search-mcp@1.0.9 as of 3d ago. This is the package itself, not its dependencies.