Notion documents 11 more tools under Custom Agent sessions, listed when the
connection may view sessions and interact with agents. The entry now names
all 39 tools Notion documents as listed.
DeepWiki is verified by the maintainers. Notion's hosted MCP server is
listed as a community plugin that signs in with OAuth on mcp.notion.com,
with the 28 tools Notion documents and its mark as the icon.
The entry was verified with no domain, so registry_check static failed, which
broke the registry's pull request check and stopped the sign job before it
signed. No ownership proof exists: the MCP Registry holds no DeepWiki listing
and Cognition publishes no SurfSense file or DNS record, so the registry's rule
makes it Community.
A registry entry now says whether SurfSense proved its author runs the server
(a .well-known file, a DNS TXT record or the MCP Registry namespace), in place
of the stored publisher. A checkmark or a Community badge sits by its name with
a tooltip, and connecting a Community plugin first asks. Its page gains About,
Tools, Added and a Publisher row; the publisher column and its compatibility
paths are gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`about` is required in both lists beside `description`: the card shows
the one, the public page the other, and the page never falls back to the
card's line. Every first-party plugin and DeepWiki has one, written as
what it lets you do and who it is useful for.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Each plugin in Browse opens one shared public page, built from its list
entry and the same whether it is connected or not: its publisher, about,
listed tools as chips, authentication, the hosts it connects to, the
month it was added, and its homepage and privacy policy. Yours keeps a
connected plugin's settings and live tools alone.
Entries gain `about`, `tools` and `added`, required in both lists and
checked in review for the registry; the first-party list's tools are
checked against each server by the plugin host's tests. One Connect
serves every listed plugin. Browse lists them in two columns.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
plugins/registry/ holds the list publishers add to by pull request, starting
with DeepWiki, and its icons. registry_check checks every entry and icon rule;
on dev, CI signs the list with Ed25519 into published/, which the release pull
request carries to main, so nothing pushes to main and the source list is
never rewritten. A small Caddy container serves the signed list, its icons and
SurfSense's OAuth client document and callback page on plugins.surfsense.com,
apart from the plugin host so a listing never restarts the scrapers. CI does
not contact listed servers: most need a sign-in, so a maintainer connects each
listing on dev. plugins/README.md is the guide for publishers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>