SurfSense/plugins/registry/check
Anish Sarkar 97faf491e5 fix(plugins): refuse SSE addresses, and never move an SSE plugin behind the user's back
Adding a plugin by an address ending in /sse, as providers' docs still
give theirs, is refused before anything is contacted, and the Add dialog
says so as the user types it, with Add off. An address that is not /sse
but streams SSE is refused as before.

A plugin recorded on SSE by an earlier version is no longer moved to its
server's /mcp at a check: it is never contacted, and its status, in the
list and in its details, says SSE is not supported and how to replace it.

The registry bot names a submitted /sse address as SSE whatever it
answers, since a sign-in there read as a key to take, and gives the /mcp
beside it when MCP answers there. The submit form says Streamable HTTP
only.
2026-10-22 23:20:33 +05:30
..
registry_check fix(plugins): refuse SSE addresses, and never move an SSE plugin behind the user's back 2026-10-22 23:20:33 +05:30
tests fix(plugins): refuse SSE addresses, and never move an SSE plugin behind the user's back 2026-10-22 23:20:33 +05:30
pyproject.toml chore(plugins): plugin host 0.0.1 and registry check 0.0.1 2026-10-14 16:53:32 +05:30
uv.lock chore(plugins): plugin host 0.0.1 and registry check 0.0.1 2026-10-14 16:53:32 +05:30