memoryintelligence-mcp 0.2.9__tar.gz → 0.2.10__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.


This version of memoryintelligence-mcp might be problematic. Click here for more details.

Files changed (23) hide show
  1. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/PKG-INFO +2 -2
  2. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/pyproject.toml +1 -1
  3. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/__init__.py +1 -1
  4. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/scrub.py +39 -2
  5. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/.gitignore +0 -0
  6. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/CHANGELOG.md +0 -0
  7. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/CONTRIBUTING.md +0 -0
  8. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/LICENSE +0 -0
  9. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/README.md +0 -0
  10. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/__main__.py +0 -0
  11. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/cli.py +0 -0
  12. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/client.py +0 -0
  13. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/config.py +0 -0
  14. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/embedder.py +0 -0
  15. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/indexer.py +0 -0
  16. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/keys.py +0 -0
  17. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/local_index.py +0 -0
  18. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/localreads.py +0 -0
  19. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/paths.py +0 -0
  20. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/recall_guard.py +0 -0
  21. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/server.py +0 -0
  22. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/umo_format.py +0 -0
  23. {memoryintelligence_mcp-0.2.9 → memoryintelligence_mcp-0.2.10}/src/mi_mcp/vault.py +0 -0
@@ -1,6 +1,6 @@
1
- Metadata-Version: 2.4
1
+ Metadata-Version: 2.5
2
2
  Name: memoryintelligence-mcp
3
- Version: 0.2.9
3
+ Version: 0.2.10
4
4
  Summary: MCP server for MemoryIntelligence — give Claude a memory you own, set up in one command
5
5
  Project-URL: Homepage, https://memoryintelligence.io
6
6
  Project-URL: Repository, https://github.com/somewhere11/memoryintelligence-mcp
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "memoryintelligence-mcp"
7
- version = "0.2.9"
7
+ version = "0.2.10"
8
8
  description = "MCP server for MemoryIntelligence — give Claude a memory you own, set up in one command"
9
9
  readme = "README.md"
10
10
  license = "Apache-2.0"
@@ -1,3 +1,3 @@
1
1
  """MI MCP Server — MemoryIntelligence tools for Claude."""
2
2
 
3
- __version__ = "0.2.9"
3
+ __version__ = "0.2.10"
@@ -87,7 +87,39 @@ _SSN_RE = re.compile(r"\b(?!000|666|9\d\d)\d{3}[\s.\-]+(?!00)\d{2}[\s.\-]+(?!000
87
87
  #: Phone. `_PHONE_LONG` is the pre-existing 10–15 digit run. The short forms are
88
88
  #: the #1446/A2 gap: every alternative needed THREE digit groups, so "555-0142"
89
89
  #: and "+1-555-0142" leaked — including `pii-phone-001`, an EXEMPLAR fixture.
90
- _PHONE_LONG_RE = re.compile(r"(?<![\d.])(?:\+?\d[\s().-]?){10,15}(?![\d.])")
90
+ # ⚠️ #1586 — `_PHONE_LONG_RE` was `(?:\+?\d[\s().-]?){10,15}`, i.e. ANY 10–15
91
+ # digit run, with each digit allowed a trailing separator. Two defects fell out
92
+ # of that, and they compounded:
93
+ #
94
+ # 1. it matched UNIX EPOCH SECONDS — 10 digits, and the most common 10-digit
95
+ # run in MI's own corpus — so `the watermark is 1737654321 seconds` became
96
+ # `<PHONE>`;
97
+ # 2. the final iteration's `[\s().-]?` SWALLOWED THE FOLLOWING SEPARATOR, so
98
+ # the next word was glued to the marker: `the watermark is <PHONE>seconds`.
99
+ #
100
+ # This is not merely a thin-install concern. `scrub_text` applies `_HARD` on top
101
+ # of core's result unconditionally, so a floor looser than core *overwrites a
102
+ # correct answer with a wrong one* on every MCP read.
103
+ #
104
+ # Split into three precise patterns, mirroring `core/security/pii_detector.py`:
105
+ #
106
+ # SEPARATED — the separators themselves are the signal, so no digit-value
107
+ # constraint is needed. Ends on a DIGIT, which is defect 2's fix.
108
+ _PHONE_SEP_RE = re.compile(
109
+ r"(?<![\d.])\+?\d{1,4}[\s().\-]+\d(?:[\s().\-]?\d){6,12}(?![\d.])"
110
+ )
111
+ # E.164 — the leading `+` is the signal. Measured in core: 0 matches across
112
+ # 2,618 of MI's own files, so it needs no further constraint.
113
+ _PHONE_E164_RE = re.compile(r"(?<![\d+])\+[1-9]\d{9,14}(?![\d])")
114
+ # BARE 10-DIGIT — the dangerous one, and the direct fix for defect 1. Same two
115
+ # constraints core measured its way to: a NANP shape (area code and exchange
116
+ # both start 2-9), which excludes epoch seconds structurally because they begin
117
+ # with `1` until 2033; and an ALNUM-AWARE boundary, because the digits of a hex
118
+ # hash are still digits (`"svo_hash": "914eb6579098371c"` contains a 10-digit
119
+ # run). Core measured 360 → 48 → 1 matches as those are applied.
120
+ _PHONE_BARE10_RE = re.compile(
121
+ r"(?<![0-9A-Za-z._\-:+])[2-9]\d{2}[2-9]\d{6}(?![0-9A-Za-z\-])"
122
+ )
91
123
  _PHONE_INTL_SHORT_RE = re.compile(r"(?<![\d])\+\d{1,3}[\s.\-]?\d{3}[\s.\-]\d{4}(?![\d])")
92
124
  #: A bare 7-digit run is NOT distinctive — core measured it hitting file:line
93
125
  #: ranges, ULID fragments and coordinates — so it is CONTEXT-ANCHORED, as there.
@@ -126,7 +158,12 @@ _HARD = [
126
158
  (re.compile(r"\b(?:\d[ -]?){13,19}\b"), "<CARD>"),
127
159
  (_ADDRESS_RE, "<ADDRESS>"),
128
160
  (_PHONE_INTL_SHORT_RE, "<PHONE>"),
129
- (_PHONE_LONG_RE, "<PHONE>"),
161
+ # #1586 — order matters within the phone group: E.164 and the separated form
162
+ # first (both carry their own signal), bare-10 last so it only ever sees runs
163
+ # the more specific patterns did not already claim.
164
+ (_PHONE_E164_RE, "<PHONE>"),
165
+ (_PHONE_SEP_RE, "<PHONE>"),
166
+ (_PHONE_BARE10_RE, "<PHONE>"),
130
167
  ]
131
168
 
132
169