AI Cortex Storage
REMOTE · MEMORY.AIC0RT3X.DEV · SCANNED SEP 26
Persistent cloud memory for AI agents. Store and search key-value memories across sessions.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (delete_memory) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 857 tokens (~57/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety92
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 2 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "settle_balance" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
How do I install the AI Cortex Storage MCP server?
AI Cortex Storage is a hosted endpoint at https://memory.aic0rt3x.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · memory.aic0rt3x.dev
claude mcp add --transport http dev-aic0rt3x-memory-mcp 'https://memory.aic0rt3x.dev/mcp'
{
"mcpServers": {
"dev-aic0rt3x-memory-mcp": {
"url": "https://memory.aic0rt3x.dev/mcp"
}
}
} {
"servers": {
"dev-aic0rt3x-memory-mcp": {
"type": "http",
"url": "https://memory.aic0rt3x.dev/mcp"
}
}
} [mcp_servers.dev-aic0rt3x-memory-mcp] url = "https://memory.aic0rt3x.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-aic0rt3x-memory-mcp": {
"type": "remote",
"url": "https://memory.aic0rt3x.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-aic0rt3x-memory-mcp --url 'https://memory.aic0rt3x.dev/mcp' --transport streamable-http
mcp_servers:
dev-aic0rt3x-memory-mcp:
url: "https://memory.aic0rt3x.dev/mcp" {
"McpServers": {
"dev-aic0rt3x-memory-mcp": {
"Transport": "http",
"Url": "https://memory.aic0rt3x.dev/mcp"
}
}
} assistant mcp add dev-aic0rt3x-memory-mcp -t streamable-http -u 'https://memory.aic0rt3x.dev/mcp'
{
"mcpServers": {
"dev-aic0rt3x-memory-mcp": {
"type": "http",
"url": "https://memory.aic0rt3x.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 26 Sept 2026 · Probed https://memory.aic0rt3x.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=aic0rt3x.dev | CN=YE2,O=Let's Encrypt,C=US | 5 Aug 2026 | 3 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 53b288f9a1744147596f5a9b9dd446a82e6 |
| SANs: *.aic0rt3x.dev, aic0rt3x.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of memory.aic0rt3x.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| aic0rt3x.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://memory.aic0rt3x.dev/mcp | Verified | 200 | |
| http (plaintext) | http://memory.aic0rt3x.dev/mcp | Inconclusive | 405 |
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 →
create_api_key ~51
Create a new live API key. Only available for active accounts. The key is shown once — store it immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Human-readable label (e.g. 'claude-desktop') |
No output schema declared.
No examples provided.
delete_memory ~39
Delete a stored value.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | ≤ 255 characters, no '/' |
| namespace | string | yes | ≤ 255 characters, no '/' |
No output schema declared.
No examples provided.
get_account ~19
Get account status, credit balance, and available credits.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_memory ~43
Retrieve a stored value by namespace and key.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | ≤ 255 characters, no '/' |
| namespace | string | yes | ≤ 255 characters, no '/' |
No output schema declared.
No examples provided.
list_api_keys ~17
List all API keys on this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_keys ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace | string | yes | ≤ 255 characters, no '/' |
No output schema declared.
No examples provided.
list_namespaces ~16
List all namespaces for this account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_payments ~46
List payment history for this account.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 50, max 100) |
| offset | integer | – | Pagination offset (default 0) |
No output schema declared.
No examples provided.
put_memory ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | ≤ 255 characters, no '/' |
| months | integer | – | How long to store this entry in months (default 1, minimum 1). Ignored on overwrite — existing expiry is scaled by the KB size ratio of old to new value. |
| namespace | string | yes | ≤ 255 characters, no '/' |
| priority | integer | – | Importance 1–10; higher = more important. Default 5. Used by top_memories to surface the most relevant context. |
| tags | array | – | Labels for searching and grouping. Duplicates are deduplicated automatically. |
| value_json | string | yes | JSON-encoded value |
No output schema declared.
No examples provided.
revoke_api_key ~43
Revoke an API key by ID. The key stops working immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The key ID to revoke, as returned by list_api_keys. |
No output schema declared.
No examples provided.
search_by_tag ~53
Find (namespace, key) pairs with a given tag. Returns up to 1000 results.
| Name | Type | Req | Description |
|---|---|---|---|
| tag | string | yes | Tag to search for. Returns up to 1000 (namespace, key) pairs. |
No output schema declared.
No examples provided.
settle_balance ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_exit_feedback ~85
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Optional free-text context (truncated at 2000 chars) |
| reason | string | yes | Primary reason for not activating |
No output schema declared.
No examples provided.
submit_feature_request ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Description of the requested feature (truncated at 10,000 chars) |
No output schema declared.
No examples provided.
top_memories ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| n | integer | – | Number of keys to return (default 10, max 1000) |
| namespace | string | yes | ≤ 255 characters, no '/' |
No output schema declared.
No examples provided.
What is the AI Cortex Storage MCP server?
AI Cortex Storage is an MCP server listed in the public MCP registry as dev.aic0rt3x.memory/mcp. Persistent cloud memory for AI agents. Store and search key-value memories across sessions. This page covers its hosted endpoint (https://memory.aic0rt3x.dev/mcp).
Is the AI Cortex Storage MCP server safe to use?
AI Cortex Storage scores 73 out of 100 on VerifyMCP. 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 AI Cortex Storage MCP server expose?
AI Cortex Storage exposes 15 tools: get_memory, put_memory, delete_memory, list_keys, top_memories, and 10 more. Their descriptions and schemas cost roughly 857 tokens of context every time the server is loaded.
Does the AI Cortex Storage MCP server require authentication?
No. We connected to AI Cortex Storage without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI Cortex Storage MCP server still maintained?
AI Cortex Storage is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.