Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.usememra/memra

REMOTE · USEMEMRA.COM

Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.

Available components

0 this week 18 Trust /100

Last scanned (13 hours ago)

Scores higher than 3% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Memory and Knowledge

Trust breakdown (7 categories)

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
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (4)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (7)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 503, which proves neither a plaintext path nor enforcement.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 6 Nov 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
  • 19 Oct 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 10 Oct 26 0
    • Stability: 0.90 → pass security
  • 28 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
  • 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
  • 8 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 7 Sept 26 0
    • Authorization: unverified → fail ▼ security
    • Authorization: unverified → fail ▼ security
    • Transport: fail → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • HTTPS: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Tool coverage: 92 functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
    • Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
    • Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
    • Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
  • 5 Sept 26 0
    • Transport: unverified → fail ▼ security
    • Authorization: fail → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
Diagnostics

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 21 Nov 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 29 Sept 2026 28 Dec 2026 RSA 4096 SHA256-RSA 5e81adb3988370c0d206fe3835db95c663f
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. DS published 19718 13 Verified
usememra.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503

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 HTTP error 503
http (plaintext) http://usememra.com/mcp Inconclusive 503
MCP tools · 7 exposed · ~1,125 tokens

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 →

Tool Tokens
memra_bootstrap ~124

Load agent bootstrap context from Memra. Returns priority-ordered memories for agent session initialization.

NameTypeReqDescription
agent_idstring–Agent identifier, defaults to API key ID
exclude_typesarray–Exclude these memory types
include_typesarray–Only include these memory types
max_tokensinteger–Token budget for bootstrap payload
namespacestringyesTenant namespace
project_idstring–Project ID (required if account has multiple projects)
recency_daysinteger–Include context from last N days
NameTypeReqDescription
health_warningsarray––
memoriesarrayyes–
revisioninteger––
token_estimateintegeryes–

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).

NameTypeReqDescription
memory_idstringyesThe memory ID to retrieve
NameTypeReqDescription
contentstringyes–
content_classificationstring––
content_originstring|null––
created_atstring|null––
idstringyes–
importanceinteger|null––
metadataobject|array|null––
namespacestring|null––
project_idstring|null––
tagsarray––
trust_statestringyes–
typestringyes–
untrusted_contentbooleanyes–
updated_atstring|null––
uristringyes–
verification_methodstring|null––
verified_bystring|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.

NameTypeReqDescription
memory_idstringyesAny memory ID in the chain
NameTypeReqDescription
chainarrayyes–
lengthintegeryes–

No examples provided.

memra_list ~97

List memories in Memra for a namespace. Returns paginated results with filtering options.

NameTypeReqDescription
limitinteger–Max results
min_importanceinteger–Minimum importance
namespacestringyesTenant namespace
offsetinteger–Pagination offset
project_idstring–Filter by project ID
tagsarray–Filter by tags
typestring–Filter by memory type
NameTypeReqDescription
memoriesarrayyes–
totalintegeryes–

No examples provided.

memra_recall ~287

Search memories in Memra by semantic similarity. Returns ranked results by relevance. Replaces memra_search.

NameTypeReqDescription
limitinteger–Max results to return
max_tokensinteger–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_confidencenumber–Minimum confidence score
namespacestringyesTenant namespace to search within
not_tagsarray–Exclude memories carrying any of these tags.
project_idstring–Filter by project ID
querystringyesSearch query for semantic matching
sincestring–Only memories created at or after this ISO-8601 date.
tagsarray–Filter by tags
typestring–Filter by memory type
untilstring–Only memories created at or before this ISO-8601 date.
used_idsarray–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_revisioninteger–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.
NameTypeReqDescription
estimated_tokensinteger––
resultsarrayyes–
total_candidatesintegeryes–

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.

NameTypeReqDescription
contentstring–Single/decision mode: memory content. Required unless using entries[] or pattern mode.
contextstring–Decision mode: reasoning/context for the decision.
entriesarray–Bulk mode: array of memory entries (max 25). When provided, the server routes to batch create.
gotchasarray–Pattern mode: common pitfalls.
importanceinteger––
maskboolean––
metadataobject––
namespacestring–Tenant namespace. Required for single, decision, and pattern modes.
project_idstring–Project ID (required if account has multiple projects)
stepsarray–Pattern mode: ordered steps. Required with title when type=pattern.
tagsarray––
titlestring–Pattern mode: title. Required with steps when type=pattern.
typestring–Memory type; use decision for decision mode and pattern for pattern mode.
verify_checklistarray–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).

NameTypeReqDescription
contentstringyesNew content that replaces the old memory
importanceinteger–Override importance (defaults to old memory's importance)
memory_idstringyesID of the memory to supersede
metadataobject–Override metadata (defaults to old memory's metadata)
tagsarray–Override tags (defaults to old memory's tags)
NameTypeReqDescription
embedding_statusstring––
new_memory_idstringyes–
revisioninteger–Read-your-writes token — pass to memra_recall as wait_for_revision.
superseded_memory_idstringyes–
typestringyes–

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http com-usememra-memra 'https://usememra.com/mcp'
Common questions

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 18 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?

Its publisher declares no required credentials for com.usememra/memra. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.usememra/memra MCP server?

VerifyMCP ran 4 checks on com.usememra/memra, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about com.usememra/memra: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.