[Critical Bug] Tool cache stuck at Namespace level — synapselayer shows stale data

[SynapseLayer]

What actually happened?

Description

Our MCP server namespace synapselayer is stuck with a stale tool snapshot from an initial deployment. Despite multiple re-publishes, new slugs, and even new upstream URLs, the public registry page continues to show only 5 outdated tools with deprecated descriptions.

Evidence of Persistence

We confirmed the cache is Namespace-level:

1. Slug: synapselayer/synapse-protocol (Original) -> 5 stale tools ❌
2. Slug: synapselayer/synapse-layer (New URL: /api/mcp-v2) -> SAME 5 stale tools ❌

Live Forge Endpoint: https://forge.synapselayer.org/api/mcp

• Live status: Returns 13 tools via tools/list with clean descriptions.
• The registry still displays "PII redaction" and "Trust Quotient", terms which were removed from our live Forge and pose a reputational risk.

Terminal Outputs

npx @smithery/cli mcp publish returns SUCCESS, but the registry UI never re-scans the upstream tools. PATCH/PUT to registry API accepted but not persisted.

What's the expected behavior?

The registry should invalidate the tool/metadata cache upon a new successful release or when a new slug is created with a different upstream URL. We expect the registry to display all 13 tools currently provided by our Forge endpoint and reflect the updated descriptions.

Requested Action: Please manually purge the cache for the synapselayer namespace.

Relevant terminal/log output

Steps to reproduce

No response

Additional information (Optional)

No response