docs: add the Glama server score badge to the README - #36
Merged
Conversation
The listing at glama.ai/mcp/servers/whats2000/isaacsim-mcp-server is already claimed under the personal account, and it publishes a maintenance/quality score (license A, quality A, maintenance A) that the badge tracks live. It sits alongside the existing Archestra quality badge. No glama.json accompanies this: Glama only requires that file to claim an org-hosted repo, and its schema carries nothing but a `maintainers` list. Co-Authored-By: Claude Opus 5 (1M context) <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 does this PR do?
Adds the Glama score badge to the README badge row, next to the existing Archestra quality badge.
The listing at glama.ai/mcp/servers/whats2000/isaacsim-mcp-server is already claimed under the personal account and publishes a live maintenance/quality score (license A, quality A, maintenance A), so the badge tracks that rather than being a static shield.
No
glama.jsonaccompanies this. Glama only requires that file to claim an org-hosted repo — a personal repo is claimed by GitHub auth alone — and its schema defines exactly one property,maintainers. It would be inert here. If the repo ever moves to an org, or a second maintainer needs Glama dashboard access, that is the moment to add it.One line changed in
README.md. NoCHANGELOG.mdentry: a README badge is not user-facing behavior in the sense that file tracks.Tested Isaac Sim Version(s)
Not applicable — docs-only, no code path touched, so nothing was run in a live simulator.
isaac-sim.sh)isaac-sim.newton.sh)Before submitting
ruff check . && ruff format .)? — no.pyfiles touchedWho can review?
@whats2000
🤖 Generated with Claude Code