com.usememra/memra
REMOTE · USEMEMRA.COM · SCANNED SEP 23
Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1388 tokens (~198/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the com.usememra/memra MCP server?
com.usememra/memra is a hosted endpoint at https://usememra.com/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 · usememra.com
claude mcp add --transport http com-usememra-memra 'https://usememra.com/mcp'
{
"mcpServers": {
"com-usememra-memra": {
"url": "https://usememra.com/mcp"
}
}
} {
"servers": {
"com-usememra-memra": {
"type": "http",
"url": "https://usememra.com/mcp"
}
}
} [mcp_servers.com-usememra-memra] url = "https://usememra.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-usememra-memra": {
"type": "remote",
"url": "https://usememra.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-usememra-memra --url 'https://usememra.com/mcp' --transport streamable-http
mcp_servers:
com-usememra-memra:
url: "https://usememra.com/mcp" {
"McpServers": {
"com-usememra-memra": {
"Transport": "http",
"Url": "https://usememra.com/mcp"
}
}
} assistant mcp add com-usememra-memra -t streamable-http -u 'https://usememra.com/mcp'
{
"mcpServers": {
"com-usememra-memra": {
"type": "http",
"url": "https://usememra.com/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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 23 Sept 2026 · Probed https://usememra.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usememra.com | CN=YR2,O=Let's Encrypt,C=US | 31 Jul 2026 | 29 Oct 2026 | RSA 4096 | SHA256-RSA | 5598a96641fe57eec2b5c567cbc8d82d7ab |
| SANs: usememra.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of usememra.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| usememra.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer
Bearer| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://usememra.com/mcp | Verified | 200 | |
| http (plaintext) | http://usememra.com/mcp | HTTPS enforced | 302 | https://usememra.com/mcp |
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 →
memra_bootstrap ~124
Load agent bootstrap context from Memra. Returns priority-ordered memories for agent session initialization.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Agent identifier, defaults to API key ID |
| exclude_types | array | – | Exclude these memory types |
| include_types | array | – | Only include these memory types |
| max_tokens | integer | – | Token budget for bootstrap payload |
| namespace | string | yes | Tenant namespace |
| project_id | string | – | Project ID (required if account has multiple projects) |
| recency_days | integer | – | Include context from last N days |
| Name | Type | Req | Description |
|---|---|---|---|
| health_warnings | array | – | – |
| memories | array | yes | – |
| revision | integer | – | – |
| token_estimate | integer | yes | – |
No examples provided.
memra_get ~48
Get a single memory by ID with full content. Use when you need the complete text of a memory (search results are truncated).
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | The memory ID to retrieve |
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | – |
| content_classification | string | – | – |
| content_origin | string|null | – | – |
| created_at | string|null | – | – |
| id | string | yes | – |
| importance | integer|null | – | – |
| metadata | object|array|null | – | – |
| namespace | string|null | – | – |
| project_id | string|null | – | – |
| tags | array | – | – |
| trust_state | string | yes | – |
| type | string | yes | – |
| untrusted_content | boolean | yes | – |
| updated_at | string|null | – | – |
| uri | string | yes | – |
| verification_method | string|null | – | – |
| verified_by | string|null | – | – |
No examples provided.
memra_history ~106
View the full supersession chain for a memory (oldest to newest). Use this when you need to audit how a fact or decision evolved over time — e.g., the user asks "why did we change X?", you need to understand prior reasoning before proposing another change, or you spotted a superseded_by reference and need the full timeline. Given any memory ID in the chain, returns every predecessor and successor.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | Any memory ID in the chain |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | array | yes | – |
| length | integer | yes | – |
No examples provided.
memra_list ~97
List memories in Memra for a namespace. Returns paginated results with filtering options.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results |
| min_importance | integer | – | Minimum importance |
| namespace | string | yes | Tenant namespace |
| offset | integer | – | Pagination offset |
| project_id | string | – | Filter by project ID |
| tags | array | – | Filter by tags |
| type | string | – | Filter by memory type |
| Name | Type | Req | Description |
|---|---|---|---|
| memories | array | yes | – |
| total | integer | yes | – |
No examples provided.
memra_recall ~287
Search memories in Memra by semantic similarity. Returns ranked results by relevance. Replaces memra_search.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return |
| max_tokens | integer | – | Token budget: return the best-scoring results that fit within this many tokens (chars/4 heuristic). Combine with a higher limit to fill the budget. |
| min_confidence | number | – | Minimum confidence score |
| namespace | string | yes | Tenant namespace to search within |
| not_tags | array | – | Exclude memories carrying any of these tags. |
| project_id | string | – | Filter by project ID |
| query | string | yes | Search query for semantic matching |
| since | string | – | Only memories created at or after this ISO-8601 date. |
| tags | array | – | Filter by tags |
| type | string | – | Filter by memory type |
| until | string | – | Only memories created at or before this ISO-8601 date. |
| used_ids | array | – | Feedback: memory IDs from your PREVIOUS recall that you actually used. They gain a small permanent ranking boost — pass these every time to make recall learn. |
| wait_for_revision | integer | – | Read-your-writes: pass the revision returned by memra_remember to block (max 5s) until that write is indexed and searchable. Use when recalling something you just stored. |
| Name | Type | Req | Description |
|---|---|---|---|
| estimated_tokens | integer | – | – |
| results | array | yes | – |
| total_candidates | integer | yes | – |
No examples provided.
memra_remember ~313
Store one or many memories in Memra. Single mode: pass content + namespace. Decision mode: pass type=decision with content + namespace (optionally context). Pattern mode: pass type=pattern with title + steps + namespace. Bulk mode: pass entries[]. If the response contains conflicts[], the new fact contradicts those existing memories — review them and use memra_supersede on the outdated one instead of leaving both active.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | Single/decision mode: memory content. Required unless using entries[] or pattern mode. |
| context | string | – | Decision mode: reasoning/context for the decision. |
| entries | array | – | Bulk mode: array of memory entries (max 25). When provided, the server routes to batch create. |
| gotchas | array | – | Pattern mode: common pitfalls. |
| importance | integer | – | – |
| mask | boolean | – | – |
| metadata | object | – | – |
| namespace | string | – | Tenant namespace. Required for single, decision, and pattern modes. |
| project_id | string | – | Project ID (required if account has multiple projects) |
| steps | array | – | Pattern mode: ordered steps. Required with title when type=pattern. |
| tags | array | – | – |
| title | string | – | Pattern mode: title. Required with steps when type=pattern. |
| type | string | – | Memory type; use decision for decision mode and pattern for pattern mode. |
| verify_checklist | array | – | Pattern mode: verification checklist. |
Structured output declared, but exposes no named fields.
No examples provided.
memra_supersede ~150
Replace a memory with new content. The old memory is marked superseded and stops appearing in search; the new memory inherits the old memory's type, importance, tags, source and metadata unless overridden. Works for all memory types (use this instead of memra_add when you are correcting or updating existing knowledge).
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | New content that replaces the old memory |
| importance | integer | – | Override importance (defaults to old memory's importance) |
| memory_id | string | yes | ID of the memory to supersede |
| metadata | object | – | Override metadata (defaults to old memory's metadata) |
| tags | array | – | Override tags (defaults to old memory's tags) |
| Name | Type | Req | Description |
|---|---|---|---|
| embedding_status | string | – | – |
| new_memory_id | string | yes | – |
| revision | integer | – | Read-your-writes token — pass to memra_recall as wait_for_revision. |
| superseded_memory_id | string | yes | – |
| type | string | yes | – |
No examples provided.
What is the com.usememra/memra MCP server?
com.usememra/memra is an MCP server listed in the public MCP registry as com.usememra/memra. Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection. This page covers its hosted endpoint (https://usememra.com/mcp).
Is the com.usememra/memra MCP server safe to use?
com.usememra/memra scores 79 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 com.usememra/memra MCP server expose?
com.usememra/memra exposes 7 tools: memra_remember, memra_recall, memra_get, memra_list, memra_supersede, and 2 more. Their descriptions and schemas cost roughly 1,125 tokens of context every time the server is loaded.
Does the com.usememra/memra MCP server require authentication?
Yes. com.usememra/memra asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.usememra/memra MCP server still maintained?
com.usememra/memra is still listed as active in the MCP registry. We last reached this channel on 23 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.