Add Verified Mode note to MCP Server page#129
Draft
claude[bot] wants to merge 2 commits into
Draft
Conversation
Contributor
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains.
|
| Filename | Overview |
|---|---|
| docs/mcp.mdx | Updates the MCP Verified Mode guidance to address the previously reported inaccurate exclusion wording. |
Reviews (2): Last reviewed commit: "Correct MCP Verified Mode note: results ..." | Re-trigger Greptile
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
…ied flagged not excluded
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Amy Madden · Slack thread
What & why
Before: The MCP Server page said nothing about Verified Mode, so MCP users had no way to know how enabling it affects their query results.
After: A short
Notecallout in the Permissions & Access section explains that when an admin enables Verified Mode, MCP query results still include all requested entities — data is not excluded — with unverified entities flagged and verified equivalents preferred. It links to the Verified Mode definition on the Mixpanel Agent page rather than duplicating it.How
<Note>callout todocs/mcp.mdxin the Permissions & Access section./docs/mixpanel-agent#verified-modeand/docs/data-governance/lexicon#verify-data.Status / merge gating
Kept as a draft. DF-452 (the MCP messaging change) is still In Progress as of this writing — hold merge until that behavior is confirmed live in production. The Mixpanel Agent page's own Verified Mode definition may also describe the pre-DF-446 exclusion behavior and likely needs a separate follow-up review.