Add MseeP.ai badge

[mseep-ai]

Hi there,

This pull request shares a security update on content-core.

We also have an entry for content-core 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 content-core.

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

Thanks,

The MseeP Team
MCP servers you can trust

---

[cubic-dev-ai]

1 issue found across 1 file

Confidence score: 5/5

• README.md has a minor formatting inconsistency: placing a badge before the # Content Core heading breaks the repo’s documented badge/H1 pattern, which can make the docs feel less polished but won’t affect runtime behavior. This PR is safe to merge, and you can de-risk follow-up churn by moving the badge block below the H1 before merging.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="README.md">

<violation number="1" location="README.md:1">
P3: Badge placed before the `# Content Core` heading, breaking the README's existing convention where all badges are grouped after the H1. Move it after the heading to keep the document structure consistent and avoid visual disruption for readers scanning the heading hierarchy.</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: Badge placed before the # Content Core heading, breaking the README's existing convention where all badges are grouped after the H1. Move it after the heading to keep the document structure consistent and avoid visual disruption for readers scanning the heading hierarchy.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 1:

<comment>Badge placed before the `# Content Core` heading, breaking the README's existing convention where all badges are grouped after the H1. Move it after the heading to keep the document structure consistent and avoid visual disruption for readers scanning the heading hierarchy.</comment>

<file context>
@@ -1,3 +1,5 @@
+[![MseeP.ai Security Assessment Badge](https://mseep.net/pr/lfnovo-content-core-badge.png)](https://mseep.ai/app/lfnovo-content-core)
+
 # Content Core
</file context>