Hi — I just published a public MCP stdio wrapper for SignalSpore and wanted to ask the recommended path for community visibility in the official MCP ecosystem.
Repo: https://github.com/yeahdog/signalspore-mcp
Release: https://github.com/yeahdog/signalspore-mcp/releases/tag/v0.1.0
Install: npx -y github:yeahdog/signalspore-mcp
Docs: https://www.signalspore.com/mcp
SignalSpore MCP exposes setup, local gate, preflight, and sanitized delta tools for risky-task prevention before shell, migration, deploy, database-reset, and brittle integration work.
Question: should third-party/community servers like this be proposed via PR to modelcontextprotocol/servers, published through the registry flow only, or surfaced somewhere else first? Happy to follow the preferred path.
Hi — I just published a public MCP stdio wrapper for SignalSpore and wanted to ask the recommended path for community visibility in the official MCP ecosystem.
Repo: https://github.com/yeahdog/signalspore-mcp
Release: https://github.com/yeahdog/signalspore-mcp/releases/tag/v0.1.0
Install:
npx -y github:yeahdog/signalspore-mcpDocs: https://www.signalspore.com/mcp
SignalSpore MCP exposes setup, local gate, preflight, and sanitized delta tools for risky-task prevention before shell, migration, deploy, database-reset, and brittle integration work.
Question: should third-party/community servers like this be proposed via PR to modelcontextprotocol/servers, published through the registry flow only, or surfaced somewhere else first? Happy to follow the preferred path.