release: v0.3.0 — ship Layer 1 (npm 0.2.0 is the broken pre-Layer-1 build) + correct 2025-12-11 registry manifest

[BarisSozen]

Why

npm @hashlock-tech/mcp@0.2.0 is already published from gitHead 68ee2da — the pre-Layer-1 build (broken get_htlc via getHTLCStatus, no structured errors, no discovery tools, no idempotency). The merged Layer 1 hardening (PR #4) is also 0.2.0, so npm refuses to republish and the fix cannot reach agents. This bumps to 0.3.0.

Changes

• package.json + src/index.ts McpServer version 0.2.0 → 0.3.0 (npm version; SemVer minor — critical get_htlc bugfix + additive discovery tools, no breaking removal)
• Replace stale 2025-09-29 server.json (had an installation block, no packages[] — re-submitting it caused a prior bad registry publish) with the correct 2025-12-11 schema mirroring the live registry: packages[0].version: 0.3.0 (npm), top-level version: 1.3.0 = registry manifest-revision counter (live is 1.2.0; must exceed it to become isLatest — this is deliberately NOT the npm version; conflating them caused the 2026-05-12 re-submit), plus the streamable-http remote the stale file omitted
• mcp-registry.json: deleted as unreferenced stale duplicate — git grep confirmed zero references to it anywhere in the repo outside the file itself

Operator steps after merge (not done here — irreversible / your creds)

1. npm publish (0.3.0) from merged main
2. npm deprecate @hashlock-tech/mcp@0.2.0 "broken get_htlc — use >=0.3.0"
3. mcp-publisher registry re-publish (server.json now correct; bumps registry to 1.3.0, packages[].version 0.3.0; JWT TTL ~10min — login→validate→publish in one session)

Follow-ups: hashlock-mcp#5 (SUI-chain validation).

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated MCP server version to 0.3.0
  • Updated server configuration with new package and remote endpoint settings
  • Simplified registry configuration structure

[coderabbitai]

Warning

Rate limit exceeded

@BarisSozen has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 49 minutes and 15 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 79278fc9-38f0-449c-97ca-9b7fe498a2f8

📥 Commits

Reviewing files that changed from the base of the PR and between e8c8a4e and bd2c7ca.

📒 Files selected for processing (1)

• server.json

📝 Walkthrough

Walkthrough

This PR coordinates a version 0.3.0 release with a server configuration restructure. Package version and MCP server version constant are bumped to 0.3.0, and server.json is migrated from a legacy manifest format to a new structure introducing packages and remotes configuration blocks for npm registry and HTTP endpoint details.

Changes

Version 0.3.0 Release and Configuration

Layer / File(s)	Summary
Version bumps to 0.3.0 package.json, src/index.ts	Package version and MCP server version constant are both updated from 0.2.0 to 0.3.0.
Server manifest restructure with packages and remotes server.json	Server configuration is migrated from legacy format to new manifest version, introducing packages entry for @hashlock-tech/mcp with npm registry metadata, stdio transport, runtime args (-y auto-confirm), and environment variables (HASHLOCK_ENDPOINT with GraphQL default and HASHLOCK_ACCESS_TOKEN as required secret). A remotes block points to the streamable HTTP endpoint at https://hashlock.markets/mcp with required Authorization header for SIWE bearer token access.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 Hop, hop, hop—the version flies,
From point-two to point-three, a sunrise rise!
Config restructured, remotes in place,
The MCP server finds its new space. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly describes the main changes: version bump to v0.3.0, shipping Layer 1 with corrected registry manifest (replacing stale 2025-09-29 with 2025-12-11 version), and clarifying the npm 0.2.0 context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.3.0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@server.json`:
- Line 26: The default value for HASHLOCK_ENDPOINT in the manifest is incorrect
(it uses "/api/graphql") and causes 401s because the server code expects
"/graphql" (see src/index.ts handling of HASHLOCK_ENDPOINT). Update the default
for the HASHLOCK_ENDPOINT entry to use "https://hashlock.markets/graphql" so it
matches the path used by the server; ensure the manifest key name
"HASHLOCK_ENDPOINT" remains unchanged and verify src/index.ts continues to
reference that environment/manifest variable.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ce6ebbe8-577e-4e5d-a179-be0dd65b680c

📥 Commits

Reviewing files that changed from the base of the PR and between 559f651 and e8c8a4e.

📒 Files selected for processing (4)

• mcp-registry.json
• package.json
• server.json
• src/index.ts

💤 Files with no reviewable changes (1)

• mcp-registry.json