@zackbart/connecta 0.31.0 → 0.33.0

package/dist/providers/mixpanel/skill.generated.js

@@ -1,9 +1,10 @@
 // Generated by scripts/generate-providers.mjs; do not edit.
 export const skill = {
-    "content": " endpoint. A project created in another residency is not reachable from here at all, so an empty result may mean wrong connector rather than no data.\n\n- Start with `List-Organizations`, then supply the returned organization id where the live `Get-Projects` schema requires it. Resolve the project and workspace, then read `Get-Business-Context` before interpreting events or metrics.\n- Resolve ids before acting; never guess one. `Get-Projects` yields the project id every other call is scoped by, and `List-Dashboards`, `List-Cohorts`, `List-Metrics`, `List-Experiments`, and `List-Feature-Flags` yield the ids their `Get-`, `Update-`, and `Delete-` counterparts expect.\n- Discover names with `Get-Events`, `List-Properties`, and `Get-Property-Values`; do not guess event or property spelling.\n- `Get-Business-Context` requires either `project_id` or `organization_id`. Its schema marks both optional, but the hosted tool rejects a call with neither.\n- `Get-Property-Values` requires `properties` or the deprecated `property` alias. Event property values also require `event`; prefer `properties` and never send both property forms with conflicting values.\n- `List-Properties` accepts `names` or `query`, never both. Use exact `names` for known properties and `query` for substring discovery.\n- One analysis is one `execute_code` program: fetch `Get-Query-Schema` once, run every `Run-Query` of the analysis in that program, and return the reduced table. The schema is tens of kilobytes and the same for every report type, so re-fetching it per query buys nothing. Never return raw `Run-Query` output.\n- Insights, funnels, and retention answer aggregate questions. A per-user ordered event timeline, or a sequence question such as \"event A with no later event B\", is not answerable with `Run-Query` in a reasonable number of calls, and this hosted catalog has no per-`distinct_id` event timeline — `Get-User-Replays-Data` covers one user's replays with their events only where session replay is enabled and present. If the deployment exposes a Mixpanel export or activity-feed connector, use that; if it does not, tell the user the question is out of reach here rather than approximating it with hourly buckets and hundreds of empty rows.\n- `false` on a boolean property may be an absent property: Mixpanel renders a missing value as `false` in boolean breakdowns, and server-imported events often lack client-side properties entirely. Confirm the property is present with `List-Properties` or `Get-Property-Values` before treating `false` as a signal, and say when a conclusion rests on that ambiguity.\n- Breakdown responses nest `$overall` and per-segment series objects. Flatten to one row per complete breakdown combination inside `execute_code` before returning, and drop `$overall` unless the question asks for the total.\n- Use `Get-Report` when the request names an existing saved report. Use `Run-Query` for a new question.\n- Dashboard row and cell ids are opaque. Read the full layout before editing and preserve grouping and order. Report cells need a project-local `query_id`; duplicate within the same project when possible. Cross-project reconstruction needs new queries in the target project.\n- Query ids can expire. Build the dashboard promptly and rerun a query if its id is rejected as expired; no fixed TTL is guaranteed.\n- This account's tool list is not a fixed set. Mixpanel gates parts of its MCP catalog by plan and beta enrollment — experiments, feature flags, session replay, and issue triage are the usual absentees — so search this connector for what it actually exposes rather than assuming a documented tool is here.\n- Mixpanel meters MCP traffic per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Mixpanel authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged. A rejected argument or a plan restriction comes back in Mixpanel's own words instead — read it rather than re-authorizing.\n- Treat every create, update, edit, merge, dismiss, duplicate, or delete operation as a write. For guest calls, classification, and routing, fetch `skills({ name: \"usage\" })`.\n",
+    "content": "\n\n- This connection uses Connecta's REST tools with a service account. Hosted MCP is the default `mixpanel()` mode; `via: \"api\"` explicitly selects REST. Declare two connection ids when both are useful. The operator pastes `username:secret` into the API connection, which sends ordinary HTTP Basic, unlike hosted MCP's `Bearer Basic` scheme. OAuth and static headers are refused in API mode.\n- One connection stays in one residency region, across all projects the account can reach. US uses `mixpanel.com` for query/app, `data.mixpanel.com` for export and `api.mixpanel.com` for ingestion. EU uses `eu.mixpanel.com`, `data-eu.mixpanel.com` and `api-eu.mixpanel.com`. India uses `in.mixpanel.com`, `data-in.mixpanel.com` and `api-in.mixpanel.com`. Wrong residency can look like missing data; do not interpret an empty response without checking the project region.\n- Start with `list_projects`, which returns redacted account metadata from `/api/app/me`. Its public reference does not specify the response schema. Resolve ids from that metadata or project settings, never guess one. Every project-scoped tool accepts `project_id`; an omitted id uses `defaultProjectId` when configured. An explicit id overrides that default and still requires service-account membership. Projects with Data Views may also require `workspace_id`.\n- Use REST for raw event export, profile queries and individual event sequences. Use hosted MCP for schema discovery, business context, aggregate analytics and dashboard work. Discover exact event and property names there before filtering raw data.\n- Export has no documented cursor. Begin with a short date range and an event or `where` filter. Every export returns `truncated` and a notice. A true flag means events may be missing at the byte or event cap; narrow ranges or filters, rather than inferring \"no later event B\" from a sample. Dates are inclusive. Mixpanel documents UTC for newer projects and the project timezone for older projects; check project settings around the January 2023 transition. Event timestamps default to seconds, or milliseconds with `time_in_ms`.\n- `get_profile_activity` sorts a user's returned events by timestamp, but `/stream/query` is in maintenance mode and has no documented pagination/completeness guarantee. For absence or sequence claims use complete, filtered raw export and sort/reduce inside `execute_code`.\n- `query_profiles` is a read-only POST to the Query API's `/engage`, distinct from ingestion `/engage` profile mutations. Pagination is vendor-owned: there is no documented caller `page_size`. Keep the same selector and output properties, pass the returned `session_id`, and increment `page` while `page.hasMore` is true. Do not treat `total` as the page length. `raw: true` preserves the redacted vendor envelope when needed.\n- Saved Insights uses `bookmark_id` from a report URL. Saved Funnels uses `funnel_id`, discoverable with `mixpanel_api_read` on `/api/query/funnels/list`. The documented Retention endpoint takes events and date parameters, not a saved-report id; default/birth retention also requires `born_event`. Use `query_retention` or hosted MCP for an existing saved Retention report. Reduce nested report results before returning them.\n- Retention `interval` is capped at 90 only for `unit: \"day\"`, including the default when unit is omitted. Week and month intervals have no documented 90-unit cap. Both named and generic retention reads enforce the day limit.\n- `mixpanel_api_search` and `mixpanel_api_details` inspect the reviewed operation subset locally. `mixpanel_api_read` permits GET only on those operations, with fixed residency hosts and no caller URL or headers. It cannot reach service-account administration, arbitrary app APIs, profile mutation, JQL or ingestion. Generic export retains the named export's byte/event bounds. Use named tools for Engage and import.\n- `import_events` is an additive write and requires an Owner or Admin service account on the target project. Connecta enforces 2000 events, 10MB per batch, less than 1MB per event and Mixpanel's documented property limits. Supply stable `$insert_id` values and use strict validation. A 400 can still ingest the valid events; never retry a whole batch automatically. Inspect the target and failed records through a trusted operator workflow before deciding what to send again.\n- Profile writes are deferred. The official ingestion `/engage` contract requires `$token` in each update; service-account Basic alone does not satisfy it, and the service-account reference documents no project-token retrieval operation. Profile delete and other irreversible mutations are absent.\n- Query permits 60 queries per hour and 5 concurrent queries per project. Export permits 60 per hour, 3 per second and 100 concurrent queries. Ingestion permits 2GB uncompressed JSON per minute or about 30000 events per second. The API connection conservatively shares a 60-call/hour, 5-concurrent default across all tools and projects; it is a per-runtime approximation, not a distributed quota or a per-second export limiter. Operators may override `callAdmission`, especially for import-heavy deployments or multiple runtimes sharing an account. A vendor 429 still wins; respect `Retry-After`.\n- Successful responses recursively redact credential-named properties and bearer URLs. Arbitrary analytics properties remain user data; do not put secrets into free-text event names or property values. HTTP failures expose status and recovery guidance rather than vendor text that could echo a credential.\n",
     "instructionsHeading": "Account instructions",
     "fragments": {
         "guide_0": " endpoint. A project created in another residency is not reachable from here at all, so an empty result may mean wrong connector rather than no data.",
-        "guide_1": "\n\n- Start with `List-Organizations`, then supply the returned organization id where the live `Get-Projects` schema requires it. Resolve the project and workspace, then read `Get-Business-Context` before interpreting events or metrics.\n- Resolve ids before acting; never guess one. `Get-Projects` yields the project id every other call is scoped by, and `List-Dashboards`, `List-Cohorts`, `List-Metrics`, `List-Experiments`, and `List-Feature-Flags` yield the ids their `Get-`, `Update-`, and `Delete-` counterparts expect.\n- Discover names with `Get-Events`, `List-Properties`, and `Get-Property-Values`; do not guess event or property spelling.\n- `Get-Business-Context` requires either `project_id` or `organization_id`. Its schema marks both optional, but the hosted tool rejects a call with neither.\n- `Get-Property-Values` requires `properties` or the deprecated `property` alias. Event property values also require `event`; prefer `properties` and never send both property forms with conflicting values.\n- `List-Properties` accepts `names` or `query`, never both. Use exact `names` for known properties and `query` for substring discovery.\n- One analysis is one `execute_code` program: fetch `Get-Query-Schema` once, run every `Run-Query` of the analysis in that program, and return the reduced table. The schema is tens of kilobytes and the same for every report type, so re-fetching it per query buys nothing. Never return raw `Run-Query` output.\n- Insights, funnels, and retention answer aggregate questions. A per-user ordered event timeline, or a sequence question such as \"event A with no later event B\", is not answerable with `Run-Query` in a reasonable number of calls, and this hosted catalog has no per-`distinct_id` event timeline — `Get-User-Replays-Data` covers one user's replays with their events only where session replay is enabled and present. If the deployment exposes a Mixpanel export or activity-feed connector, use that; if it does not, tell the user the question is out of reach here rather than approximating it with hourly buckets and hundreds of empty rows.\n- `false` on a boolean property may be an absent property: Mixpanel renders a missing value as `false` in boolean breakdowns, and server-imported events often lack client-side properties entirely. Confirm the property is present with `List-Properties` or `Get-Property-Values` before treating `false` as a signal, and say when a conclusion rests on that ambiguity.\n- Breakdown responses nest `$overall` and per-segment series objects. Flatten to one row per complete breakdown combination inside `execute_code` before returning, and drop `$overall` unless the question asks for the total.\n- Use `Get-Report` when the request names an existing saved report. Use `Run-Query` for a new question.\n- Dashboard row and cell ids are opaque. Read the full layout before editing and preserve grouping and order. Report cells need a project-local `query_id`; duplicate within the same project when possible. Cross-project reconstruction needs new queries in the target project.\n- Query ids can expire. Build the dashboard promptly and rerun a query if its id is rejected as expired; no fixed TTL is guaranteed.\n- This account's tool list is not a fixed set. Mixpanel gates parts of its MCP catalog by plan and beta enrollment — experiments, feature flags, session replay, and issue triage are the usual absentees — so search this connector for what it actually exposes rather than assuming a documented tool is here.\n- Mixpanel meters MCP traffic per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Mixpanel authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged. A rejected argument or a plan restriction comes back in Mixpanel's own words instead — read it rather than re-authorizing.\n- Treat every create, update, edit, merge, dismiss, duplicate, or delete operation as a write. For guest calls, classification, and routing, fetch `skills({ name: \"usage\" })`.\n"
+        "guide_1": "\n\n- Start with `List-Organizations`, then supply the returned organization id where the live `Get-Projects` schema requires it. Resolve the project and workspace, then read `Get-Business-Context` before interpreting events or metrics.\n- Resolve ids before acting; never guess one. `Get-Projects` yields the project id every other call is scoped by, and `List-Dashboards`, `List-Cohorts`, `List-Metrics`, `List-Experiments`, and `List-Feature-Flags` yield the ids their `Get-`, `Update-`, and `Delete-` counterparts expect.\n- Discover names with `Get-Events`, `List-Properties`, and `Get-Property-Values`; do not guess event or property spelling.\n- `Get-Business-Context` requires either `project_id` or `organization_id`. Its schema marks both optional, but the hosted tool rejects a call with neither.\n- `Get-Property-Values` requires `properties` or the deprecated `property` alias. Event property values also require `event`; prefer `properties` and never send both property forms with conflicting values.\n- `List-Properties` accepts `names` or `query`, never both. Use exact `names` for known properties and `query` for substring discovery.\n- One analysis is one `execute_code` program: fetch `Get-Query-Schema` once, run every `Run-Query` of the analysis in that program, and return the reduced table. The schema is tens of kilobytes and the same for every report type, so re-fetching it per query buys nothing. Never return raw `Run-Query` output.\n- Insights, funnels, and retention answer aggregate questions. A per-user ordered event timeline, or a sequence question such as \"event A with no later event B\", is not answerable with `Run-Query` in a reasonable number of calls, and this hosted catalog has no per-`distinct_id` event timeline — `Get-User-Replays-Data` covers one user's replays with their events only where session replay is enabled and present. If the deployment exposes a Mixpanel export or activity-feed connector, use that; if it does not, tell the user the question is out of reach here rather than approximating it with hourly buckets and hundreds of empty rows.\n- `false` on a boolean property may be an absent property: Mixpanel renders a missing value as `false` in boolean breakdowns, and server-imported events often lack client-side properties entirely. Confirm the property is present with `List-Properties` or `Get-Property-Values` before treating `false` as a signal, and say when a conclusion rests on that ambiguity.\n- Breakdown responses nest `$overall` and per-segment series objects. Flatten to one row per complete breakdown combination inside `execute_code` before returning, and drop `$overall` unless the question asks for the total.\n- Use `Get-Report` when the request names an existing saved report. Use `Run-Query` for a new question.\n- Dashboard row and cell ids are opaque. Read the full layout before editing and preserve grouping and order. Report cells need a project-local `query_id`; duplicate within the same project when possible. Cross-project reconstruction needs new queries in the target project.\n- Query ids can expire. Build the dashboard promptly and rerun a query if its id is rejected as expired; no fixed TTL is guaranteed.\n- This account's tool list is not a fixed set. Mixpanel gates parts of its MCP catalog by plan and beta enrollment — experiments, feature flags, session replay, and issue triage are the usual absentees — so search this connector for what it actually exposes rather than assuming a documented tool is here.\n- Mixpanel meters MCP traffic per user per hour, shared with everything else that credential does. Reuse discovery results within a run and avoid speculative fan-out.\n- An `auth_required` failure means this connector's Mixpanel authorization is missing or expired: run `authorize_connector` for this connector id, then retry the same call unchanged. A rejected argument or a plan restriction comes back in Mixpanel's own words instead — read it rather than re-authorizing.\n- Treat every create, update, edit, merge, dismiss, duplicate, or delete operation as a write. For guest calls, classification, and routing, fetch `skills({ name: \"usage\" })`.\n",
+        "api": "\n\n- This connection uses Connecta's REST tools with a service account. Hosted MCP is the default `mixpanel()` mode; `via: \"api\"` explicitly selects REST. Declare two connection ids when both are useful. The operator pastes `username:secret` into the API connection, which sends ordinary HTTP Basic, unlike hosted MCP's `Bearer Basic` scheme. OAuth and static headers are refused in API mode.\n- One connection stays in one residency region, across all projects the account can reach. US uses `mixpanel.com` for query/app, `data.mixpanel.com` for export and `api.mixpanel.com` for ingestion. EU uses `eu.mixpanel.com`, `data-eu.mixpanel.com` and `api-eu.mixpanel.com`. India uses `in.mixpanel.com`, `data-in.mixpanel.com` and `api-in.mixpanel.com`. Wrong residency can look like missing data; do not interpret an empty response without checking the project region.\n- Start with `list_projects`, which returns redacted account metadata from `/api/app/me`. Its public reference does not specify the response schema. Resolve ids from that metadata or project settings, never guess one. Every project-scoped tool accepts `project_id`; an omitted id uses `defaultProjectId` when configured. An explicit id overrides that default and still requires service-account membership. Projects with Data Views may also require `workspace_id`.\n- Use REST for raw event export, profile queries and individual event sequences. Use hosted MCP for schema discovery, business context, aggregate analytics and dashboard work. Discover exact event and property names there before filtering raw data.\n- Export has no documented cursor. Begin with a short date range and an event or `where` filter. Every export returns `truncated` and a notice. A true flag means events may be missing at the byte or event cap; narrow ranges or filters, rather than inferring \"no later event B\" from a sample. Dates are inclusive. Mixpanel documents UTC for newer projects and the project timezone for older projects; check project settings around the January 2023 transition. Event timestamps default to seconds, or milliseconds with `time_in_ms`.\n- `get_profile_activity` sorts a user's returned events by timestamp, but `/stream/query` is in maintenance mode and has no documented pagination/completeness guarantee. For absence or sequence claims use complete, filtered raw export and sort/reduce inside `execute_code`.\n- `query_profiles` is a read-only POST to the Query API's `/engage`, distinct from ingestion `/engage` profile mutations. Pagination is vendor-owned: there is no documented caller `page_size`. Keep the same selector and output properties, pass the returned `session_id`, and increment `page` while `page.hasMore` is true. Do not treat `total` as the page length. `raw: true` preserves the redacted vendor envelope when needed.\n- Saved Insights uses `bookmark_id` from a report URL. Saved Funnels uses `funnel_id`, discoverable with `mixpanel_api_read` on `/api/query/funnels/list`. The documented Retention endpoint takes events and date parameters, not a saved-report id; default/birth retention also requires `born_event`. Use `query_retention` or hosted MCP for an existing saved Retention report. Reduce nested report results before returning them.\n- Retention `interval` is capped at 90 only for `unit: \"day\"`, including the default when unit is omitted. Week and month intervals have no documented 90-unit cap. Both named and generic retention reads enforce the day limit.\n- `mixpanel_api_search` and `mixpanel_api_details` inspect the reviewed operation subset locally. `mixpanel_api_read` permits GET only on those operations, with fixed residency hosts and no caller URL or headers. It cannot reach service-account administration, arbitrary app APIs, profile mutation, JQL or ingestion. Generic export retains the named export's byte/event bounds. Use named tools for Engage and import.\n- `import_events` is an additive write and requires an Owner or Admin service account on the target project. Connecta enforces 2000 events, 10MB per batch, less than 1MB per event and Mixpanel's documented property limits. Supply stable `$insert_id` values and use strict validation. A 400 can still ingest the valid events; never retry a whole batch automatically. Inspect the target and failed records through a trusted operator workflow before deciding what to send again.\n- Profile writes are deferred. The official ingestion `/engage` contract requires `$token` in each update; service-account Basic alone does not satisfy it, and the service-account reference documents no project-token retrieval operation. Profile delete and other irreversible mutations are absent.\n- Query permits 60 queries per hour and 5 concurrent queries per project. Export permits 60 per hour, 3 per second and 100 concurrent queries. Ingestion permits 2GB uncompressed JSON per minute or about 30000 events per second. The API connection conservatively shares a 60-call/hour, 5-concurrent default across all tools and projects; it is a per-runtime approximation, not a distributed quota or a per-second export limiter. Operators may override `callAdmission`, especially for import-heavy deployments or multiple runtimes sharing an account. A vendor 429 still wins; respect `Retry-After`.\n- Successful responses recursively redact credential-named properties and bearer URLs. Arbitrary analytics properties remain user data; do not put secrets into free-text event names or property values. HTTP failures expose status and recovery guidance rather than vendor text that could echo a credential.\n"
     }
 };

