mcp-scraper 0.66.1 → 0.66.3

package/CHANGELOG.md

@@ -4,6 +4,31 @@ All notable changes to MCP Scraper are documented here. The format is based on [
 
 ## [Unreleased]
 
+## [0.66.3] - 2026-08-25
+
+### Changed
+
+- Runtime MCP discovery now omits output schemas across hosted OAuth, API-key, npm stdio, and MCPB clients, while the complete generated developer contract continues to supply typed Node and Python SDK outputs.
+
+### Fixed
+
+- Restored compatibility for strict MCP clients that could connect successfully but silently register zero tools when the complete output-schema catalog was advertised; tool calls retain both readable content and structured results.
+
+## [0.66.2] - 2026-08-24
+
+### Changed
+
+- Hosted MCP, npm stdio, and MCPB now advertise every recorded tool output schema from one canonical contract; the former `none`, `essential`, and `all` environment profiles no longer change `tools/list`.
+- Ordinary PAA calls continue to wait directly for their result, while Task-capable hosted clients start the same work immediately and poll its persisted status without routing the run through a scheduler.
+- Direct PAA Tasks now allow three total managed-browser attempts, keeping the first two retryable browser interruptions or verification challenges inside the same Task and billing hold before exposing a terminal failure.
+
+### Fixed
+
+- Direct PAA Tasks no longer sit in an external event queue before browser work begins; the request runtime starts provider work immediately and uses its existing 800-second execution window.
+- Complete output-schema advertising no longer causes Task-capable tools to be serialized as already-completed calls; hosted Task starts are validated and returned through the Task extension seam before terminal output validation.
+- Replaying an idempotent request returns the existing run and never redispatches it, preserving duplicate-charge protection without turning replay into job recovery.
+- Public npm artifacts no longer embed a developer-machine path for optional site-audit ZIP classification; installs use portable configuration and keep the existing LLM fallback when that dataset is absent.
+
 ## [0.66.1] - 2026-08-24
 
 ### Changed
@@ -1073,7 +1098,10 @@ All notable changes to MCP Scraper are documented here. The format is based on [
 - Write actions remain unavailable until the account owner explicitly enables them.
 - Provider-specific connection data is normalized into one agent-facing contract.
 
-[Unreleased]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.66.0...HEAD
+[Unreleased]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.66.3...HEAD
+[0.66.3]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.66.2...v0.66.3
+[0.66.2]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.66.1...v0.66.2
+[0.66.1]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.66.0...v0.66.1
 [0.66.0]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.65.1...v0.66.0
 [0.65.1]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.65.0...v0.65.1
 [0.65.0]: https://github.com/VilovietaSEO/mcp-scraper/compare/v0.64.1...v0.65.0

package/README.md

@@ -159,7 +159,7 @@ Build the branded one-click bundle:
 npm run build:mcpb
 ```
 
-The generated bundle is written to `build/mcpb/mcp-scraper-<version>.mcpb` and copied to `public/downloads/` for the hosted download. The current public bundle is `https://mcpscraper.dev/downloads/mcp-scraper.mcpb` (`0.66.1`, SHA-256 `4784c8f97d3e4eebe423f11454760efbfca7d65b5f03bcb27401b15d84d6a4ad`). Install it by opening or dragging it into Claude Desktop. Claude displays the `MCP Scraper` install card, icon, API-key configuration field, and manually curated current-release message from the bundle manifest.
+The generated bundle is written to `build/mcpb/mcp-scraper-<version>.mcpb` and copied to `public/downloads/` for the hosted download. The current public bundle is `https://mcpscraper.dev/downloads/mcp-scraper.mcpb` (`0.66.3`, SHA-256 `353b034b878340971fc1e07ca2ccf11578d6fd2e2ff894c8da1fa7df2c2bbd2d`). Install it by opening or dragging it into Claude Desktop. Claude displays the `MCP Scraper` install card, icon, API-key configuration field, and manually curated current-release message from the bundle manifest.
 
 The MCPB install exposes every tool — web-intelligence plus all `browser_*` tools — through the one `mcp-scraper` server.
 
@@ -315,7 +315,7 @@ For Google SERP and Maps tools, callers provide the query, two-letter country co
 
 The `mcp-scraper` server (and the MCPB bundle, which runs it) exposes both sections through one MCP server.
 
-All MCP tools expose output schemas and return `structuredContent` with the IDs, URLs, CSV paths, transcripts, browser session handles, replay paths, artifacts, recipe fields, or blueprint fields needed by the next step. Browser Agent tools keep a JSON text block for older clients, but structured data is the primary contract. All tools carry MCP annotations; file-writing tools such as replay downloads and annotations state their filesystem side effects.
+All MCP tools return `structuredContent` with the IDs, URLs, CSV paths, transcripts, browser session handles, replay paths, artifacts, recipe fields, or blueprint fields needed by the next step, plus readable text content for compatibility. Runtime `tools/list` omits output schemas so strict clients can register the complete catalog; the generated developer manifest retains every canonical output schema for validation and typed SDK generation. All tools carry MCP annotations; file-writing tools such as replay downloads and annotations state their filesystem side effects.
 
 The canonical tool inventory is generated at `docs/mcp-tool-manifest.generated.json`. The unified server exposes 259 tools: 158 scraper, browser, workflow, billing, and connected-service tools plus 101 durable-memory tools. The scraper-side inventory includes rendered site-content similarity, governed Local Sourcebook tools, Transparent Commons entity, linkset, and publication tools, direct site-export text and image readers, the searchable News Publisher and Editorial Reading Room template workflow, and 24 X-Ray tools for pixel administration, reporting, attribution journeys, campaign links, exports, and scheduled reports. Successful evidence-compiled Local Sourcebook revisions publish automatically to their canonical `localsourcebook.com` category profile and review URLs; administrator controls handle exceptional rejection or unpublishing. Release verification compares the exact local and hosted tool-name sets, not only the count.