From ebd9baa0a5791f4bf3755bb552f569145762cb99 Mon Sep 17 00:00:00 2001
From: cdeust <3167767+cdeust@users.noreply.github.com>
Date: Thu, 30 Jul 2026 08:51:00 +0000
Subject: [PATCH 1/2] chore: refresh MCP Toplist rank badge

---
 assets/badge-mcp-toplist.svg | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/assets/badge-mcp-toplist.svg b/assets/badge-mcp-toplist.svg
index 2e5fa042..5fbc6239 100644
--- a/assets/badge-mcp-toplist.svg
+++ b/assets/badge-mcp-toplist.svg
@@ -1,9 +1,9 @@
-<svg xmlns="http://www.w3.org/2000/svg" width="216" height="20" viewBox="0 0 216 20" role="img" aria-label="MCP Toplist: Top 1.2% of 81,919 tracked MCP servers, Jul 2026">
-  <title>MCP Toplist: Top 1.2% of 81,919 tracked MCP servers, Jul 2026</title>
+<svg xmlns="http://www.w3.org/2000/svg" width="216" height="20" viewBox="0 0 216 20" role="img" aria-label="MCP Toplist: Top 1.0% of 94,230 tracked MCP servers, Jul 2026">
+  <title>MCP Toplist: Top 1.0% of 94,230 tracked MCP servers, Jul 2026</title>
   <!-- GENERATED by scripts/refresh_mcp_toplist_badge.py — do not hand-edit.
-       Source: server page reported rank 964 of 81,919
-       tracked MCP servers, read 2026-07-28
-       (964/81919 = 1.18% -> "Top 1.2%").
+       Source: server page reported rank 947 of 94,230
+       tracked MCP servers, read 2026-07-30
+       (947/94230 = 1.00% -> "Top 1.0%").
        Verify: https://mcptoplist.com/server/io.github.cdeust%2Fhypermnesia-mcp
        Upstream's score is a popularity and activity signal, not a quality
        assessment, and ~25% of its weighting is undisclosed — so this badge
@@ -23,7 +23,7 @@
   <g font-family="Verdana,DejaVu Sans,Geneva,sans-serif" font-size="11">
     <text x="54" y="15" fill="#000" fill-opacity="0.25" text-anchor="middle" textLength="64" lengthAdjust="spacingAndGlyphs">MCP Toplist</text>
     <text x="54" y="14" fill="#f8f7f2" text-anchor="middle" textLength="64" lengthAdjust="spacingAndGlyphs">MCP Toplist</text>
-    <text x="154" y="15" fill="#000" fill-opacity="0.25" text-anchor="middle" textLength="110" lengthAdjust="spacingAndGlyphs">Top 1.2% · Jul 2026</text>
-    <text x="154" y="14" fill="#fff" text-anchor="middle" textLength="110" lengthAdjust="spacingAndGlyphs">Top 1.2% · Jul 2026</text>
+    <text x="154" y="15" fill="#000" fill-opacity="0.25" text-anchor="middle" textLength="110" lengthAdjust="spacingAndGlyphs">Top 1.0% · Jul 2026</text>
+    <text x="154" y="14" fill="#fff" text-anchor="middle" textLength="110" lengthAdjust="spacingAndGlyphs">Top 1.0% · Jul 2026</text>
   </g>
 </svg>

From d8a099e9a5be0170b983f92341bf310b53a7b2ff Mon Sep 17 00:00:00 2001
From: cdeust <cdeust@icloud.com>
Date: Thu, 30 Jul 2026 13:05:03 +0200
Subject: [PATCH 2/2] chore: trigger CI on this badge-refresh PR

PRs opened with the default GITHUB_TOKEN do not trigger workflows (GitHub's
documented behaviour, and noted in this repo's own CHANGELOG for exactly this
workflow), so #289's required CI checks never started and it sat
MERGEABLE/BLOCKED with only the 4 CodeQL checks reported. An empty commit
pushed from a user credential starts them. #290 fixed the repo setting that
prevents Actions from opening these PRs at all; this unblocks the one already
open.