Notion

The materials state that no keys or environment variables are required, and there is no explicit request for additional sensitive secrets; however, as a Notion integration, deployment should still verify whether workspace access tokens are granted via host-side OAuth or another mechanism.

The stated functions—querying databases, creating pages, and managing Notion content—imply that related data and actions are sent to Notion's service; the materials do not list a specific remote host, so the egress destination is incompletely documented and should be verified before use.

The system checks indicate that this tool executes code, meaning it runs a local MCP service process; this is standard behavior for MCP tools, and the materials do not show requests for unusual system privileges or actions unrelated to its stated purpose.

Its access scope appears centered on Notion content itself, including database queries, page creation, and content management; this is consistent with its stated function, and the materials do not indicate extra access to the local filesystem or unrelated resources.

The source is platform-curated and points to Notion's official open-source repository, with auditable source code and about 4.4k stars in community adoption, which materially lowers supply-chain risk; the remaining gaps are that the license and maintenance status are not explicit in the materials.