mcp-scraper 0.29.0 → 0.29.1

package/docs/mcp-tool-manifest.generated.json

@@ -1,9 +1,9 @@
 {
-  "generatedAt": "2026-07-20T22:25:32.188Z",
+  "generatedAt": "2026-07-20T23:54:07.092Z",
   "generatedFrom": "dist/bin/mcp-stdio-server.js",
   "serverInfo": {
     "name": "mcp-scraper",
-    "version": "0.29.0"
+    "version": "0.29.1"
   },
   "counts": {
     "unified_stdio": 165
@@ -9870,7 +9870,7 @@
     {
       "name": "import_service_connection_to_memory",
       "title": "Import Connected Service Snapshot to Memory",
-      "description": "Run exactly one bounded, approved read on a tenant-owned connected service and upsert the redacted result into an existing ordinary Memory vault at a server-generated stable path. The saved document is embedded for RAG and marked as untrusted provider data, never instructions. This is a one-result snapshot: it does not paginate, bulk-import an account, continuously sync changes, propagate deletions, or create normalized tables. Use list_service_connections first and supply an exact current readTools entry; action and admin tools are rejected.",
+      "description": "Run exactly one bounded, approved read on a tenant-owned connected service and upsert the redacted result into an existing ordinary Memory vault at a server-generated stable path. The saved document is embedded for RAG and marked as untrusted provider data, never instructions. This is a one-result snapshot: it does not paginate, bulk-import an account, continuously sync changes, propagate deletions, or create normalized tables. It is not a People contact-card activity importer: when the user asks to add verified Gmail or Calendar activity to a person, resolve the People hub and create a linked Communications or Calendar record with stable provider references instead. Use list_service_connections first and supply an exact current readTools entry; action and admin tools are rejected.",
       "inputSchema": {
         "type": "object",
         "properties": {
@@ -12775,7 +12775,7 @@
     {
       "name": "memory-capture",
       "title": "Capture Governed Memory",
-      "description": "Strict normal-create path for durable memory. Before capture, list the complete tag vocabulary, call prepare-memory-write, run hybrid memory-search for related notes, and read the strongest link candidates. This tool refuses incomplete notes and invalid relationship-domain writes: projects need a project kind, tasks need a verified project, deals need a known party, and draft emails need a pending approval state. It writes through memory-put, registers canonical tags, and verifies persisted content and props. Reserve memory-put for low-level migrations or deliberate edits.",
+      "description": "Strict normal-create path for durable memory. Before capture, list the complete tag vocabulary, call prepare-memory-write, run hybrid memory-search for related notes, and read the strongest link candidates. This tool refuses incomplete notes and invalid relationship-domain writes: projects need a project kind, tasks can be independent Inbox todos or link a verified project, deals need a known party, and draft emails need a pending approval state. It writes through memory-put, registers canonical tags, and verifies persisted content and props. Reserve memory-put for low-level migrations or deliberate edits.",
       "inputSchema": {
         "type": "object",
         "properties": {
@@ -13753,7 +13753,7 @@
     {
       "name": "memory-put",
       "title": "Put Memory Note",
-      "description": "Create or deliberately edit one note at a path in a memory vault; content is persisted and indexed for search. For normal new People, Deals, Projects, Tasks, or Communications records, use prepare-memory-write then memory-capture: People must be real people or organizations, Deals need a known party, Projects need a supported kind, Tasks need a verified Project, and draft emails need pending approval. For row-shaped datasets you'll filter/sort by exact value, use table-create/table-insert-rows/table-query instead. Ordinary vaults are indexed and shareable — never store real secrets there; use a secure vault (create-secure-vault) instead, which is never indexed or shareable and is encrypted at rest. Requires write scope.",
+      "description": "Create or deliberately edit one note at a path in a memory vault; content is persisted and indexed for search. For normal new People, Deals, Projects, Tasks, or Communications records, use prepare-memory-write then memory-capture: People must be real people or organizations, Deals need a known party, Projects need a supported kind, Tasks may be independent Inbox todos or use a verified Project link when requested, and draft emails need pending approval. For row-shaped datasets you'll filter/sort by exact value, use table-create/table-insert-rows/table-query instead. Ordinary vaults are indexed and shareable — never store real secrets there; use a secure vault (create-secure-vault) instead, which is never indexed or shareable and is encrypted at rest. Requires write scope.",
       "inputSchema": {
         "type": "object",
         "properties": {
@@ -15167,7 +15167,7 @@
     {
       "name": "prepare-memory-write",
       "title": "Prepare Memory Write",
-      "description": "Mandatory planning pass for a normal new memory. First inspect the complete tag vocabulary with list-memory-tags; then this pass routes the note, returns the live template and natural vault relationships, resolves proposed tags, and shortlists interlinks. For People, Deals, Projects, Tasks, and Communications, it also returns required relationship and approval guidance: search existing records first and ask rather than inventing a missing project or party. Use hybrid memory-search (3 focused queries, 50 fused candidates, bounded graph expansion, rerank to 30 by default) and read strong related notes before capture. This is an explicit AI workflow directive, not a claim of persisted call-order enforcement.",
+      "description": "Mandatory planning pass for a normal new memory. First inspect the complete tag vocabulary with list-memory-tags; then this pass routes the note, returns the live template and natural vault relationships, resolves proposed tags, and shortlists interlinks. For People, Deals, Projects, Tasks, and Communications, it also returns relationship and approval guidance: a Task may be an independent Inbox todo, so search existing records only before adding a requested project or party link and never invent one. Use hybrid memory-search (3 focused queries, 50 fused candidates, bounded graph expansion, rerank to 30 by default) and read strong related notes before capture. This is an explicit AI workflow directive, not a claim of persisted call-order enforcement.",
       "inputSchema": {
         "type": "object",
         "properties": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-scraper",
-  "version": "0.29.0",
+  "version": "0.29.1",
   "description": "MCP server for MCP Scraper web intelligence tools",
   "type": "module",
   "main": "./dist/index.cjs",
@@ -77,7 +77,7 @@
     "hono": "^4.12.18",
     "inngest": "^4.4.0",
     "jose": "^6.2.3",
-    "mcpscraper-memory-tools": "^1.8.2",
+    "mcpscraper-memory-tools": "^1.8.4",
     "p-limit": "^7.3.0",
     "papaparse": "^5.4.0",
     "playwright": "^1.44.0",