Open
Conversation
Reviewer's GuideThis PR integrates the new Trust Score badge into the project’s README to surface transparent quality metrics, while also regenerating the dependency lockfile and introducing a set of duplicated documentation and configuration artifacts (suffixed with “2”) likely stemming from an automated file generation process. Flow diagram for Trust Score badge rendering and navigationflowchart TD
A[User opens README.md]
B[Trust Score badge loads from MCP Catalog API]
C[User clicks badge]
D[User navigates to MCP Catalog project page]
A --> B
B --> C
C --> D
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey there - I've reviewed your changes - here's some feedback:
Blocking issues:
- Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource. (link)
General comments:
- This PR includes hundreds of unrelated files (lockfile, docs, changelogs) that obscure the small badge change—please trim the diff to only the README badge insertion.
- The badge URL uses uppercase “VeriTeknik” which may not match your catalog slug; ensure the casing matches the actual identifier (usually all lowercase) to avoid broken links.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- This PR includes hundreds of unrelated files (lockfile, docs, changelogs) that obscure the small badge change—please trim the diff to only the README badge insertion.
- The badge URL uses uppercase “VeriTeknik” which may not match your catalog slug; ensure the casing matches the actual identifier (usually all lowercase) to avoid broken links.
## Security Issues
### Issue 1
<location> `README 2.md:330` </location>
<issue_to_address>
**security (curl-auth-header):** Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
*Source: gitleaks*
</issue_to_address>Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
README 2.md
Outdated
Comment on lines
+330
to
+331
| curl -X POST http://localhost:12006/mcp \ | ||
| -H "Authorization: Bearer YOUR_API_KEY" \ |
There was a problem hiding this comment.
security (curl-auth-header): Discovered a potential authorization token provided in a curl command header, which could compromise the curl accessed resource.
Source: gitleaks
|
Hey @Matvey-Kuk Congrats on your seed round. Hope you succeed. Best, |
Cleaned up files with ' 2' suffix that were accidentally added
Author
|
@ckaraca thank you, and apologies! Fixed the PR. |
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
2 participants
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.
Hi!
This PR adds the "Trust Score" badge from our new Open Source MCP catalog.
Our catalog evaluates MCP servers based on technical quality—like protocol feature implementation and dependency health—rather than vanity metrics like GitHub stars.
The scoring process is fully transparent and reproducible:
The badge is designed to be respectful to the structure of your readme, example:
Projects like Grafana MCP (https://github.com/grafana/mcp-grafana) are already participating.
We believe that transparent and truly open source MCP catalog should help the community to identify great MCP servers like yours 😊
We'd appreciate your support by merging this PR!
Summary by Sourcery
Add a transparent Trust Score badge to the project README and commit a pnpm lockfile to ensure consistent dependency installs.
New Features:
Enhancements:
Documentation: