MemoFS MCP Server
REMOTE · MEMOFS.DEV · 2 COMPONENTS
Persistent memory and virtual filesystem MCP server for AI agents.
Available components
Last scanned (18 hours ago)
Scores higher than 0% of remote servers
Reachable. Last reached 27 Sep 2026.
Category Memory and Knowledge
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 Security0
- TLS not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.Unverified
- Authorisation not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.Unverified
- HTTPS not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check. View diagnostics → Unverified
- HSTS not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.Unverified
- DNSSEC not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.Unverified
Transport & Reachability0
- Transport not yet verified: the listed URL is a template whose projectId variable has no value or default, so there is no address for us to connect to. See how to fix → View diagnostics → Unverified
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: 7 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.
Checks we ran (0)
We have not been able to confirm any check yet.
Checks we could not complete (11)
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.
- TLS certificate in Endpoint Security (scores 0 for this)TLS not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.
- Authorization in Endpoint Security (scores 0 for this)Authorisation not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.
- HTTPS in Endpoint Security (scores 0 for this)HTTPS not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.
- HSTS header in Endpoint Security (scores 0 for this)HSTS not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.
- DNSSEC in Endpoint Security (scores 0 for this)DNSSEC not yet verified: the listed URL is a template whose projectId variable has no value or default, so there was no address for us to check.
- Transport in Transport & Reachability (scores 0 for this)Transport not yet verified: the listed URL is a template whose projectId variable has no value or default, so there is no address for us to connect to.
- 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 →
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.
- 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
- 20 Sept 26 0
- Transport: unverified → fail ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: pass → fail ▼ security
- HTTPS: unverified → pass ▲ 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
- 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
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. 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
- 17 Aug 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 5 Nov 2026 · Probed https://memofs.dev/api/v1/projects/{projectId}/mcp
Transports 1 probe
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| http (plaintext) | http://memofs.dev/api/v1/projects/%7BprojectId%7D/mcp | Inconclusive |
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 →
No tool schema has been captured from this endpoint yet.
How do I install the MemoFS MCP Server server?
MemoFS MCP Server is a hosted endpoint at https://memofs.dev/api/v1/projects/%7BprojectId%7D/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 · memofs.dev
claude mcp add --transport http dev-memofs-mcp-server 'https://memofs.dev/api/v1/projects/%7BprojectId%7D/mcp'
What is the MemoFS MCP Server server?
MemoFS MCP Server is listed in the public MCP registry as dev.memofs/mcp-server. Persistent memory and virtual filesystem MCP server for AI agents. This page covers its hosted endpoint (https://memofs.dev/api/v1/projects/{projectId}/mcp).
Is the MemoFS MCP Server server safe to use?
MemoFS MCP Server scores 0 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.
Does the MemoFS MCP Server server require authentication?
Its publisher declares that MemoFS MCP Server requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the MemoFS MCP Server server still maintained?
MemoFS MCP Server is still listed as active in the MCP registry. We last reached this channel on 27 September 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 MemoFS MCP Server server?
VerifyMCP could not confirm any check on MemoFS MCP Server yet. 11 items could not be completed, a gap on our side rather than a finding about MemoFS MCP Server: TLS certificate, Authorization, HTTPS, HSTS header and 7 more. 7 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.