Skip to content

AI Cortex Storage MCP server

dev.aic0rt3x.memory/mcpmemory.aic0rt3x.devstreamable-httpv1.0.0Scanned

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

15 tools: 2 can delete or cancel things, 1 do something that can't be undone, 4 change things and 8 only read.

Tools: 2 delete, 1 irreversible, 4 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the AI Cortex Storage MCP server can do

The AI Cortex Storage MCP server is published by memory.aic0rt3x.dev, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (2 tools: delete_memory and revoke_api_key), do things that cannot be undone, such as sending, paying or publishing (settle_balance) and create or change data (4 tools: put_memory, create_api_key, submit_exit_feedback and submit_feature_request). 8 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 1, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 2Claude Code: deny
  • delete_memoryDelete a stored value.No findings

    Why it is in this group

    • The name "delete_memory" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Delete a stored value.

    Annotations the server declares

    • destructiveHint: true
  • revoke_api_keyRevoke an API key by ID.No findings

    Why it is in this group

    • The name "revoke_api_key" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Revoke an API key by ID. The key stops working immediately.

    Annotations the server declares

    • destructiveHint: true
Can't be undone 1Claude Code: ask
  • settle_balanceCharges the saved payment method to settle your outstanding balance.No findings

    Why it is in this group

    • The description's first verb is "charge": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Charges the saved payment method to settle your outstanding balance. Requires explicit user approval before running. For trial accounts, returns the activation URL instead. Minimum charge: $5.
Changes things 4Claude Code: ask
  • create_api_keyCreate a new live API key.No findings

    Why it is in this group

    • The name "create_api_key" says "create": a word for a change.
    Description, as the server wrote it
    Create a new live API key. Only available for active accounts. The key is shown once — store it immediately.
  • put_memoryStore a value with optional tags, priority, and storage duration in months (default 1).No findings

    Why it is in this group

    • The name "put_memory" says "put": a word for a change.
    Description, as the server wrote it
    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 by the KB size ratio of old to new value.

    Annotations the server declares

    • idempotentHint: true
  • submit_exit_feedbackSubmit feedback when a trial ends without activation.No findings

    Why it is in this group

    • The name "submit_exit_feedback" says "submit": a word for a change.
    Description, as the server wrote it
    Submit feedback when a trial ends without activation. Free to call — no credits charged. Only the first submission per account is recorded; duplicates are silently ignored. Call this when the user declines to activate or the trial is exhausted.
  • submit_feature_requestSubmit a feature request or product feedback.No findings

    Why it is in this group

    • The name "submit_feature_request" says "submit": a word for a change.
    Description, as the server wrote it
    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 alike.
Only reads 8Show 8 read-only tools
  • get_accountGet account status, credit balance, and available credits.No findings

    Why it is in this group

    • The name "get_account" says "get": a word for reading.
    Description, as the server wrote it
    Get account status, credit balance, and available credits.

    Annotations the server declares

    • readOnlyHint: true
  • get_memoryRetrieve a stored value by namespace and key.No findings

    Why it is in this group

    • The name "get_memory" says "get": a word for reading.
    Description, as the server wrote it
    Retrieve a stored value by namespace and key.

    Annotations the server declares

    • readOnlyHint: true
  • list_api_keysList all API keys on this account.No findings

    Why it is in this group

    • The name "list_api_keys" says "list": a word for reading.
    Description, as the server wrote it
    List all API keys on this account.

    Annotations the server declares

    • readOnlyHint: true
  • list_keysList keys in a namespace with metadata (created_at, updated_at, updated_count, ttl, priority, last_modified_key_id).No findings

    Why it is in this group

    • The name "list_keys" says "list": a word for reading.
    Description, as the server wrote it
    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. Expired keys are automatically excluded.

    Annotations the server declares

    • readOnlyHint: true
  • list_namespacesList all namespaces for this account.No findings

    Why it is in this group

    • The name "list_namespaces" says "list": a word for reading.
    Description, as the server wrote it
    List all namespaces for this account.

    Annotations the server declares

    • readOnlyHint: true
  • list_paymentsList payment history for this account.No findings

    Why it is in this group

    • The name "list_payments" says "list": a word for reading.
    Description, as the server wrote it
    List payment history for this account.

    Annotations the server declares

    • readOnlyHint: true
  • search_by_tagFind (namespace, key) pairs with a given tag.No findings

    Why it is in this group

    • The name "search_by_tag" says "search": a word for reading.
    Description, as the server wrote it
    Find (namespace, key) pairs with a given tag. Returns up to 1000 results.

    Annotations the server declares

    • readOnlyHint: true
  • top_memoriesReturn the top N highest-priority non-expired keys in a namespace, ordered by priority descending.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    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 limited. Maximum n is 1000.

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, no OAuth metadata

Looked at Nov 20, 2026, 18:51 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
522
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: initialize answered HTTP 522.

Posture changes

  1. Nov 6, 2026
    • HTTP status of an anonymous initialize: 200 to 522
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-03-26 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 522; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 522
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 7 to 0
    • Protocol version: 2025-03-26 to none

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http memory https://memory.aic0rt3x.dev/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http memory https://memory.aic0rt3x.dev/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__memory__get_memory",
      "mcp__memory__list_keys",
      "mcp__memory__top_memories",
      "mcp__memory__list_namespaces",
      "mcp__memory__search_by_tag",
      "mcp__memory__get_account",
      "mcp__memory__list_api_keys",
      "mcp__memory__list_payments"
    ],
    "ask": [
      "mcp__memory__put_memory",
      "mcp__memory__create_api_key",
      "mcp__memory__settle_balance",
      "mcp__memory__submit_exit_feedback",
      "mcp__memory__submit_feature_request"
    ],
    "deny": [
      "mcp__memory__delete_memory",
      "mcp__memory__revoke_api_key"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as memory. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.aic0rt3x.memory/mcp/verify?hash=dc703eb444249f983cb0ff0ec91800ac2b0f8c7156baa5106dc22beed9dd411a" | jq -e '.changed == false'

Pinned hash dc703eb44424, from Nov 1, 2026, 22:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.aic0rt3x.memory/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.aic0rt3x.memory/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.aic0rt3x.memory/mcp.svg)](https://radar.anlyon.com/servers/dev.aic0rt3x.memory/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 18:11 UTC.

AI Cortex Storage MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AI Cortex Storage MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AI Cortex Storage MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: delete_memory and revoke_api_key.

Can the AI Cortex Storage MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: settle_balance.

What tools does the AI Cortex Storage MCP server have?

15 tools: 2 destructive, 1 irreversible, 4 write, 8 read. delete_memory, revoke_api_key, settle_balance, put_memory, create_api_key, submit_exit_feedback, submit_feature_request, get_memory and 7 more.

Does the AI Cortex Storage MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the AI Cortex Storage MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AI Cortex Storage MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 1, 2026.