Studio

com.fintechstudiosPublished by fintechstudios.comOfficial publisherv1.1.0Updated Oct 24, 2026

Real-time financial news & regulatory intelligence: cited search, fetch, summaries, collections.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

Gives an assistant cited search, fetch and summarization of real-time financial news and regulatory intelligence, plus collections.

What you can do
Studio exposes tools for searching and fetching real-time financial news and regulatory intelligence, producing summaries and organizing results into collections. Results are cited, so the assistant can point back to sources. It is offered both as a hosted remote endpoint and as a local npm package over stdio.
When to use it
Useful when an assistant needs current financial or regulatory news with citations, for example monitoring developments, gathering source-backed summaries, or assembling collections of items on a topic.
Requirements
Either connect to the remote endpoint or run the npm package @fts-studio/studio-mcp locally with Node.js over stdio. Authentication is OAuth and required, and an FTS Studio API key must be supplied in the FTS_API_KEY environment variable. Network access is needed.
Before you install
The server requires an API key (FTS_API_KEY), which is a secret and should be kept out of shared configuration. The key may be a live key, so treat it as billable or production-sensitive. Search and fetch requests send queries to a third-party service.

Installation

In SourceWeft

  1. Open Studio 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/com.fintechstudios%2Fstudio/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": {
    "studio": {
      "type": "http",
      "url": "https://mcp.fintechstudios.com/mcp"
    }
  }
}

README

This repository has no README.

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

2
  1. v1.1.0LatestOct 13, 2026
  2. v1.0.0Sep 16, 2026

Score

60% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.