RMCP.DEV
← Registry

Data Collection

clearvoyance.ai

MCP server for a prepaid campaign platform that collects answers from open or targeted respondents, including pricing, account creation, ledger tracking, and Stripe card top-ups.

2 endpoints36 known toolsFirst detected September 27, 2026Last detected October 5, 2026

ENDPOINT 1

https://clearvoyance.ai/mcp

No auth detected

MCP server metadata

Name
clearvoyance
Version
1.1.0
Capabilities
tools.listChanged
Server instructions

Clearvoyance collects anonymous, honest feedback from real people by voice or text and returns the answers plus an AI report. Start with get_pricing, then create_account: mode "sandbox" tries everything with a notional $20 balance and sends nothing; "live" is for real campaigns. Keep the apiKey it returns - it is shown once and every other tool needs it. A live account needs a top-up first: create_card_topup gives a Stripe link for a person to pay. Then quote_campaign and launch_campaign. kind "open_link" returns a share link to put in the user's own post-purchase email (giftText, such as a promo code, is shown after answering); kind "targeted" emails one invitation per address. Poll get_campaign; get_campaign_results and analyze_campaign once the privacy threshold is met; close_campaign when done. Money not spent on campaigns stays in the balance for the next one; close_account (preview first, then confirm: true with the owner's agreement) refunds it to the card that paid. Price: a flat price per campaign by size, from $4.99, charged in full at launch whatever it receives. Answers carry no link to the person and are deleted 30 days after the campaign closes. Tools marked LEGACY are the older Solana-wallet flow; use the key flow unless the user is already integrated with it.

Known tools 27

get_pricing

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.

Inferred read-only
create_account

Creates an agent account and returns its API key ONCE — store it; it is not kept anywhere and cannot be shown again.

Inferred read-only
get_account

The account behind a key: mode, balance, what is available to launch with, the declared deposit wallet.

Inferred read-only
get_ledger

Every movement of money on the account, newest first: top-ups, each campaign's price (set aside and charged at launch), refunds.

Inferred read-only
create_card_topup

Creates a Stripe Checkout link for a PERSON to pay with a card; hand them the checkoutUrl.

Potential side effects
check_topup

Whether a card top-up session has been paid and credited.

Inferred read-only
quote_campaign

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).

Potential side effects
launch_campaign

Creates the campaign and makes it live at once, charging its flat price from your balance (quote_campaign tells you the price).

Inferred read-only
list_my_campaigns

Every campaign on this account with its status, answers so far, the share link (open link), and what it has cost so far.

Inferred read-only
get_campaign

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.

Inferred read-only
get_campaign_results

The answers, once the privacy threshold is met (open link: 5 answers; targeted: minPercent of the list).

Inferred read-only
analyze_campaign

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.

Inferred read-only
close_campaign

Ends the campaign now: no more answers are accepted.

Inferred read-only
close_account

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).

Potential side effects
get_agent_config

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
get_session_nonce

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
initialize_session

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
verify_payment

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
validate_campaign

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
create_campaign

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
verify_campaign_funding

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
verify_campaign_activation

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
get_login_nonce

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
verify_login_signature

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
list_campaigns

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
get_campaign_details

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only
export_campaign_data

LEGACY wallet flow — new integrations should use create_account and launch_campaign (API key + prepaid balance, no wallet).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clearvoyance]
url = "https://clearvoyance.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "clearvoyance": {
      "type": "http",
      "url": "https://clearvoyance.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: clearvoyance
Remote MCP URL: https://clearvoyance.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "clearvoyance": {
      "url": "https://clearvoyance.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "clearvoyance": {
      "type": "http",
      "url": "https://clearvoyance.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "clearvoyance",
  "transport": "streamable-http",
  "url": "https://clearvoyance.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://clearvoyance.ai/connect/mcp

No auth detected

MCP server metadata

Name
clearvoyance-connect
Version
1.0.0
Capabilities
tools.listChanged
Server instructions

Clearvoyance collects anonymous, honest feedback from real people by voice or text and returns the answers plus an AI report. A campaign is a share link the user puts in front of their customers (a post-purchase email, a receipt, a website); it closes after 10, 50, 100 or 200 answers, or when the user closes it. Use get_pricing and quote_campaign to plan one (no sign-in needed). create_campaign saves it as a draft and returns campaignUrl: nothing is charged or sent from the chat — the user reviews the draft and pays its flat price on clearvoyance.ai, and it goes live when they do. Then get_campaign for the share link and progress, get_campaign_results and analyze_campaign once enough people have answered, close_campaign to stop early. Answers carry no link to the person who gave them and are deleted 30 days after the campaign closes.

Known tools 9

get_pricing

The flat price of a feedback campaign by how many answers it collects (10, 50, 100 or 200), and how paying works.

Inferred read-only
quote_campaign

Checks a campaign before it is created: lists every problem at once, any adjustments, and its flat price.

Inferred read-only
create_campaign

Saves the campaign as an unpaid draft in the user's Clearvoyance account and returns campaignUrl, the draft's page on clearvoyance.ai.

Inferred read-only
list_campaigns

The user's feedback campaigns, newest first, with their state (draft_unpaid, live, closed, discarded) and answers so far.

Inferred read-only
get_campaign

One campaign: its state, whether it is paid, the share link once it is live, answers so far and whether enough people have answered to unlock the results.

Inferred read-only
get_campaign_results

The anonymous answers, once enough people have answered to protect their privacy.

Inferred read-only
analyze_campaign

The AI report on a campaign's answers: themes, sentiment and quotes.

Inferred read-only
close_campaign

Stops a live campaign: its share link stops taking answers.

Inferred read-only
delete_draft

Throws away a draft that has not been paid for.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.clearvoyance-connect]
url = "https://clearvoyance.ai/connect/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "clearvoyance-connect": {
      "type": "http",
      "url": "https://clearvoyance.ai/connect/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: clearvoyance-connect
Remote MCP URL: https://clearvoyance.ai/connect/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "clearvoyance-connect": {
      "url": "https://clearvoyance.ai/connect/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code 
{
  "servers": {
    "clearvoyance-connect": {
      "type": "http",
      "url": "https://clearvoyance.ai/connect/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "clearvoyance-connect",
  "transport": "streamable-http",
  "url": "https://clearvoyance.ai/connect/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.