package/dist/providers/mixpanel/value-safety.js

@@ -0,0 +1,16 @@
+import { safe } from "../_shared/rest/value-safety.js";
+/** Reviewed 2026-10-14 against the official schemas and service-account guide. */
+export const MIXPANEL_VALUE_SAFETY = {
+    title: "Mixpanel",
+    operations: {
+        "GET /api/app/me": safe("Account metadata has no documented response schema; redact credential-named fields recursively, including project tokens. No service-account administration endpoints are admitted."),
+        "GET /api/2.0/export": safe("JSONL event names and properties; arbitrary property bags pass through recursive credential and bearer-URL redaction."),
+        "GET /api/query/stream/query": safe("Activity event names and properties; arbitrary property bags pass through recursive credential and bearer-URL redaction."),
+        "POST /api/query/engage": safe("Existing profile ids and properties only; arbitrary property bags pass through recursive credential and bearer-URL redaction."),
+        "GET /api/query/insights": safe("Report headers name breakdown dimensions, not HTTP headers; numeric time series contain no authentication values.", ["headers"]),
+        "GET /api/query/funnels": safe("Funnel steps and conversion counts, no authentication values."),
+        "GET /api/query/funnels/list": safe("Saved funnel names and ids, no authentication values."),
+        "GET /api/query/retention": safe("Cohort dates and retention counts, no authentication values."),
+        "POST /import": safe("Import status and counts only. Vendor error text is withheld because it may quote submitted properties."),
+    },
+};

