Hi Flamecast team 👋 — we're Mnemoverse (an MCP memory server). flamecast.com auto-listed our server from Smithery ("Add Mcp Memory to your Telegram"), and we hit a few snags trying the install. Sharing as friendly alpha feedback — no urgency, our server + Smithery listing are fine. (If the flamecast.com web app lives in a different repo, please route this there — this looked like the most relevant public Flamecast repo.)
1. /install/telegram returns HTTP 404.
https://flamecast.com/install/telegram?mcp=https://server.smithery.ai/mnemoverse/mcp-memory-server&go=1 → 404 (the page itself). So the "Continue to Telegram" install flow dead-ends.
2. Gateway connect 401s for OAuth-gated servers (no OAuth flow).
Past the 404, the install targets the Smithery gateway https://server.smithery.ai/mnemoverse/mcp-memory-server, which correctly returns 401 — our server is OAuth-gated (OAuth 2.1 + PKCE, per-user isolation; it emits a 401 with WWW-Authenticate: Bearer resource_metadata=... per RFC 9728). It looks like the install doesn't run the OAuth handshake, so it can't connect. Suggestion: on a 401 with resource_metadata, run the OAuth flow (or surface "this server needs sign-in" rather than a hard failure).
3. Display name is taken from the slug, not the Smithery displayName.
The listing shows "Mcp Memory" (from the slug mcp-memory-server) instead of our Smithery displayName "Mnemoverse Memory". Reading displayName would render the intended name.
Thanks for building this — happy to help test the OAuth-connector path. — Mnemoverse (https://mnemoverse.com)
Hi Flamecast team 👋 — we're Mnemoverse (an MCP memory server). flamecast.com auto-listed our server from Smithery ("Add Mcp Memory to your Telegram"), and we hit a few snags trying the install. Sharing as friendly alpha feedback — no urgency, our server + Smithery listing are fine. (If the flamecast.com web app lives in a different repo, please route this there — this looked like the most relevant public Flamecast repo.)
1.
/install/telegramreturns HTTP 404.https://flamecast.com/install/telegram?mcp=https://server.smithery.ai/mnemoverse/mcp-memory-server&go=1→ 404 (the page itself). So the "Continue to Telegram" install flow dead-ends.2. Gateway connect 401s for OAuth-gated servers (no OAuth flow).
Past the 404, the install targets the Smithery gateway
https://server.smithery.ai/mnemoverse/mcp-memory-server, which correctly returns 401 — our server is OAuth-gated (OAuth 2.1 + PKCE, per-user isolation; it emits a401withWWW-Authenticate: Bearer resource_metadata=...per RFC 9728). It looks like the install doesn't run the OAuth handshake, so it can't connect. Suggestion: on a401withresource_metadata, run the OAuth flow (or surface "this server needs sign-in" rather than a hard failure).3. Display name is taken from the slug, not the Smithery displayName.
The listing shows "Mcp Memory" (from the slug
mcp-memory-server) instead of our Smithery displayName "Mnemoverse Memory". ReadingdisplayNamewould render the intended name.Thanks for building this — happy to help test the OAuth-connector path. — Mnemoverse (https://mnemoverse.com)