Add MseeP.ai badge

[mseep-ai]

Hi there,

This pull request shares a security update on harnss.

We also have an entry for harnss in our directory, MseeP.ai, where we provide regular security and trust updates on your app.

We invite you to add our badge for your MCP server to your README to help your users learn from a third party that provides ongoing validation of harnss.

You can easily take control over your listing for free: visit it at https://mseep.ai/app/opensource03-harnss.

Thanks,

The MseeP Team
MCP servers you can trust

---

Summary by CodeRabbit

• Documentation
  • Added a security assessment badge to the README for enhanced transparency.

[coderabbitai]

📝 Walkthrough

Walkthrough

The README.md file is updated with a new security assessment badge image linking to MseeP.ai and a blank line inserted before an existing warning notice, comprising two added lines with no removals.

Changes

Cohort / File(s)	Summary
Documentation Update README.md	Added MseeP.ai security assessment badge and inserted blank line before existing warning notice for improved formatting and security visibility.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A badge of trust now shines so bright,
Security stamped, all is right,
A line of space, so clean and clear,
README blooms—the path is here! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description lacks the required template structure with missing critical sections: Summary, Type of Change, Related Issues, How to Test, and Checklist.	Follow the repository's PR template by providing a concise summary in bullet points, selecting relevant change type(s), linking related issues, and completing the provided checklist items.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'Add MseeP.ai badge' accurately summarizes the main change: adding a security badge to the README file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Warning

⚠️ This pull request might be slop. It has been flagged by CodeRabbit slop detection and should be reviewed carefully.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@README.md`:
- Line 1: The badge link (the Markdown line containing the "MseeP.ai Security
Assessment Badge" image and the URL https://mseep.ai/app/opensource03-harnss)
currently points to a page that lacks documented audit scope and methodology;
update the target to a page or file that clearly documents the audit scope,
methodology, findings, assessor identity, and report date (e.g., create
SECURITY_AUDIT.md or an external audit URL) and change the badge link to that
URL so users clicking the badge reach transparent audit documentation.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: fc957995-ed75-412f-8ec6-35672890759a

📥 Commits

Reviewing files that changed from the base of the PR and between 06b4d1a and 4e6b229.

📒 Files selected for processing (1)

• README.md

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

URL_PAGE="https://mseep.ai/app/opensource03-harnss"
URL_BADGE="https://mseep.net/pr/opensource03-harnss-badge.png"

echo "== HTTP headers =="
for u in "$URL_PAGE" "$URL_BADGE"; do
  echo "--- $u ---"
  curl -sSI "$u" | sed -n '1,15p'
done

echo
echo "== Check listing page for audit transparency signals =="
curl -sL "$URL_PAGE" | rg -ni "methodology|criteria|scope|report|audit|last updated|evidence" -C2 || true

Repository: OpenSource03/harnss

Length of output: 11200

---

Ensure the security badge links to documentation with clear audit scope and methodology.

The badge image is accessible, but verification shows the linked page does not contain documented audit methodology, scope, or report details. Users clicking this badge should find transparent documentation of what was audited, how, and by whom—otherwise it risks misleading them about your actual security assurance level.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@README.md` at line 1, The badge link (the Markdown line containing the
"MseeP.ai Security Assessment Badge" image and the URL
https://mseep.ai/app/opensource03-harnss) currently points to a page that lacks
documented audit scope and methodology; update the target to a page or file that
clearly documents the audit scope, methodology, findings, assessor identity, and
report date (e.g., create SECURITY_AUDIT.md or an external audit URL) and change
the badge link to that URL so users clicking the badge reach transparent audit
documentation.