Add MseeP.ai badge

[lwsinclair]

Hi there,

This pull request shares a security update on perfetto-mcp.

We also have an entry for perfetto-mcp 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 perfetto-mcp.

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

Yours Sincerely,

Lawrence W. Sinclair
CEO/SkyDeck AI
Founder of MseeP.ai
MCP servers you can trust

---

Here are our latest evaluation results of perfetto-mcp

Security Scan Results

Security Score: 100/100

Risk Level: low

Scan Date: 2025-09-18

Score starts at 100, deducts points for security issues, and adds points for security best practices

This security assessment was conducted by MseeP.ai, an independent security validation service for MCP servers. Visit our website to learn more about our security reviews.

Summary by CodeRabbit

• Documentation
  • Added a clickable MseeP.ai Security Assessment Badge at the top of the project README to highlight current security status and provide quick access to assessment details.
  • Improves visibility, trust, and branding without altering functionality or user workflows.
  • No changes to APIs, configuration, or behavior; all existing content remains unchanged.

[coderabbitai]

Walkthrough

Adds a clickable MseeP.ai Security Assessment Badge at the top of README.md above the main heading. No code or functional changes.

Changes

Cohort / File(s)	Summary of Changes
Docs: README badge README.md	Inserted a linked security assessment badge image at the very top, with a blank line before the existing "# Perfetto MCP" heading. No other content modified.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A badge hops in, a shiny new seal,
Atop the README, crisp and real.
I twitch my ears—no code to tweak,
Just branding flair, sleek and chic.
Thump-thump! Approvals near,
Carrots up—security’s here! 🥕✅

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The PR title "Add MseeP.ai badge" is concise, a single sentence, and directly describes the primary change (inserting the MseeP.ai security badge into README.md), so it accurately summarizes the main intent of the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

README.md (3)

1-2: Confirm third‑party endorsement and make date explicit.

Adding a vendor badge can imply endorsement. Please confirm you want to advertise MseeP.ai in the README and consider adding a brief note with the scan date so readers don’t mistake point‑in‑time results for a guarantee.

Proposed addition immediately under the badge:

 [![MseeP.ai Security Assessment Badge](https://mseep.net/pr/antarikshc-perfetto-mcp-badge.png)](https://mseep.ai/app/antarikshc-perfetto-mcp)
+
+_Security score reported by MseeP.ai as of 2025-09-18; follow the badge for the latest status._

---

1-2: Place badges under the H1 for consistency.

Most repos keep badges below the title to preserve a clean top anchor. Optional, but improves readability.

-[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/antarikshc-perfetto-mcp-badge.png)](https://mseep.ai/app/antarikshc-perfetto-mcp)
-
-# Perfetto MCP
+# Perfetto MCP
+
+[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/antarikshc-perfetto-mcp-badge.png)](https://mseep.ai/app/antarikshc-perfetto-mcp)

---

1-2: External asset/link hygiene.

Minor: verify that mseep.net (image) is stable and intended; if possible, prefer the same apex domain as the link (mseep.ai) for simpler governance. Alt text is fine.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ac9cb06 and c43d2b0.

📒 Files selected for processing (1)

• README.md (1 hunks)