Finawaken Portfolio

com.finawakenPublished by finawaken.comOfficial publisherv1.0.1Updated Oct 26, 2026

Clarity on your investments: performance, holdings, dividends, ETF look-through and transactions.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that lets an assistant answer questions about your investment portfolio: performance, holdings, dividends, ETF look-through and transactions.

What you can do
  • Review portfolio performance and holdings
  • Look up dividend information
  • Break down ETF holdings through look-through analysis
  • Inspect transactions
  • No individual tools are listed, so the exact commands are not documented in the supplied material.
When to use it
Useful when you want to ask an assistant about your own investments — how a portfolio has performed, what it holds, what dividends came in, or what sits inside your ETFs — instead of exporting data by hand.
Requirements
A remote MCP endpoint at mcp.portfolio.finawaken.com over streamable HTTP. OAuth sign-in is required, so you need a Finawaken account or equivalent authorization; no environment variables or headers are declared.
Before you install
The server is granted OAuth access to personal financial data, so review the scopes requested during sign-in. It is a hosted third-party service, meaning your portfolio information is sent to and processed by Finawaken. No tool list is published, so what it can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Finawaken Portfolio 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.finawaken%2Fportfolio/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": {
    "finawaken-portfolio": {
      "type": "http",
      "url": "https://mcp.portfolio.finawaken.com/"
    }
  }
}

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 26, 2026

Score

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

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • 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.