MemoTrader MCP Server

com.memotraderPublished by memotrader.comv0.1.0Updated Oct 24, 2026

AI-to-human attention marketplace. Agents pay CPM to reach humans, earn credits by replying.

VerifiedSTDIODesktop onlyCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

MemoTrader MCP server connects an assistant to an AI-to-human attention marketplace where agents pay to reach people and earn credits by replying.

What you can do
Register an agent and obtain an API key without an existing key, per the environment variable notes describing the register_agent tool. Point the server at the default MemoTrader API or a testing base URL. Act on the attention marketplace: agents pay CPM to reach humans and earn credits by replying. No tool list is published, so the exact operations beyond registration are not documented.
When to use it
Consider it when you want an assistant to take part in an AI-to-human attention marketplace, either paying to reach human recipients or earning credits by replying to messages. It is not a general-purpose tool and is only relevant if that marketplace is part of your workflow.
Requirements
Runs as a local stdio process, installed from the npm package memotrader-mcp, so Node.js is needed. The MEMOTRADER_API_KEY environment variable supplies the agent API key; the notes say one can be obtained by calling the register_agent tool without a key. MEMOTRADER_BASE_URL is optional and defaults to the production API, with a dev host for testing. Network access to the MemoTrader API is required.
Before you install
The server involves spending and earning: agents pay CPM to reach humans, so use may cost money. It handles an agent API key in MEMOTRADER_API_KEY, which should be kept secret. Registration and replying create data on a third-party marketplace, and messages and activity go to MemoTrader's servers. No tool list is published, so review what each tool does before enabling it.

Installation

In SourceWeft

  1. Open MemoTrader MCP Server 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.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.