Foxy Pro

app.bottomupPublished by bottomup.appOfficial publisherv1.0.1Updated Oct 27, 2026

Market analysis from live data: stocks, ETFs, commodities, crypto, reports and options levels.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that gives an assistant live market analysis across stocks, ETFs, commodities, crypto, reports and options levels.

What you can do
  • Retrieve live market data and analysis for stocks, ETFs, commodities and crypto.
  • Pull market reports and options levels for the instruments it covers.
  • No individual tools are documented, so the exact commands and output formats are not described in the listing.
When to use it
Useful when an assistant needs current market context — quotes, analysis, reports or options levels — while researching or discussing investments, rather than relying on stale training data.
Requirements
A remote streamable HTTP endpoint at foxy-api.bottomup.app; no local package or runtime. OAuth sign-in is required, so a Foxy Pro account with the provider is needed. No environment variables or headers are declared.
Before you install
Access is tied to an OAuth account with the provider, so review what data the connection exposes. Market analysis and options levels are informational and may be incomplete or delayed; nothing in the listing says the server places trades or moves money, but verify before relying on it for decisions.

Installation

In SourceWeft

  1. Open Foxy Pro in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.bottomup%2Ffoxy-pro/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "foxy-pro": {
      "type": "http",
      "url": "https://foxy-api.bottomup.app/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestOct 25, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.