# MCP Directory Repair Pack

Updated: 2026-05-19T22:24:55.683Z

This is a sales operator artifact. It is not proof of directory approval, ranking, installs, or revenue by itself.

## Objective
Repair MCP directory drift so ThumbGate discovery points to one canonical identity and one proof-backed install path.

## Positioning
- State: directory-repair
- Headline: Fix legacy-name MCP directory drift before scaling discovery.
- Short description: ThumbGate already has live MCP directory discovery, but major surfaces still leak retired names and old repo paths. Repair those first, then scale directory acquisition.
- Summary: Current checks show one canonical listing on MCP.so, one canonical-but-stale Glama listing, one legacy Smithery namespace, one canonical-plus-legacy duplicate on the highest-reach awesome list, and one missing awesome-list entry.

## Canonical Identity
- Display name: ThumbGate
- Repository: https://github.com/IgorGanapolsky/ThumbGate
- npm package: https://www.npmjs.com/package/thumbgate
- Homepage: https://thumbgate.ai
- Commercial truth: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md
- Verification evidence: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
- Support docs: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/mcp-hub-submission.md

## Demand Surfaces
### MCP.so canonical listing
- Role: Live discovery surface with the current ThumbGate slug.
- Public status: Live on the canonical `thumbgate/IgorGanapolsky` path.
- Operator use: Use as the reference listing while repairing drift everywhere else.
- Surface URL: https://mcp.so/server/thumbgate/IgorGanapolsky
- Submission path: https://mcp.so/submit
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/marketing/mcp-directories.md
- Evidence checked: 2026-05-03
- Evidence summary: Direct curl check confirmed the page title `Thumbgate MCP Server`, current ThumbGate overview copy, and the canonical GitHub link.
- Next repair: Keep description and proof links aligned with `COMMERCIAL_TRUTH.md` and `VERIFICATION_EVIDENCE.md` as the canonical directory copy.
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### Glama canonical listing
- Role: High-volume MCP registry surface with a canonical ThumbGate slug but stale legacy metadata.
- Public status: Search for `thumbgate` now resolves to the canonical `IgorGanapolsky/ThumbGate` listing.
- Operator use: Clean up the remaining legacy metadata and FAQ payload before pushing more Glama-facing discovery.
- Surface URL: https://glama.ai/mcp/servers?query=thumbgate
- Submission path: https://glama.ai/mcp/servers/IgorGanapolsky/ThumbGate
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/marketing/mcp-directories.md
- Evidence checked: 2026-05-03
- Evidence summary: Search results now resolve to the ThumbGate slug, but the canonical page still ships legacy schema text about `memory management and gateway capabilities` and an FAQ answer that opens with `The MCP Memory Gateway`.
- Next repair: Update the canonical Glama metadata and FAQ content so the schema description, FAQ answer, and page copy are ThumbGate-only.
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### Smithery search result
- Role: Installer-facing directory surface with a legacy namespace result.
- Public status: Search returns `rlhf-loop/thumbgate` with `0 connections` instead of a canonical ThumbGate namespace.
- Operator use: Publish or repair the canonical Smithery listing before treating Smithery as an active acquisition lane.
- Surface URL: https://smithery.ai/search?q=thumbgate
- Submission path: https://smithery.ai/new
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/marketing/mcp-directories.md
- Evidence checked: 2026-05-03
- Evidence summary: Direct search output shows `thumbgate [remote]`, the legacy `rlhf-loop/thumbgate` namespace, and a details link at the legacy path.
- Next repair: Publish or migrate Smithery metadata to a canonical ThumbGate namespace and retire the legacy `rlhf-loop` ownership path.
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### punkpeye awesome-mcp-servers
- Role: Largest GitHub awesome-list discovery surface in the current repo research.
- Public status: Listed under the canonical ThumbGate repository, but the README still carries a duplicate legacy `IgorGanapolsky/mcp-memory-gateway` entry.
- Operator use: Open a cleanup PR that removes the duplicate legacy entry while preserving the canonical ThumbGate listing.
- Surface URL: https://github.com/punkpeye/awesome-mcp-servers
- Submission path: https://github.com/punkpeye/awesome-mcp-servers/blob/main/README.md
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/marketing/mcp-directories.md
- Evidence checked: 2026-05-03
- Evidence summary: README search now shows both a canonical `IgorGanapolsky/ThumbGate` entry and a second legacy `IgorGanapolsky/mcp-memory-gateway` entry.
- Next repair: Submit a PR removing the duplicate legacy entry so discovery points at one canonical ThumbGate listing.
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