package/dist/providers/notion/index.d.ts

@@ -38,6 +38,13 @@ export interface NotionTokenOptions extends NotionCommonOptions {
     auth: {
         type: "token";
     };
+    /**
+     * Per-runtime downstream call-admission policy, replacing the default of
+     * 180 calls/minute and 3 concurrent. Business and Enterprise allow 600
+     * requests/minute per connection; all connections share a workspace-wide
+     * limit. One admitted call can make several HTTP requests.
+     */
+    callAdmission?: ConnectorCallAdmissionPolicy;
     /** Operator-facing label for the integration token. */
     credentialLabel?: string;
     /**

package/dist/providers/notion/index.js

@@ -11,13 +11,11 @@ export const NOTION_MCP_ENDPOINT = "https://mcp.notion.com/mcp";
 /** Lean by default: smaller than Notion's 100 so a first read stays cheap. */
 const DEFAULT_PAGE_SIZE = 25;
 /**
- * Notion documents "an average of three requests per second, with some bursts
- * beyond the average allowed" per connection. 180 calls per minute is that
- * average over a window short bursts pass and a sustained loop does not, and
- * `maxConcurrency: 3` is the load-bearing half — an averaged budget cannot stop
- * forty calls in one tick, and declaring a queue is also what makes the queue
- * settings legal at construction. Per runtime, and a floor on the real request
- * rate rather than a ceiling, since one admitted call can spend many fetches.
+ * Conservative default for every Notion plan: 180 calls per minute, with
+ * Connecta's concurrency cap of three to bound bursts. Business and Enterprise
+ * allow 600 requests per minute per connection; all connections also share a
+ * workspace-wide limit. This policy is per runtime and counts calls rather
+ * than HTTP requests, since one admitted call can spend many fetches.
  */
 const NOTION_ADMISSION = {
     rules: [
@@ -52,13 +50,31 @@ function oauthUsageGuide(purpose, instructions) {
 }
 /**
  * Reviewed in #705's provider audit against https://developers.notion.com/guides/mcp/mcp-supported-tools.
- * Retains the release-reviewed inventory, including names absent from today's
- * public reference. Live annotations were not reverified without credentials.
- * No schema digest is asserted without a captured schema to review.
+ * Extended in #814 from the operator's 2026-10-15 hosted catalog capture,
+ * recorded in mcp-catalog-2026-10-15.md. Includes names absent from the public
+ * reference and retains reviewed names absent from this client's catalog.
+ * Annotations were not visible; captured input summaries are not schema
+ * documents, so no schema digests are asserted.
  */
 const NOTION_MCP_CLASSIFICATION = {
     tools: {
         "notion-search": { "verdict": "read", "reason": "Retrieves Notion  information without changing vendor state." },
+        "notion-ai-search": {
+            "verdict": "read",
+            "reason": "Legacy AI search, still callable by name; retrieves matching content without changing vendor state.",
+        },
+        "notion-get-self": {
+            "verdict": "read",
+            "reason": "Returns the connected workspace and user without changing vendor state.",
+        },
+        "notion-get-tool-access": {
+            "verdict": "read",
+            "reason": "Reads which tools the workspace plan allows; it grants nothing and changes nothing.",
+        },
+        "notion-download-skill": {
+            "verdict": "read",
+            "reason": "Returns an existing Skill as a signed, expiring archive URL; it changes no workspace state.",
+        },
         "notion-search-skills": {
             "verdict": "read",
             "reason": "Retrieves Notion skills information without changing vendor state.",
@@ -185,6 +201,94 @@ const NOTION_MCP_CLASSIFICATION = {
             "reason": "update view changes existing Notion state or removes it.",
         },
         "notion-stop-session": { "verdict": "destructive", "reason": "Stops an existing session and interrupts its work." },
+        "notion-check-mcp-next-steps": {
+            "verdict": "read",
+            "reason": "Returns an upsell or next-step card without changing workspace state or enabling access.",
+        },
+        "notion-show-advanced-analysis-next-steps": {
+            "verdict": "read",
+            "reason": "Returns a message and destination link without changing workspace state or enabling access.",
+        },
+        "notion-get-enabled-skills": {
+            "verdict": "read",
+            "reason": "Lists the current user's enabled skills; enabling or disabling them is a separate write.",
+        },
+        "notion-get-file-download-urls": {
+            "verdict": "read",
+            "reason": "Returns signed, expiring download URLs for existing file references without changing workspace state; use only for downloads and do not expose the URLs.",
+        },
+        "notion-get-groups": {
+            "verdict": "read",
+            "reason": "Retrieves visible permission group IDs and names without changing membership or permissions.",
+        },
+        "notion-list-favorite-pages": {
+            "verdict": "read",
+            "reason": "Lists existing favorites in sidebar order without changing them.",
+        },
+        "notion-list-page-backlinks": {
+            "verdict": "read",
+            "reason": "Retrieves IDs, titles and URLs of existing page backlinks without changing links or pages.",
+        },
+        "notion-list-private-pages": {
+            "verdict": "read",
+            "reason": "Lists existing pages and databases in the user's Private sidebar without changing them.",
+        },
+        "notion-list-recent-pages": {
+            "verdict": "read",
+            "reason": "Lists the user's existing page-view history without changing pages or recording a new view.",
+        },
+        "notion-list-shared-pages": {
+            "verdict": "read",
+            "reason": "Lists existing pages and databases in the user's Shared sidebar without changing sharing.",
+        },
+        "notion-memory-search": {
+            "verdict": "read",
+            "reason": "Searches memories saved by connected agents in earlier sessions without saving or changing memories.",
+        },
+        "notion-query-multiple-data-sources": {
+            "verdict": "read",
+            "reason": "Runs read-only SQLite SQL across existing data sources without changing them.",
+        },
+        "notion-delete-comment": {
+            "verdict": "destructive",
+            "reason": "Deletes a comment and may remove its discussion when no comments remain.",
+        },
+        "notion-delete-databases": {
+            "verdict": "destructive",
+            "reason": "Moves existing databases to Trash; an optional confirmation flag does not make this tool read-only.",
+        },
+        "notion-delete-pages": {
+            "verdict": "destructive",
+            "reason": "Moves existing pages to Trash; an optional confirmation flag does not make this tool read-only.",
+        },
+        "notion-restore-pages": {
+            "verdict": "destructive",
+            "reason": "Restores pages or databases from Trash and changes their workspace state.",
+        },
+        "notion-set-comment-reaction": {
+            "verdict": "destructive",
+            "reason": "Adds or removes the user's emoji reaction on a comment; repeatability does not make it read-only.",
+        },
+        "notion-set-discussion-resolved": {
+            "verdict": "destructive",
+            "reason": "Resolves or reopens an existing comment discussion.",
+        },
+        "notion-update-comment": {
+            "verdict": "destructive",
+            "reason": "Replaces the text of an existing comment.",
+        },
+        "notion-update-enabled-skills": {
+            "verdict": "destructive",
+            "reason": "Changes the current user's skill enablement for external MCP clients, Notion AI, or both.",
+        },
+        "notion-update-folder": {
+            "verdict": "destructive",
+            "reason": "Changes an existing folder by adding or removing files or adding a subfolder.",
+        },
+        "notion-upload-skill": {
+            "verdict": "destructive",
+            "reason": "Preparation returns a credential-bearing upload URL and headers; completion replaces the target page title, Description, body and Files. Both actions stay writes.",
+        },
     },
 };
 const COMMON = keys("title", "authScope", "purpose", "instructions", "maxResultBytes");
@@ -198,6 +302,7 @@ const NOTION_OPTIONS = variants(["auth", "type"], {
     }).shape,
     token: optionsOf()({
         ...COMMON,
+        callAdmission: CALL_ADMISSION,
         ...keys("credentialLabel", "defaultPageSize"),
         auth: optionsOf()(keys("type")),
     }).shape,
@@ -230,7 +335,7 @@ function notionToken(id, options, provider) {
             placeholder: "Paste the integration token",
         },
         testCredential: rest.testCredential,
-        callAdmission: NOTION_ADMISSION,
+        callAdmission: options.callAdmission === undefined ? NOTION_ADMISSION : options.callAdmission,
         usageGuide: {
             content: tokenUsageGuide(options.purpose, options.instructions),
             summary: "Internal integration over REST. Flattened reads, authoring helpers, and the pinned API index for the rest.",