Clearvoyance MCP server
ai.clearvoyance/clearvoyanceclearvoyance.aistreamable-httpv1.1.0Scanned
Anonymous feedback from real people by voice or text, with an AI report. Flat price per campaign.
27 tools: 2 can delete or cancel things, 2 do something that can't be undone, 11 change things and 12 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here can delete or cancel things and 2 do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Clearvoyance MCP server can do
The Clearvoyance MCP server is published by clearvoyance.ai, a domain the MCP Registry verified. It has 27 tools. It can delete or cancel things (2 tools: close_campaign and close_account), do things that cannot be undone, such as sending, paying or publishing (check_topup and verify_payment) and create or change data (11 tools: create_account, create_card_topup, quote_campaign, launch_campaign and 7 more). 12 tools only read.
5 tools bring in text other people can write (create_card_topup, check_topup, launch_campaign and 2 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
27 tools
Deletes or cancels 2Claude Code: deny
close_accountCloses the account and refunds what is left of the balance to the card(s) that paid, newest top-up first, less Stripe's processing fee on each payment refunded (Stripe keeps it; th…Reads text others writeNo findings
Why it is in this group
- The name "close_account" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Closes the account and refunds what is left of the balance to the card(s) that paid, newest top-up first, less Stripe's processing fee on each payment refunded (Stripe keeps it; the account owner bears it). Call it WITHOUT confirm first: that only previews the refund per card and moves nothing. Then, only if the account owner has agreed, call again with confirm: true. Every campaign must be closed first. A refund the card refuses stays as credit, and the key keeps working while any credit remains. Once the balance is zero the key is revoked for good. Sandbox accounts: the key is revoked and nothing is refunded (the credit is notional). If Stripe does not answer, call again to finish.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
close_campaignEnds the campaign now: no more answers are accepted.No findings
Why it is in this group
- The name "close_campaign" says "close": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Ends the campaign now: no more answers are accepted. The price was charged at launch, so closing early refunds nothing. Campaigns also close on their own at the cap or on expiry. Closing twice changes nothing.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Can't be undone 2Claude Code: ask
check_topupWhether a card top-up session has been paid and credited.Reads text others writeNo findings
Why it is in this group
- The name "check_topup" says "topup": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Whether a card top-up session has been paid and credited. Safe to call repeatedly; credits at most once.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
verify_paymentLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "verify_payment" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). Only when initialize_session returned paymentRequired true: verifies your on-chain USDC payment to the treasury and returns a one-time access token. A free session needs no payment and is refused here. The access token is required for create_campaign and expires after 1 hour. The token is single-use — it is consumed when create_campaign is called.
Changes things 11Claude Code: ask
analyze_campaignRuns the AI analysis over every answer so far and returns an executive summary with themes, sentiment and quotes; the report is then also part of get_campaign_results.Reads text others writeNo findings
Why it is in this group
- The name "analyze_campaign" says "analyze": a word for reading.
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Runs the AI analysis over every answer so far and returns an executive summary with themes, sentiment and quotes; the report is then also part of get_campaign_results. Re-running with no new answers returns the same report. A sandbox campaign gets the illustrative sample report, marked sample: true.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
create_accountCreates an agent account and returns its API key ONCE — store it; it is not kept anywhere and cannot be shown again.No findings
Why it is in this group
- The name "create_account" says "create": a word for a change.
Description, as the server wrote it Creates an agent account and returns its API key ONCE — store it; it is not kept anywhere and cannot be shown again. No email, no password, nothing personal: the account is a key and a balance. mode 'sandbox' gives a cv_test_ key with $20.00 of notional balance — the same API, no money moves, no email is sent (a sandbox targeted campaign returns its invitation links instead of sending them). mode 'live' (default) starts at $0 and needs a top-up before a campaign can launch. Free; limited to 10 accounts per hour per address.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
create_campaignLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "create_campaign" says "create": a word for a change.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). (launch_campaign is its equivalent for the key flow.) Creates a new anonymous audio feedback campaign. Two modes: (a) INCENTIVIZED — participants earn USDC rewards; you must fund an escrow address returned in the response, then call verify_campaign_funding. Participants have 30 days after the campaign ends to claim; anything unclaimed then goes back to the wallet you signed in with. (b) NO_REWARD — survey only, no crypto rewards; you pay a flat Stripe activation fee (returned in activationRequired), then call verify_campaign_activation. The accessToken is single-use and is consumed on success. Privacy threshold: minPercent enforces the minimum response rate before results are unlocked (minimum 50%). Campaign expiry: 1–42 days (default 7).
create_card_topupCreates a Stripe Checkout link for a PERSON to pay with a card; hand them the checkoutUrl.Reads text others writeNo findings
Why it is in this group
- The name "create_card_topup" says "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Creates a Stripe Checkout link for a PERSON to pay with a card; hand them the checkoutUrl. Live accounts only, $4.99 to $1,000.00. Nothing is credited until they pay. Then call check_topup with the sessionId until credited is true — the balance is credited once, by whichever of Stripe's webhook, check_topup or the payer's own page sees the payment first.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
export_campaign_dataLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). (get_campaign_results is its equivalent for the key flow, as JSON with the AI report.) Exports raw response data for a completed campaign as CSV text. Each row contains a response ID, submission timestamp, and one column per question with the participant's audio transcription as the value. Only available after campaign expiry. AI insight reports are not included (raw data only). Data is deleted 30 days after the first export — check agentDataExpiresAt from get_campaign_details. Requires the sessionToken from verify_login_signature.
initialize_sessionLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). Creates a new agent session, proving the wallet with a signature from get_session_nonce. Returns a sessionId and paymentRequired. While sessions are free (paymentRequired false), the response also carries the one-time accessToken for create_campaign, and no payment step follows. If paymentRequired is true, send the stated USDC amount to the treasury address on-chain, then call verify_payment with the transaction signature to receive the access token. The wallet you prove here becomes the campaign's creator, and is the only wallet that will be able to read its results from the dashboard.
launch_campaignCreates the campaign and makes it live at once, charging its flat price from your balance (quote_campaign tells you the price).Reads text others writeNo findings
Why it is in this group
- The description's first verb is "create": a word for a change.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Creates the campaign and makes it live at once, charging its flat price from your balance (quote_campaign tells you the price). open_link returns shareUrl — the link to put in front of the people you want to hear from; it closes at responseCap or on expiry. targeted sends one invitation per address in cohortEmails from clearvoyance.ai (a sandbox account gets inviteLinks back instead and nothing is emailed). The flat price for the campaign's size is charged from your balance in full at launch, whatever it receives; it is not refunded for fewer answers. Refused with INSUFFICIENT_BALANCE (shortfallCents) if the balance does not cover the tier, or INVALID_CAMPAIGN (problems[]) if the quote would fail.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
quote_campaignChecks a campaign BEFORE launching it, for free: every problem at once (not just the first), any adjustments we would make, the flat price that launching would charge, and whether …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Checks a campaign BEFORE launching it, for free: every problem at once (not just the first), any adjustments we would make, the flat price that launching would charge, and whether your balance covers it (and by how much it is short). For targeted campaigns pass cohortSize (the number of people), never the addresses. Always quote before launch_campaign.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
verify_campaign_activationLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). For NO_REWARD campaigns only. After you have paid the flat USDC activation fee (returned in activationRequired by create_campaign), call this with the payment transaction signature to launch the campaign LIVE. Invite emails are sent to all cohort participants automatically. This call is idempotent — safe to retry.
verify_campaign_fundingLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). For INCENTIVIZED campaigns only. After you have funded the escrow wallet returned by create_campaign, call this with the funding transaction signature to launch the campaign LIVE. Invite emails are sent to all cohort participants automatically. This call is idempotent — safe to retry if you are unsure whether it succeeded.
verify_login_signatureLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). Second step of dashboard authentication. Verifies your wallet signature against the nonce message from get_login_nonce. Returns a sessionToken (valid 24 hours) and your campaign list. Pass the sessionToken to list_campaigns, get_campaign_details, and export_campaign_data.
Only reads 12Show 12 read-only tools
get_accountThe account behind a key: mode, balance, what is available to launch with, the declared deposit wallet.No findings
Why it is in this group
- The name "get_account" says "get": a word for reading.
Description, as the server wrote it The account behind a key: mode, balance, what is available to launch with, the declared deposit wallet.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_agent_configLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "get_agent_config" says "get": a word for reading.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). Returns the agent session configuration: whether a session fee applies (paymentRequired), the fee in cents, the accepted token mint (USDC on Solana) and the treasury wallet address.
get_campaignOne campaign: status, answers so far, invitations sent or the cap, the share link, the privacy threshold and whether it is met, and the price charged.No findings
Why it is in this group
- The name "get_campaign" says "get": a word for reading.
Description, as the server wrote it One campaign: status, answers so far, invitations sent or the cap, the share link, the privacy threshold and whether it is met, and the price charged.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_campaign_detailsLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "get_campaign_details" says "get": a word for reading.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). (get_campaign is its equivalent for the key flow.) Returns detailed stats for a specific campaign: invite count, response count, completion rate, question definitions, and campaign status. Only campaigns owned by your wallet are accessible. Requires the sessionToken from verify_login_signature.
get_campaign_resultsThe answers, once the privacy threshold is met (open link: 5 answers; targeted: minPercent of the list).No findings
Why it is in this group
- The name "get_campaign_results" says "get": a word for reading.
Description, as the server wrote it The answers, once the privacy threshold is met (open link: 5 answers; targeted: minPercent of the list). Below it the count and what is still needed. Each transcript is anonymous by construction — no field links an answer to a person. Includes the AI report if analyze_campaign has run. Answers are deleted 30 days after the campaign closes (dataDeletesAt).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_ledgerEvery movement of money on the account, newest first: top-ups, each campaign's price (set aside and charged at launch), refunds.No findings
Why it is in this group
- The name "get_ledger" says "get": a word for reading.
Description, as the server wrote it Every movement of money on the account, newest first: top-ups, each campaign's price (set aside and charged at launch), refunds. The balance after each row.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_login_nonceLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "get_login_nonce" says "get": a word for reading.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). First step of dashboard authentication. Returns a nonce and a message string that you must sign with your Solana wallet. The signed message is then passed to verify_login_signature to receive a session token. Nonces expire after 5 minutes.
get_pricingThe price list as data: a flat price per campaign by size (open link: 10/50/100/200 answers; targeted: 10–200 people), charged from your prepaid balance in full when a campaign lau…No findings
Why it is in this group
- The name "get_pricing" says "get": a word for reading.
Description, as the server wrote it The price list as data: a flat price per campaign by size (open link: 10/50/100/200 answers; targeted: 10–200 people), charged from your prepaid balance in full when a campaign launches, whatever it receives. Also the fee on crypto rewards and how unclaimed rewards are returned. Also the top-up rules and how the sandbox works. Public — no key needed. Call this first.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_session_nonceLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "get_session_nonce" says "get": a word for reading.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). First step of creating a campaign session. Returns the exact message you must sign with your Solana wallet, and the nonce inside it. Pass the message and your base58 signature to initialize_session. Nonces expire after 5 minutes, and a message signed for the dashboard will not work here.
list_campaignsLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "list_campaigns" says "list": a word for reading.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). (list_my_campaigns is its equivalent for the key flow.) Lists all campaigns created by your wallet. Requires the sessionToken from verify_login_signature. Returns campaign IDs, titles, statuses, cohort sizes, and data expiry dates.
list_my_campaignsEvery campaign on this account with its status, answers so far, the share link (open link), and what it has cost so far.No findings
Why it is in this group
- The name "list_my_campaigns" says "list": a word for reading.
Description, as the server wrote it Every campaign on this account with its status, answers so far, the share link (open link), and what it has cost so far.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_campaignLEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).No findings
Why it is in this group
- The name "validate_campaign" says "validate": a word for reading.
Description, as the server wrote it LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). (quote_campaign is its equivalent for the key flow.) Checks a campaign BEFORE you pay for anything. Free, and needs no session or access token. Returns whether it is valid, every problem at once (not just the first), any adjustments we would make (expiry clamped, privacy threshold raised, empty questions dropped), and what it will cost — the escrow total for incentivized campaigns (rewards only: the campaign price is paid at activation), or the activation fee for no-reward ones. Call this first, fix anything it reports, and only then call get_session_nonce and pay. Pass the cohort SIZE, not the addresses: this endpoint never receives contact details.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:25 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 15
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://clearvoyance.ai/.well-known/oauth-protected-resource
- Authorization servers
- https://clearvoyance.ai
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 15 tools that change things (2 destructive, 2 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://clearvoyance.ai/mcp: tools/list returned 27 tools to an anonymous client, including close_campaign (destructive), close_account (destructive), check_topup (irreversible), verify_payment (irreversible), create_account (write) and 10 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http clearvoyance https://clearvoyance.ai/mcpclaude mcp add --transport http clearvoyance https://clearvoyance.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__clearvoyance__get_pricing",
"mcp__clearvoyance__get_account",
"mcp__clearvoyance__get_ledger",
"mcp__clearvoyance__list_my_campaigns",
"mcp__clearvoyance__get_campaign",
"mcp__clearvoyance__get_campaign_results",
"mcp__clearvoyance__get_agent_config",
"mcp__clearvoyance__get_session_nonce",
"mcp__clearvoyance__validate_campaign",
"mcp__clearvoyance__get_login_nonce",
"mcp__clearvoyance__list_campaigns",
"mcp__clearvoyance__get_campaign_details"
],
"ask": [
"mcp__clearvoyance__create_account",
"mcp__clearvoyance__create_card_topup",
"mcp__clearvoyance__check_topup",
"mcp__clearvoyance__quote_campaign",
"mcp__clearvoyance__launch_campaign",
"mcp__clearvoyance__analyze_campaign",
"mcp__clearvoyance__initialize_session",
"mcp__clearvoyance__verify_payment",
"mcp__clearvoyance__create_campaign",
"mcp__clearvoyance__verify_campaign_funding",
"mcp__clearvoyance__verify_campaign_activation",
"mcp__clearvoyance__verify_login_signature",
"mcp__clearvoyance__export_campaign_data"
],
"deny": [
"mcp__clearvoyance__close_campaign",
"mcp__clearvoyance__close_account"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as clearvoyance. Review it before you use it.
Capability tags behind 5 rules
- mcp__clearvoyance__create_card_topup untrusted-input
- mcp__clearvoyance__check_topup untrusted-input
- mcp__clearvoyance__launch_campaign untrusted-input
- mcp__clearvoyance__analyze_campaign untrusted-input
- mcp__clearvoyance__close_account untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/ai.clearvoyance/clearvoyance/verify?hash=b1e813818f5e81721525ffeb5865cc539b4b93dcc961b90bf15b71516d650344" | jq -e '.changed == false'Pinned hash b1e813818f5e, from Nov 11, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/ai.clearvoyance/clearvoyance/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/ai.clearvoyance/clearvoyance)Source: MCP Registry. Synced Oct 21, 2026, 17:41 UTC.
Clearvoyance MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Clearvoyance MCP server safe?
- No scan can promise that. What its definitions show: 27 tools, 15 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Clearvoyance MCP server delete data?
- Yes. 2 tools can delete, cancel or revoke something: close_campaign and close_account.
Can the Clearvoyance MCP server do things that cannot be undone?
- Yes. 2 tools can send, pay, publish or merge: check_topup and verify_payment.
What tools does the Clearvoyance MCP server have?
- 27 tools: 2 destructive, 2 irreversible, 11 write, 12 read. close_campaign, close_account, check_topup, verify_payment, create_account, create_card_topup, quote_campaign, launch_campaign and 19 more.
Does the Clearvoyance MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Clearvoyance MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Clearvoyance MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.