-
Notifications
You must be signed in to change notification settings - Fork 77
Open
Description
Summary
I'm trying to publish an MCP server (agora402 - agent trust scoring on Base) and all three publishing methods fail:
1. Web form at smithery.ai/new
- Namespace:
michu5696validates OK (green checkmark) - Server ID:
agora402fails with "Unable to verify server ID. Please try again" (red X) - MCP Server URL:
https://agora402.fly.dev/mcp - Tried multiple alternative server IDs - all fail with the same error
- No requests from Smithery appear in our server logs
2. CLI (smithery mcp publish)
smithery auth loginfails with "Failed to mint token"- Without auth, publish obviously fails too
3. API key from smithery.ai/account/api-keys
smithery auth whoamiworks (recognizes the token)smithery mcp publishwithSMITHERY_API_KEYenv var fails with 401 "Invalid API key or session token"smithery auth token(mint service token) also fails with 401
Server details
- MCP endpoint:
https://agora402.fly.dev/mcp(Streamable HTTP transport, working and tested) - Server card:
https://agora402.fly.dev/.well-known/mcp/server-card.json(serving correctly) - CORS is configured to allow requests from any origin
- The MCP initialize handshake works correctly (tested with curl)
Environment
- @smithery/cli@4.5.0
- macOS
- Node 20
Steps to reproduce
- Go to smithery.ai/new
- Enter namespace: michu5696, server ID: agora402, URL: https://agora402.fly.dev/mcp
- Server ID validation fails immediately
Or via CLI:
npx @smithery/cli@latest auth login # "Failed to mint token"Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels