loci
PYPI · LOCI-MEM
Scoped memory for coding agents: picks the right project, answers in scope, or abstains.
Available components
Last scanned (18 hours ago)
Scores higher than 86% of PyPI servers
Category Memory and Knowledge
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs maturin at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 1 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 54 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 209 tokens (~69/item across 3 items; 3 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 Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 0
- Provenance: unverified → fail ▼ security
- 27 Oct 26 0
- Provenance: fail → unverified ▼ security
- 26 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed pypi/loci-mem@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | maturin |
Background: Why install scripts are a supply-chain risk →
Dependencies 1 package
| Packages resolved | 1 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ask ~164
Answer a question about the user's projects. Routes to the right project automatically, then searches both its code structure and its written history (notes, docs, commits). Returns ABSTAINED when the question is too vague to route -- ask the user which project rather than guessing.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | The user's working directory. Pass it whenever known: it is the strongest routing signal. |
| group | string | – | Restrict to one group of projects, e.g. 'me' or 'client:delroy'. |
| k | integer | – | Episode hits per scope. |
| question | string | yes | – |
| rerank | boolean | – | Cross-encoder rerank; slower, better ordering. |
| scope | string | – | Force a project by name, bypassing routing. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | yes | – |
| clarify | object|null | – | – |
No examples provided.
doctor ~31
Report which projects have missing or thin coverage, and the command to fix each. Use when a question returns no evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scopes ~14
List indexed projects with their sizes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the loci MCP server?
loci runs locally as a PyPI package, launched with uvx loci-mem. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · loci-mem
claude mcp add 3m1ry33t-loci -- uvx loci-mem
What is the loci MCP server?
loci is an MCP server listed in the public MCP registry as io.github.3M1RY33T/loci. Scoped memory for coding agents: picks the right project, answers in scope, or abstains. This page covers its PyPI package (loci-mem).
Is the loci MCP server safe to use?
loci scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 loci MCP server expose?
loci exposes 3 tools: ask, scopes, doctor. Their descriptions and schemas cost roughly 209 tokens of context every time the server is loaded.
Is the loci MCP server still maintained?
loci is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the loci MCP server under?
loci declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.