Skip to content

Conversation

@punkpeye
Copy link

@punkpeye punkpeye commented Nov 5, 2025

This PR adds a badge for the Node.js Sandbox MCP Server server listing in Glama MCP server directory.

Node.js Sandbox Server MCP server

Glama performs regular codebase and documentation checks to:

  • Confirm that the MCP server is working as expected
  • Confirm that there are no obvious security issues with dependencies of the server
  • Extract server characteristics such as tools, resources, prompts, and required parameters.

This badge helps your users to quickly assess that the MCP server is safe, server capabilities, and instructions for installing the server.

Summary by Sourcery

Add a Glama MCP server badge to the README and fix a typo in the documentation.

Documentation:

  • Embed a Glama MCP server badge in the README linking to the Node.js Sandbox MCP server listing
  • Standardize apostrophe usage in a README bullet point

@punkpeye
Copy link
Author

punkpeye commented Nov 5, 2025

Realized that GitHub does not recognize the project license

https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository

Would you mind adding one?

@sourcery-ai
Copy link

sourcery-ai bot commented Nov 5, 2025

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR embeds a clickable Glama MCP server badge in the README to showcase server health and capabilities, and standardizes apostrophe styling for consistency.

File-Level Changes

Change Details Files
Added Glama MCP server badge markup
  • Inserted HTML anchor tag wrapping an image badge linking to the Glama MCP server directory
  • Specified badge dimensions and alt text
README.md
Standardized apostrophe usage
  • Replaced typographic apostrophe (’) with straight apostrophe (') in list item
README.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai
Copy link

coderabbitai bot commented Nov 5, 2025

Summary by CodeRabbit

  • Documentation
    • Added an MCP server badge to the documentation.
    • Updated text formatting for consistency.

Walkthrough

Documentation-only update to README.md adding an MCP server badge and standardizing apostrophe formatting across bullet points. No functional or logic changes.

Changes

Cohort / File(s) Summary
Documentation badge & formatting
README.md
Added HTML badge snippet linking to MCP server badge; replaced typographic apostrophes with ASCII apostrophes in two bullet points for consistency

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • No logic or behavior changes
  • Documentation and formatting cleanup only

Poem

🐰 A badge gleams bright in the readme's light,
Apostrophes straightened, the formatting's right,
No code was changed, just cosmetic care,
The docs are refreshed with a gentle flair! ✨

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'add MCP server badge' directly and clearly describes the main change in the pull request, which is adding an HTML badge snippet to the README.
Description check ✅ Passed The description is directly related to the changeset, providing context about the Glama MCP server badge being added to the README and mentioning documentation fixes.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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 and usage tips.

@gemini-code-assist
Copy link

Summary of Changes

Hello @punkpeye, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily enhances the project's documentation by integrating a Glama MCP server badge into the README.md. This addition aims to provide users with a quick and reliable way to assess the Node.js Sandbox MCP Server's safety, capabilities, and usage instructions directly from the repository's main page. Alongside this, minor textual and formatting improvements have been applied to the README file.

Highlights

  • Glama MCP Server Badge: A new badge has been added to the README.md, linking to the Node.js Sandbox MCP Server listing on Glama.ai. This badge provides quick access to server details, safety assessments, and installation instructions.
  • Typographical Correction: A minor correction was made in the README.md, changing 'don’t' to 'don't' for consistency.
  • File Formatting: A trailing newline character was removed from the end of the README.md file.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@punkpeye
Copy link
Author

punkpeye commented Nov 5, 2025

I will follow up with a separate PR to show how to connect to the MCP server.

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey there - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a Glama MCP server badge to the README.md file and fixes a minor typo. My review includes two suggestions for the README.md: one to improve the accessibility of the new badge by making its alt text more descriptive, and another to adhere to the common convention of ending files with a newline character.

![Website Preview](https://raw.githubusercontent.com/alfonsograziano/node-code-sandbox-mcp/master/assets/images/website_homepage.png)

<a href="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox Server MCP server" />

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For improved accessibility, the alt text for the badge image should be more descriptive. The current text, "Node.js Sandbox Server MCP server", is slightly repetitive. I suggest changing it to more clearly state the purpose of the badge.

Suggested change
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox Server MCP server" />
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Status badge for Node.js Sandbox MCP server" />

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

This change removes the final newline character from the file. It is a widely-followed convention to end text files with a single newline character. This practice avoids unexpected behavior with common command-line tools (like cat) and helps version control systems represent file changes more clearly. Please re-add the newline at the end of the file.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3a66861 and bdd33ed.

📒 Files selected for processing (1)
  • README.md (3 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
README.md

297-297: Files should end with a single newline character

(MD047, single-trailing-newline)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Sourcery review
🔇 Additional comments (1)
README.md (1)

269-269: Apostrophe standardization is appropriate.

Using ASCII apostrophes instead of typographic ones ("don't" → "don't") improves consistency and compatibility across markdown renderers and plain-text contexts. Good catch.

Comment on lines +7 to +9
<a href="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox Server MCP server" />
</a>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Minor: Remove redundant "server" in badge alt text.

The alt text "Node.js Sandbox Server MCP server" repeats "server" twice, which is redundant. Simplify to avoid confusion for screen readers.

-  <img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox Server MCP server" />
+  <img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox MCP server badge" />
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
<a href="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox Server MCP server" />
</a>
<a href="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@ssdeanx/node-code-sandbox-mcp/badge" alt="Node.js Sandbox MCP server badge" />
</a>
🤖 Prompt for AI Agents
In README.md around lines 7 to 9, the image badge alt text reads "Node.js
Sandbox Server MCP server" which redundantly repeats "server"; update the img
alt attribute to a concise, non-redundant phrase such as "Node.js Sandbox MCP"
(or "Node.js Sandbox Server MCP" if you want to keep the single word "Server")
to remove the duplicate word and maintain clear, accessible alt text for screen
readers.

FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Add trailing newline to file.

The file should end with a single newline character per markdown best practices (MD047).

 OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

297-297: Files should end with a single newline character

(MD047, single-trailing-newline)

🤖 Prompt for AI Agents
In README.md around line 297, the file is missing a trailing newline; add a
single newline character at the end of the file so it ends with exactly one
newline (per MD047) and ensure no extra blank lines are appended.

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