### appcypher awesome-mcp-servers
- Role: Secondary GitHub discovery list that currently has no ThumbGate entry.
- Public status: No ThumbGate entry found in the current README search.
- Operator use: Treat this as a clean add-listing submission, not a rename repair.
- Surface URL: https://github.com/appcypher/awesome-mcp-servers
- Submission path: https://github.com/appcypher/awesome-mcp-servers
- Support: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/marketing/mcp-directories.md
- Evidence checked: 2026-05-03
- Evidence summary: README search returned no `thumbgate` or `IgorGanapolsky` matches, so this surface is still missing entirely.
- Next repair: Open a new listing PR with ThumbGate-only copy and the canonical GitHub repository.
- Proof: https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md

## Follow-On Offers
- Proof-backed setup guide: Discovery CTA
  Buyer: Directory visitors who want a current install and proof surface before anything sales-led.
  CTA: https://thumbgate.ai/guide?utm_source=mcp_directories&utm_medium=directory&utm_campaign=mcp_directory_guide&utm_content=guide&campaign_variant=directory_repair&offer_code=MCP-DIRECTORY_GUIDE&cta_id=mcp_directory_guide&cta_placement=follow_on_offer&surface=mcp_directory_guide
- ThumbGate Pro: $19/mo or $149/yr
  Buyer: Directory visitors who already want the self-serve path and need a tracked paid-intent lane after the guide.
  CTA: https://thumbgate.ai/checkout/pro?utm_source=mcp_directories&utm_medium=directory&utm_campaign=mcp_directory_pro&utm_content=pro&campaign_variant=self_serve_paid_intent&offer_code=MCP-DIRECTORY_PRO&cta_id=mcp_directory_pro&cta_placement=follow_on_offer&plan_id=pro&surface=mcp_directory_pro
- Workflow Hardening Sprint: Primary revenue motion
  Buyer: Teams that already named one repeated workflow failure and want rollout proof, not just a directory listing.
  CTA: https://thumbgate.ai/?utm_source=mcp_directories&utm_medium=directory&utm_campaign=mcp_directory_sprint&utm_content=workflow_sprint&campaign_variant=repair_to_team_motion&offer_code=MCP-DIRECTORY_SPRINT&cta_id=mcp_directory_sprint&cta_placement=follow_on_offer&surface=mcp_directory_sprint#workflow-sprint-intake

## Operator Queue
### Glama listing owner or claimant
- Evidence: Glama search now resolves to `IgorGanapolsky/ThumbGate`, but the canonical page still carries legacy schema text about `memory management and gateway capabilities` and an FAQ answer that begins with `The MCP Memory Gateway`.
- Proof trigger: Do this before sending more discovery traffic into Glama because the canonical listing still carries legacy metadata and FAQ copy.
- Proof asset: https://glama.ai/mcp/servers/IgorGanapolsky/ThumbGate
- Next ask: https://glama.ai/mcp/servers/IgorGanapolsky/ThumbGate
- Recommended motion: Edit the canonical Glama listing so the schema description, FAQ answer, and repo-facing copy are ThumbGate-only.

### Smithery publisher or maintainer
- Evidence: Smithery search returns the legacy `rlhf-loop/thumbgate` namespace with no canonical ThumbGate ownership path.
- Proof trigger: Fix before treating Smithery as a live install lane because the namespace itself is still legacy.
- Proof asset: https://smithery.ai/search?q=thumbgate
- Next ask: https://smithery.ai/servers/rlhf-loop/thumbgate
- Recommended motion: Publish or migrate Smithery to a canonical ThumbGate namespace and retire `rlhf-loop`.

### GitHub awesome-list maintainer or contributor
- Evidence: The most visible awesome list now carries the canonical `IgorGanapolsky/ThumbGate` entry plus a second legacy `IgorGanapolsky/mcp-memory-gateway` duplicate.
- Proof trigger: Repair before doing net-new list work because discovery should not split across both a canonical and legacy entry.
- Proof asset: https://github.com/punkpeye/awesome-mcp-servers
- Next ask: https://github.com/punkpeye/awesome-mcp-servers/pulls
- Recommended motion: Open a small README PR that deletes the duplicate legacy entry and preserves the canonical ThumbGate listing.

