[PulseBet]

The README currently starts with tool/integration details, uses floating npm install commands, and still says 1.3.1 is unpublished. It now leads with the GitHub MCP listing and a complete keyless install → BTC sample → unchanged-receipt verification workflow, including the requested sample prompt and explicit signature/access boundaries.

All README npm commands pin pulse-verity@1.3.1: this is the actual package selected by the official registry's metadata version 1.3.2. npm confirms publication on October 4, 2026; the linked MCPB also exists. Detailed signature coverage and integration instructions are preserved. The security summary now accurately distinguishes the five data tools from the separate private feedback tool.

Validation:

• Passed: WORDS gate; Cursor, Grok, Gemini, and Claude plugin static checks; README relative links/anchors; exact prompt/pin checks; git diff --check.
• Passed: existing claude-plugin-smoke.mjs --candidate-entry <published-1.3.1>/dist/index.js --live against the published npm archive using existing dependencies and an explicitly empty API key. One BTC sample and its unchanged receipt verified (recordValid=true, verificationScope=full-record). No feedback was submitted.
• Existing static checks: 26 passed, 2 failed. Both failures reproduce against pristine base 907c2c539f430b5201546517c2ce540b587bf933: manifest-copy-test.mjs rejects the registry description's “offline” wording and rejects registry metadata version 1.3.2 pointing to npm 1.3.1. Registry records and test policy are unchanged by this README-only PR.
• Five linked public resources returned HTTP 200, including the listing, developer pages, Grok guide and MCPB (HEAD only). npm's package webpage returned HTTP 403; npm registry metadata and the archive were accessible, and archive SHA-512/SHA-1 matched published values.
• Never run locally: builds, dependency installation, full npm test, emulator/media work, or publication/deployment workflows.

Version audit: source/package/client pins remain 1.3.1; the published package's MCP SDK dependency is ^1.6.1, while current upstream source declares ^1.32.1. Matching version strings do not mean source/dependency changes are already distributed. The unchanged Smithery configuration still floats pulse-verity without a version and overstates key-based coverage (including a fixed asset count and implying verification needs a key). Those differences are reported for the configuration owner; no blind version bump or npm/registry update is included.

This PR does not change runtime code, services, pricing, quotas, authentication, registry records, website implementation or billing. No merge or deployment is requested.

Remote CI for da4df048e2f2aa1d15f77cc18f35866060e50d3d: Claude plugin passed, including its build and candidate stdio check on GitHub runners. Gemini extension failed at npm test with the same two baseline manifest-copy failures; packaging, audit, install and MCP smoke steps were skipped. Publish and verify-published jobs were skipped. No CI workflow was manually dispatched.