Hosted MCP server/Finance

Redstone Markets MCP server

Hosted at redstonemarkets.com·Streamable HTTP

Redstone Markets provides returns, risk, and backtest data for US stocks and ETFs through six tools: get_security_metrics, compare_securities, backtest_portfolio, screen_securities, search_portfolios, and get_portfolio. An assistant can compare 2-5 tickers, test a described portfolio, screen by metrics such as Sharpe ratio or drawdown, and search public portfolios. The endpoint at https://redstonemarkets.com/api/mcp answers initialize and tools/list without authentication. The provider's Learn hub does not document the MCP server, so the tool list comes from the live endpoint.

redstonemarkets.com Streamable HTTP No authentication (endpoint answers initialize and tools/list) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Investors and analysts researching US stocks and ETFs with risk metrics and backtests.

  • Compare returns and risk for 2-5 tickers.
  • Backtest a portfolio described in plain language.
  • Screen for stocks or ETFs by Sharpe ratio and drawdown.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Setup

Install it in your client

Choose a client, run the command or use the one-click install, then verify the connection. The endpoint uses Streamable HTTP.

All client guides
  1. 01

    Run this command in your terminal

    This adds Redstone Markets as a remote Streamable HTTP server in Claude Code.

    Claude Code
    claude mcp add --transport http redstone-markets https://redstonemarkets.com/api/mcp --scope project
  2. 02

    Verify the connection

    Run claude mcp list, or open /mcp in a Claude Code session.

    Learn more about MCP in Claude Code

More clients, including project and global config files, are in the sidebar.

Connection

Endpoint and configuration

Endpoint
https://redstonemarkets.com/api/mcp
Host
redstonemarkets.com · /api/mcp
Transport
Streamable HTTP
Authentication
No authentication (endpoint answers initialize and tools/list)
Server name
redstone-markets
Listing type
Community or directory listing

The installer uses the server name redstone-markets. If you add the endpoint by hand, keep the same name so the guide and your config match.

Verification

Check the connection

After you add the server, confirm that the client can see its tools and that one small request returns what the provider describes.

  1. 1
    Open the tool list.

    Restart the client or start a new session. Confirm that redstone-markets appears and that the tools match the provider documentation.

  2. 2
    Run one small request.

    Start with: Compare returns and risk for 2-5 tickers. Check the result before you give the server more access.

  3. 3
    Check permissions.

    The provider documents no credential for this endpoint, so there is no scope or token to review. Remove the server when you no longer need it.

Server not checked yet

We checked the provider's page, not the MCP connection itself. No MCP sign-in or tool call was attempted. A provider page is linked but was not included in the automated check. Open it before setup.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The server connects but no tools appear. Confirm the URL and transport, then restart the client.
  • The first tool call times out. Try a smaller request and check the provider's status or rate limits.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.