MemoFS MCP Server
Local MCP server · registry.npmjs.org · found in a public registry · checked since 2026-10-18
Package available · latest check
@memofs/mcp-server · latest version 1.3.0-beta.3, changed 2026-08-17The name is the registry's label, not ours. Not reviewed by a person.
Our checks
A package check monthly, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked monthly. Local MCP servers (package checks): weekly once the service's place in the capability tree is confirmed, monthly otherwise.
Details
Access
- Our latest check
- not observed: our check does not call the service itself
- Stated
- not stated
- Payment model
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Compute, code and storage / Memory (primary). Placed by keyword rules (placement-rules/3, tree/3) on 2026-10-18. Wrong place? Tell us.
In the index only: does not meet every one of our listing criteria (listing-criteria/3): ✗ what it does is unclear to our placement; ✓ its latest check passed.
Recent package checks
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Package available HTTP 200 | 381 ms |
What these figures do not show
- A passing check means the package exists in its registry and its latest version is not deprecated or yanked (package-check/1). It does not show that the server works, what its tools do, or that it is safe to run: it runs on your machine with the access you give it.
- Listed in the Official MCP Registry; the package facts come from npm or PyPI. The registry's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_760a20f033beb49e