Ramaris App

io.github.ramaris-appPublished by GitHub account ramaris-appv0.1.4Updated Oct 24, 2026

On-chain wallet analytics and trading strategies on Base for AI assistants

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server giving AI assistants on-chain wallet analytics and trading strategies on the Base network, authenticated with a Ramaris API key.

What you can do
  • Provides on-chain wallet analytics for the Base network.
  • Supports trading strategies built on that wallet data.
  • Exposes these capabilities to an AI assistant as MCP tools over a local stdio process.
  • No individual tools are documented in the supplied listing, so exact operations are not specified.
When to use it
Useful when you want an assistant to look at Base wallet activity and reason about trading strategies without leaving the chat. Only worth adding if you already use Ramaris and have API access.
Requirements
Runs as a local process via the npm package @ramaris/mcp-server over stdio, so Node.js is needed. Requires a Ramaris API key supplied in the RAMARIS_API_KEY environment variable, obtained from the provider's API access page. Desktop client only; not available as a web-hosted server.
Before you install
The server requires an API key stored in RAMARIS_API_KEY; treat it as a secret and keep it out of shared configs. It deals with on-chain wallets and trading strategies, so any actions it can take may affect real funds or expose wallet data. Review what it sends to the Ramaris service before use.

Installation

In SourceWeft

  1. Open Ramaris App 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. v0.1.4LatestSep 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.