Repository navigation
Conversation
Stdio and stateless Streamable HTTP, on MCP SDK v2, for 2026-07-28 and 2025-era clients alike. It answers from the published docs-index.json, npm and the Zunia chain registry, read when asked, and runs the SDK's own explainZuniaError, verifySignIn, ibcDenomHash and buildForwardMemo, so an answer matches the shipped packages. Read-only: it never signs and holds no keys. The tarball checks and smoke test now cover it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…MCP server. api.zunialab.com has served zunia.connect.v2 to any dApp origin since the relay went public (CORS is open on /v1/connect/), so the examples use it and no longer tell dApps to run their own. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
@zunialab/mcp0.1.0. An MCP server for coding assistants, over stdio and stateless Streamable HTTP (MCP SDK v2). It serves clients on the 2026-07-28 protocol and 2025-era clients alike.docs-index.json, written by every docs build), npm and the Zunia chain registry, read when asked. Nothing is bundled, so an answer is never older than what is published.search_docs,get_doc,list_docs,list_integrations,get_integration_guide,get_sdk_packages,get_chain,check_address,explain_error,verify_sign_in,ibc_denom,build_forward_memo.explainZuniaError,verifySignIn,ibcDenomHashandbuildForwardMemo, so answers match the shipped packages.integrate_zunia.api.zunialab.comis open to any site: CORS is open on/v1/connect/, and Zunia mobile store builds trust only that relay. The examples now use it instead of telling dApps to run their own. The MCP package is listed.scripts/pack.mjsandsmoke-tarballs.mjsnow cover the new package. The smoke test installs the packed tarball and talks to its bin over stdio.After merge
zunia-mcp.serviceserveshttps://docs.zunialab.com/mcp.sdk-core,sdk-web,sdk-reactandinterchain(npm still has 0.1.0), plus@zunialab/mcp0.1.0. Then tagv0.1.1.Checks run
pnpm build,typecheckandtestpass: 720 tests (interchain 543, core 91, web 44, mcp 37, react 5).check:packagespasses (publint, attw), and so doessmoke:tarballs(Node, Vite, and the MCP bin over stdio).🤖 Generated with Claude Code