Financial Signals MCP

io.github.FoundryNetPublished by GitHub account FoundryNetv1.0.0Updated Oct 24, 2026

Derived financial intelligence: insider patterns, earnings, institutional & ratio signals.

The publisher's own server: SIGNALS Loyalty Agent Platform

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint that gives an assistant derived financial intelligence: insider patterns, earnings, institutional and ratio signals.

What you can do
  • Surface derived financial signals for companies, including insider activity patterns.
  • Review earnings-related signals.
  • Look at institutional holdings signals.
  • Examine financial ratio signals.
  • No individual tools are documented, so the exact queries and output formats are not described.
When to use it
Useful when an assistant needs quick, pre-computed financial signals about companies rather than raw filings or market data, for example to screen or contextualize insider, earnings, institutional or ratio trends.
Requirements
A remote streamable HTTP endpoint; no packages, environment variables or headers are declared. The manifest declares no authentication, so no account or API key appears to be needed.
Before you install
The server is a third-party hosted endpoint with no declared authentication, so queries and any data sent to it leave your machine unencrypted only as far as the endpoint's own policies allow; treat outputs as derived signals, not investment advice, and verify before acting on them.

Installation

In SourceWeft

  1. Open Financial Signals MCP in the dashboard and add it to a workspace.
  2. 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/io.github.FoundryNet%2Ffinancial-signals-mcp/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.

{
  "mcpServers": {
    "financial-signals": {
      "type": "http",
      "url": "https://financial-signals-mcp-production.up.railway.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 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 listedRequired15 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.

Other Signals integrations