Clearvoyance
REMOTE · CLEARVOYANCE.AI · SCANNED SEP 28
Anonymous feedback from real people by voice or text, with an AI report. Flat price per campaign.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (close_campaign). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 4645 tokens (~172/item across 27 items; 27 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (52% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 27 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Clearvoyance MCP server?
Clearvoyance is a hosted endpoint at https://clearvoyance.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · clearvoyance.ai
claude mcp add --transport http ai-clearvoyance-clearvoyance 'https://clearvoyance.ai/mcp'
{
"mcpServers": {
"ai-clearvoyance-clearvoyance": {
"url": "https://clearvoyance.ai/mcp"
}
}
} {
"servers": {
"ai-clearvoyance-clearvoyance": {
"type": "http",
"url": "https://clearvoyance.ai/mcp"
}
}
} [mcp_servers.ai-clearvoyance-clearvoyance] url = "https://clearvoyance.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-clearvoyance-clearvoyance": {
"type": "remote",
"url": "https://clearvoyance.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-clearvoyance-clearvoyance --url 'https://clearvoyance.ai/mcp' --transport streamable-http
mcp_servers:
ai-clearvoyance-clearvoyance:
url: "https://clearvoyance.ai/mcp" {
"McpServers": {
"ai-clearvoyance-clearvoyance": {
"Transport": "http",
"Url": "https://clearvoyance.ai/mcp"
}
}
} assistant mcp add ai-clearvoyance-clearvoyance -t streamable-http -u 'https://clearvoyance.ai/mcp'
{
"mcpServers": {
"ai-clearvoyance-clearvoyance": {
"type": "http",
"url": "https://clearvoyance.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://clearvoyance.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=clearvoyance.ai | CN=WE1,O=Google Trust Services,C=US | 14 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c29a3de0fe9de234137a9a0ea896c272 |
| SANs: clearvoyance.ai, *.clearvoyance.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of clearvoyance.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| clearvoyance.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
| content-security-policy | frame-ancestors 'self'; base-uri 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://clearvoyance.ai/mcp | Verified | 200 | |
| http (plaintext) | http://clearvoyance.ai/mcp | HTTPS enforced | 301 | https://clearvoyance.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_campaign Analyse the answers ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| campaignId | integer | yes | A campaign id from launch_campaign or list_my_campaigns |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
check_topup Check a card top-up ~78
Whether a card top-up session has been paid and credited. Safe to call repeatedly; credits at most once.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| sessionId | string | yes | The sessionId create_card_topup returned (cs_…) |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
close_account Close the account and refund the balance ~202
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| confirm | boolean | – | true to actually close and refund. Omit or false to preview only. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
close_campaign Close a campaign ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| campaignId | integer | yes | A campaign id from launch_campaign or list_my_campaigns |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
create_account Create an account ~183
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | – | Optional name for the account, chosen by you (e.g. 'acme-shop post-purchase bot') |
| mode | string | – | Default 'live'. Use 'sandbox' to try everything with a notional balance. |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
create_campaign ~416
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).
| Name | Type | Req | Description |
|---|---|---|---|
| accessToken | string | yes | One-time access token from verify_payment |
| cohortEmails | array | yes | Email addresses of participants (minimum 2 for privacy) |
| description | string | yes | Short description of the campaign purpose |
| digitalGiftText | string | – | Optional digital gift description shown to NO_REWARD participants (e.g. a discount code) |
| expiresInDays | integer | – | Campaign duration in days (1–42, default 7) |
| incentiveCents | integer | – | Reward per participant in cents (e.g. 500 = $5.00). Required for INCENTIVIZED. |
| minPercent | number | – | Minimum response rate (%) required to unlock results. Defaults to 50. |
| questions | array | yes | List of audio questions for participants to answer |
| rewardMint | string | – | SPL token mint address for rewards. Defaults to USDC if omitted. |
| rewardMode | string | yes | INCENTIVIZED: crypto rewards per response. NO_REWARD: survey only, flat activation fee. |
| title | string | yes | Campaign title (shown to participants) |
No output schema declared.
No examples provided.
create_card_topup Top up by card ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| amountCents | integer | yes | US cents, e.g. 2000 for $20.00. Minimum 499. |
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
export_campaign_data ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | integer | yes | Campaign ID to export |
| sessionToken | string | yes | Session token from verify_login_signature |
No output schema declared.
No examples provided.
get_account Account and balance ~57
The account behind a key: mode, balance, what is available to launch with, the declared deposit wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
get_agent_config ~79
LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). Returns the payment configuration needed before starting an agent session: treasury wallet address, accepted token mint (USDC on Solana), and the one-time session fee in cents. Call this first to learn how much to pay and where.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_campaign Campaign status ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| campaignId | integer | yes | A campaign id from launch_campaign or list_my_campaigns |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
get_campaign_details ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | integer | yes | Campaign ID to inspect |
| sessionToken | string | yes | Session token from verify_login_signature |
No output schema declared.
No examples provided.
get_campaign_results Campaign results ~131
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).
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| campaignId | integer | yes | A campaign id from launch_campaign or list_my_campaigns |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
get_ledger Ledger ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| limit | integer | – | Rows to return, default 100 |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
get_login_nonce ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Your Solana wallet public key (base58) |
No output schema declared.
No examples provided.
get_pricing Price list ~95
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
get_session_nonce ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| walletAddress | string | yes | Your Solana wallet public key (base58) |
No output schema declared.
No examples provided.
initialize_session ~188
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 the payment details (treasury address, token mint, amount in cents). After calling this, send the required USDC to the treasury address on-chain, then call verify_payment with the transaction signature to receive an 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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Exact message string returned by get_session_nonce (must match byte for byte) |
| signature | string | yes | Base58-encoded Ed25519 signature of the message returned by get_session_nonce |
| walletAddress | string | yes | Your Solana wallet public key (base58) |
No output schema declared.
No examples provided.
launch_campaign Launch a campaign ~501
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| cohortEmails | array | – | targeted only: the addresses to invite (10–200). Duplicates are folded. The list is discarded once every invitation is queued; only hashes are kept. |
| description | string | yes | What you want to learn. Steers the AI analysis; participants do not see it. |
| expiresInDays | integer | – | 1–42. Default 14 for open_link, 7 for targeted. |
| giftText | string | – | Shown to a participant after answering: a promo code, a thank-you, a link. Optional. |
| kind | string | yes | open_link: a share link anyone can answer, closing at responseCap — put it in your own post-purchase email. targeted: we email one invitation per address in cohortEmails. |
| minPercent | integer | – | targeted only: results unlock once this share of the list has answered. Floored at 50. |
| questions | array | yes | 1–10 questions participants answer by voice or text. No links or phone numbers. |
| responseCap | integer | – | open_link only: 10, 50, 100 or 200 — the link closes at that many answers. Sets the tier: $4.99 / $17.99 / $29.99 / $49.99. |
| senderName | string | – | Who is asking, as participants see it (your shop or product name). Required for open_link. |
| title | string | yes | Shown to participants, e.g. 'How was your order?' |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
list_campaigns ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionToken | string | yes | Session token from verify_login_signature |
No output schema declared.
No examples provided.
list_my_campaigns List campaigns ~65
Every campaign on this account with its status, answers so far, the share link (open link), and what it has cost so far.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
quote_campaign Quote a campaign ~408
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.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | yes | Your Clearvoyance API key (cv_live_… or cv_test_…), from create_account |
| cohortSize | integer | – | targeted only: how many people you will invite (10–200). The number, not the addresses. |
| description | string | yes | What you want to learn. Steers the AI analysis; participants do not see it. |
| expiresInDays | integer | – | 1–42. Default 14 for open_link, 7 for targeted. |
| giftText | string | – | Shown to a participant after answering: a promo code, a thank-you, a link. Optional. |
| kind | string | yes | open_link: a share link anyone can answer, closing at responseCap — put it in your own post-purchase email. targeted: we email one invitation per address in cohortEmails. |
| minPercent | integer | – | targeted only: results unlock once this share of the list has answered. Floored at 50. |
| questions | array | yes | 1–10 questions participants answer by voice or text. No links or phone numbers. |
| responseCap | integer | – | open_link only: 10, 50, 100 or 200 — the link closes at that many answers. Sets the tier: $4.99 / $17.99 / $29.99 / $49.99. |
| senderName | string | – | Who is asking, as participants see it (your shop or product name). Required for open_link. |
| title | string | yes | Shown to participants, e.g. 'How was your order?' |
| Name | Type | Req | Description |
|---|---|---|---|
| ok | boolean | yes | – |
No examples provided.
validate_campaign ~304
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 including protocol fee for incentivized campaigns, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| cohortSize | number | – | How many participants — the number, not the email addresses |
| description | string | – | What you want to learn |
| expiresInDays | number | – | 1-42, default 7 |
| incentiveCents | number | – | Reward per participant in cents (incentivized campaigns) |
| minPercent | number | – | Privacy threshold; floored at 50 |
| questions | array | – | 1-10 questions with non-empty text |
| rewardMint | string | – | SPL token mint for the reward; defaults to USDC |
| rewardMode | string | – | Defaults to INCENTIVIZED |
| title | string | – | Campaign title, shown to participants |
No output schema declared.
No examples provided.
verify_campaign_activation ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | integer | yes | Campaign ID from create_campaign |
| txSignature | string | yes | Solana transaction signature of your USDC activation fee payment to treasury |
| walletAddress | string | yes | Your Solana wallet public key (must match the campaign creator) |
No output schema declared.
No examples provided.
verify_campaign_funding ~149
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.
| Name | Type | Req | Description |
|---|---|---|---|
| campaignId | integer | yes | Campaign ID from create_campaign |
| txSignature | string | yes | Solana transaction signature of your USDC transfer to the escrow address |
| walletAddress | string | yes | Your Solana wallet public key (must match the campaign creator) |
No output schema declared.
No examples provided.
verify_login_signature ~145
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Exact message string returned by get_login_nonce (must match exactly) |
| signature | string | yes | Base58-encoded Ed25519 signature of the message returned by get_login_nonce |
| walletAddress | string | yes | Your Solana wallet public key (base58) |
No output schema declared.
No examples provided.
verify_payment ~114
LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet). Verifies your on-chain USDC payment to the treasury and returns a one-time access token. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| sessionId | integer | yes | Session ID returned by initialize_session |
| txSignature | string | yes | Solana transaction signature of your USDC payment to treasury |
No output schema declared.
No examples provided.
What is the Clearvoyance MCP server?
Clearvoyance is an MCP server listed in the public MCP registry as ai.clearvoyance/clearvoyance. Anonymous feedback from real people by voice or text, with an AI report. Flat price per campaign. This page covers its hosted endpoint (https://clearvoyance.ai/mcp).
Is the Clearvoyance MCP server safe to use?
Clearvoyance scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Clearvoyance MCP server expose?
Clearvoyance exposes 27 tools: get_pricing, create_account, get_account, get_ledger, create_card_topup, and 22 more. Their descriptions and schemas cost roughly 4,363 tokens of context every time the server is loaded.
Does the Clearvoyance MCP server require authentication?
No. We connected to Clearvoyance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Clearvoyance MCP server still maintained?
Clearvoyance is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.