Skip to main content
Glama
Riku-KANO

mem9-guard-mcp

by Riku-KANO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MEM9_API_KEYNomem9 API key. Falls back to a local JSON store when unset.
MEM9_API_URLNoDefaults to https://api.mem9.ai. Override for self-hosted mem9.
MEM9_AGENT_IDNoX-Mnemo-Agent-Id header (optional).
MEM9_GUARD_POLICYNoPath to a policy YAML. Defaults to Policy.strict().
MEM9_GUARD_LOCAL_PATHNoPath of the fallback JSON store (default mem9_local_store.json).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_writeA

Write a value to guarded mem9 memory.

The value is screened by agent-memory-guard before persisting; the result may be
allow / redact / quarantine / block. Declare provenance honestly via source_class
(user_input | external_tool | agent_authored | system) — it drives self-poisoning
detection. Optionally classify with memory_class (e.g. "ephemeral").
memory_readB

Read a value from guarded mem9 memory.

Reads run integrity verification and outbound screening; sensitive content may come back redacted, and tampered or policy-violating entries are blocked.

memory_deleteC

Delete a key from guarded mem9 memory. Protected keys cannot be deleted.

memory_listA

List all keys currently stored in guarded mem9 memory.

security_eventsA

Return recent security events emitted by the guard (newest first).

Useful for auditing why a write was blocked, redacted, or quarantined.

quarantine_listA

List writes currently held in quarantine (detected anomalies pending review).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clear, distinct purpose: core memory operations (delete, list, read, write) plus quarantine and security events. No overlap ambiguity.

Naming Consistency4/5

Main tools follow a consistent 'memory_' prefix pattern. 'quarantine_list' and 'security_events' deviate slightly but are still descriptive and follow a sensible scheme.

Tool Count5/5

Six tools is an appropriate number for a guarded memory system, covering essential operations without being overwhelming.

Completeness4/5

Covers CRUD (memory_write as create/update, memory_read, memory_delete, memory_list) plus quarantine and security auditing. Missing an explicit update operation, but write can serve that role.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources