Thryx Portfolio

io.github.lordbasilaiassistant-sudoPublished by GitHub account lordbasilaiassistant-sudov1.0.0Updated Oct 24, 2026

Read-only MCP server for the THRYX onchain portfolio (14 contracts on Base mainnet).

The publisher's own server: PortfolioFit

VerifiedSTDIODesktop onlyDatabasesFinance

Overview

AI-generated overview

Read-only access to the THRYX onchain portfolio, covering 14 contracts on Base mainnet.

What you can do
This local MCP server exposes read-only tools for inspecting the THRYX onchain portfolio, which the description says spans 14 contracts on Base mainnet. It queries Base mainnet through an RPC endpoint to retrieve portfolio data. No write, transfer, or transaction-signing tools are described.
When to use it
Useful when an assistant needs to look up THRYX portfolio state or contract data on Base mainnet without making changes. It suits read-only inspection and reporting rather than trading or contract administration.
Requirements
Runs as a local stdio process, installed from the npm package @thryx/portfolio-mcp-server, so Node.js is needed. Network access to Base mainnet is required. The optional environment variable BASE_RPC_URL can point to a custom Base mainnet RPC URL; otherwise a default public endpoint is used. No authentication is declared.
Before you install
The server is described as read-only, so it should not be expected to send transactions or move funds. It queries Base mainnet, and any RPC endpoint set through BASE_RPC_URL receives the requests, so a third-party provider may see them. No credentials or private keys are requested by the manifest.

Installation

In SourceWeft

  1. Open Thryx Portfolio in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

Other Portfolio integrations