INDIVIDUAL MCP TOOL

get_rejection_funnel

Use this when diagnosing zero or few trades; it returns server-counted candidates, qualifications, submissions, fills, and rejection reasons.

papertigerapp.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://api.papertigerapp.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_rejection_funnel and invoke it with your own arguments.

{}

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

CONNECT WITH APPROVAL

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

Codex

~/.codex/config.toml

[mcp_servers.papertiger]
url = "https://api.papertigerapp.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "papertiger": {
      "type": "http",
      "url": "https://api.papertigerapp.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: papertiger
Remote MCP URL: https://api.papertigerapp.com/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": {
    "papertiger": {
      "url": "https://api.papertigerapp.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "papertiger": {
      "type": "http",
      "url": "https://api.papertigerapp.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "papertiger",
  "transport": "streamable-http",
  "url": "https://api.papertigerapp.com/mcp"
}

MCP Inspector

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

get_capabilities — Use this when the user wants to know which PaperTiger research, paper-trading, experiment, or analysis workflows are available.
get_account_context — Use this before account-scoped work to inspect the connected user, wallets, buying power, and application wallet limit.
create_wallet — Use this when the user wants an isolated PaperTiger wallet for a paper-trading hypothesis or experiment.
update_wallet — Use this when the user wants to rename a specific PaperTiger paper wallet.
reset_wallet — Use this only when the user explicitly asks to erase a wallet's paper orders, positions, activities, and performance and restore its starting balance.
delete_wallet — Use this only when the user explicitly asks to permanently delete a named PaperTiger wallet and its paper-trading history.
search_markets — Use this to find current public Polymarket or Kalshi markets before creating a hypothesis, paper order, or experiment.
resolve_market — Use this when the user supplies an exact Polymarket or Kalshi URL and needs the canonical PaperTiger market identifiers.