Unverified50% confidenceEventExact time
In the author's validation with eight records, querying directly in SQL, submitting via MCP and then closing the connection, both the CLI and a new MCP session retrieved the same three-row summary result.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
10/19/2026
First Seen
Valid until: 1/17/2027
Sources
Related Entities
Related Claims
UnverifiedPlunger's three entry points (GUI, CLI, MCP) share the same set of saved requests, the same set of variables, and the same history.69% similarUnverifiedThe division-of-labor pattern of MCP for exploration and CLI for execution: first use MCP for exploratory analysis, then hand the confirmed logic to the CLI to solidify, avoiding manually copying SQL throughout or writing scripts too early and incurring excessive debugging cost.67% similarUnverifiedPlunger's history marks whether each request came from the CLI or from MCP.66% similarUnverifiedWhen evaluating an MCP integration, one must confirm that permission checks occur on the server side in the context of each retrieval request, rather than relying solely on identity verification at connection initialization.66% similarUnverifiedcline mcp add now retains the value of --header when opening the configuration wizard; previously, the request header would be lost when accepting pre-filled answers.65% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1066841API
curl https://kongchang.com/api/v1/knowledge/claims/1066841MCP
get_claim(id=1066841)