# dev.aic0rt3x.memory/mcp

Persistent cloud memory for AI agents. Store and search key-value memories across sessions.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.0
- **Author:** dev.aic0rt3x.memory
- **License:** Unknown
- **Endpoints:** streamable-http https://memory.aic0rt3x.dev/mcp
- **Source:** https://memory.aic0rt3x.dev/mcp
- **Endpoint health:** reachable (last checked 2026-10-03T06:28:42.194Z, 6 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 36 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-08-29T21:15:07.882Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

15 declared. Observed from a live `tools/list` probe.
- `get_memory` — Retrieve a stored value by namespace and key.
- `put_memory` — Store a value with optional tags, priority, and storage duration in months (default 1). value_json must be ≤ 1 MB. On overwrite, the existing expiry is scaled b
- `delete_memory` — Delete a stored value.
- `list_keys` — List keys in a namespace with metadata (created_at, updated_at, updated_count, ttl, priority, last_modified_key_id). Returns up to 1000 keys sorted by recency. 
- `top_memories` — Return the top N highest-priority non-expired keys in a namespace, ordered by priority descending. Useful for loading the most important context when space is l
- `list_namespaces` — List all namespaces for this account.
- `search_by_tag` — Find (namespace, key) pairs with a given tag. Returns up to 1000 results.
- `get_account` — Get account status, credit balance, and available credits.
- `list_api_keys` — List all API keys on this account.
- `create_api_key` — Create a new live API key. Only available for active accounts. The key is shown once — store it immediately.
- `revoke_api_key` — Revoke an API key by ID. The key stops working immediately.
- `list_payments` — List payment history for this account.
- `settle_balance` — Charges the saved payment method to settle your outstanding balance. Requires explicit user approval before running. For trial accounts, returns the activation 
- `submit_exit_feedback` — Submit feedback when a trial ends without activation. Free to call — no credits charged. Only the first submission per account is recorded; duplicates are silen
- `submit_feature_request` — Submit a feature request or product feedback. Charged at storage rate: ceil_kb(description_length) × 100 credits per KB. Available to trial and active accounts 

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp\": {\n      \"type\": \"http\",\n      \"url\": \"https://memory.aic0rt3x.dev/mcp\"\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: deletes data; runs on someone else's infrastructure.
- Floor 32, ceiling 56 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/dev.aic0rt3x.memory%2Fmcp
- Install plan: https://forgeregistry.com/api/v1/packages/dev.aic0rt3x.memory%2Fmcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/dev.aic0rt3x.memory%2Fmcp
- HTML page: https://forgeregistry.com/registry/dev.aic0rt3x.memory%2Fmcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.