Repository navigation
docs: add LightNow capability badge - #11
Open
nils-friedrichs wants to merge 1 commit into
Open
nils-friedrichs wants to merge 1 commit into
nils-friedrichs wants to merge 1 commit into
Conversation
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.
I'm the founder of LightNow. The Smithery badge image currently returns HTTP 500. This keeps the Smithery badge and adds a LightNow capability badge alongside it, linking to WickedAPI MCP's existing LightNow listing, where readers can inspect its MCP interface by version and find client setup instructions. This changes only the badge line; the existing Smithery badge and backlinks stay unchanged.
Maintainers can claim the listing to add links and mark older versions as deprecated. Badge variants and fallback behavior.