### GitHub awesome-list maintainer or contributor
- Evidence: No current ThumbGate entry exists in the appcypher list, so this is clean acquisition expansion instead of repair.
- Proof trigger: Only pursue after the legacy-name repairs are underway so new discovery traffic sees one canonical identity.
- Proof asset: https://github.com/appcypher/awesome-mcp-servers
- Next ask: https://github.com/appcypher/awesome-mcp-servers/pulls
- Recommended motion: Open a new listing PR with ThumbGate-only copy, the npm package, and the canonical GitHub repository.

### Directory maintenance owner
- Evidence: MCP.so already exposes the correct ThumbGate slug and current overview, so it can anchor every other repair.
- Proof trigger: Use as the backstop whenever a directory repair needs a live canonical listing reference.
- Proof asset: https://mcp.so/server/thumbgate/IgorGanapolsky
- Next ask: https://mcp.so/server/thumbgate/IgorGanapolsky
- Recommended motion: Preserve this listing as the canonical reference and mirror its ThumbGate-only naming everywhere else.

## Outreach Drafts
### Glama claim or support request — Glama listing maintainer
ThumbGate now resolves to the canonical Glama listing, but the page still carries legacy metadata: the schema description still says `memory management and gateway capabilities`, and the FAQ answer still opens with `The MCP Memory Gateway`. Please refresh that metadata and FAQ copy so the canonical listing is ThumbGate-only.

### Smithery publish note — Smithery publisher
The current Smithery search result for `thumbgate` resolves to the legacy `rlhf-loop/thumbgate` namespace. The active package and repository are `thumbgate` and `IgorGanapolsky/ThumbGate`. Publish or migrate the listing under the canonical ThumbGate namespace before treating Smithery as a live acquisition lane.

### punkpeye README PR body — awesome-mcp-servers maintainer
This PR removes the duplicate legacy `IgorGanapolsky/mcp-memory-gateway` entry and keeps the canonical `IgorGanapolsky/ThumbGate` listing in place. The description remains focused on ThumbGate as pre-action gates that prevent AI coding agents from repeating known mistakes.

### appcypher README PR body — awesome-mcp-servers maintainer
This PR adds ThumbGate to the list using the canonical repository and current product language. ThumbGate is the pre-action gates layer for AI coding agents: it captures explicit feedback, turns repeated failures into prevention rules, and blocks repeat mistakes before risky actions run again.

## 90-Day Measurement Plan
- North star: directory_referral_to_paid_intent
- Policy: Treat directory presence as acquisition evidence only after a tracked guide click, install-surface click, or qualified workflow conversation exists.
- Minimum useful signal: One tracked setup-guide visit or workflow-sprint conversation sourced from a repaired directory surface.
- Strong signal: Three tracked paid-intent events sourced from repaired directory referrals across guide, Pro, or sprint lanes.
Tracked metrics:
- directory_referral_clicks
- guide_visits_from_directories
- codex_plugin_page_visits_from_directories
- workflow_sprint_intake_submissions_from_directories
- pro_checkout_starts_from_directories
Guardrails:
- Do not claim directory approval, ranking, installs, or revenue without direct command evidence.
- Do not ship new directory copy that mentions `mcp-memory-gateway`, `rlhf-loop`, or other retired product names as active surfaces.
- Keep pricing aligned with COMMERCIAL_TRUTH.md.
- Keep proof claims aligned with VERIFICATION_EVIDENCE.md.
Milestones:
- days_0_30: Refresh Glama metadata, repair Smithery namespace drift, and remove the punkpeye legacy duplicate before broadening directory distribution. Decision rule: Do not add lower-priority directories until the visible legacy-name leaks and duplicate entries are fixed or actively queued.
- days_31_60: Measure whether repaired directory referrals produce guide clicks or qualified workflow conversations. Decision rule: If referral clicks exist without paid intent, move proof and install CTAs higher on the linked destination pages.
- days_61_90: Prune low-signal directories and keep only the surfaces that produce tracked downstream intent. Decision rule: If a directory does not create tracked guide clicks or workflow conversations, stop treating it as an active acquisition lane.
Do not count as success:
- directory pages that still use legacy names
- directory visibility without a tracked downstream click
- unverified claims about official registry presence, approval, or paid traffic

## Proof Links
- https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/COMMERCIAL_TRUTH.md
- https://github.com/IgorGanapolsky/ThumbGate/blob/main/docs/VERIFICATION_EVIDENCE.md
