Skip to content

docs: refresh Injective MCP skill contract - #22

Open
aicyberg wants to merge 1 commit into
InjectiveLabs:masterfrom
aicyberg:docs/refresh-injective-mcp-skill
Open

docs: refresh Injective MCP skill contract#22
aicyberg wants to merge 1 commit into
InjectiveLabs:masterfrom
aicyberg:docs/refresh-injective-mcp-skill

Conversation

@aicyberg

@aicyberg aicyberg commented Aug 2, 2026

Copy link
Copy Markdown

Summary

  • document all tools currently registered by the official Injective MCP server
  • align the Node.js prerequisite with the MCP package engine requirement

Changes

  • add 13 missing tools covering address normalization, native USDC/CCTP, RFQ, frontend guidance, inbound deBridge, and AuthZ
  • mark read-only and transaction tools in their descriptions
  • update the prerequisite from Node.js v22+ to v24+

Validation

  • documented tool names exactly match all 37 server.tool(...) registrations at InjectiveLabs/mcp-server@daa98388cdf6c472c93211b1e9059725d72bc42e
  • Agent Skill validation passed
  • public and security preflight completed with no errors or warnings

@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@aicyberg, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 46994b7e-8534-4fa6-92e4-88151bac2ba9

📥 Commits

Reviewing files that changed from the base of the PR and between 6d68c2c and d23b988.

📒 Files selected for processing (1)
  • skills/injective-mcp-servers/SKILL.md

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

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant