Fensory

com.fensoryPublished by fensory.comOfficial publisherv1.1.0Updated Oct 24, 2026

Trading MCP server for AI agents, with live market data, account reads and controlled execution.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote trading MCP server that gives AI agents live market data, account reads and controlled order execution.

What you can do
  • Retrieve live market data for trading decisions.
  • Read account information such as balances and positions.
  • Execute trades under the server's stated controls.
  • No tool list is published, so the exact commands available are not documented here.
When to use it
When an assistant needs to work with live market data, inspect a trading account, or place trades through a controlled execution layer rather than manual clicks.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. OAuth authentication is required, so an account with the provider and a completed OAuth sign-in are needed. No environment variables or headers are declared.
Before you install
The server can execute trades, which moves real money and carries financial risk; review any confirmation or limit controls before enabling it. OAuth grants the server access to a trading account, so check the scopes requested. Account and trading data is shared with the provider's hosted service.

Installation

In SourceWeft

  1. Open Fensory 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.fensory%2Ffensory/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": {
    "fensory": {
      "type": "http",
      "url": "https://mcp.fensory.com/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

2
  1. v1.1.0LatestOct 9, 2026
  2. v1.0.0Sep 16, 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.