🧪 Testing Bounty: PR #1861 - MCP Trust Score

[github-actions[bot]]

🧪 Testing Bounty for PR #1861

/bounty 20

overview

this is a testing bounty for PR #1861: MCP Trust Score by @Matvey-Kuk. we're looking for thorough testing across different environments to ensure the changes work as expected.

important links

• testing guide
• pull request #1861

testing instructions

please follow our testing guide and focus on the areas affected by this PR.

how to participate

1. comment on this issue to claim the bounty
2. test the changes following our testing guide
3. report your results in this issue
4. each valid test report will receive a $20 bounty (multiple testers welcome!)

testing requirements

please include the following in your test report:

• [ ] your testing environment details (os, hardware, etc.)
• [ ] steps you followed for testing
• [ ] results of each test with screenshots/recordings
• [ ] any issues encountered
• [ ] system logs if relevant

submission format

environment details

os: 
version: 
cpu: 
ram: 
other relevant details:

test results checklist

• [ ] installation successful
• [ ] permissions granted correctly
• [ ] recording status works
• [ ] screen capture functions correctly
• [ ] audio capture functions correctly
• [ ] performance within expected parameters

evidence

please attach:

• screen recordings of your testing process
• screenshots of important behavior
• logs if there were issues (from ~/.screenpipe or equivalent)

bounty rules

• multiple testers can receive the bounty ($20 each)
• testing should be thorough and follow the guide
• bounties will be paid through algora
• test reports must be submitted within 7 days of this issue

thank you for helping make screenpipe better!

[yashyogeshkathane]

Hi, I’ve successfully built the app from scratch and reviewed the testing guide. However, I’m not sure what exactly needs to be tested for PR #1861 (MCP Trust Score).

From my understanding, this PR only modifies the README.md by adding the Trust Score badge. If that’s the case, should testing just verify that:

the badge appears correctly in the README,

the link behind the badge opens properly (to the evaluation script and catalog page),

and the formatting isn’t broken in light/dark modes?

Or is there any in-app location (such as Help/About/Docs screens) where the README content is rendered and the badge would also need to be checked inside the app itself?

I want to make sure I’m testing the right thing before proceeding with the full checklist. Could you clarify whether the testing scope here is just the README/badge, or if there are app UI areas affected as well?

Thanks!

[rakesh0x]

hey will you pls stop spamming your repo with these shitty testing bounty programs