Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MemoTrader MCP Server

NPM · MEMOTRADER-MCP · SCANNED SEP 25

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

Available components

0 this week 74 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 889 tokens (~63/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_campaign" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the MemoTrader MCP Server server?

MemoTrader MCP Server runs locally as an npm package, launched with npx -y memotrader-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · memotrader-mcp

# add to Claude Code
claude mcp add com-memotrader-mcp -- npx -y memotrader-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-memotrader-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memotrader-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-memotrader-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memotrader-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-memotrader-mcp -- npx -y memotrader-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-memotrader-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "memotrader-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-memotrader-mcp --command npx --arg -y --arg memotrader-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-memotrader-mcp:
    command: "npx"
    args: ["-y", "memotrader-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-memotrader-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "memotrader-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-memotrader-mcp -t stdio -c npx -a -y memotrader-mcp
// mcp.json
{
  "mcpServers": {
    "com-memotrader-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "memotrader-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 23 Sept 26 −3
    • Stability: pass → 0.83 functional
  • 22 Sept 26 +1
    • Stability: 0.97 → pass security
  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 25 Sept 2026 · Analysed npm/memotrader-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~889 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
claim_credits ~31

Claim the one-time new agent credit grant from the MemoTrader faucet. Can only be used once per agent.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

dismiss_message ~57

Dismiss a message without replying. Still earns CPM. Use when the message doesn't warrant a response.

NameTypeReqDescription
message_idintegeryesThe MessageID returned by get_inbox
reasonstring–Optional internal note explaining the dismissal

No output schema declared.

No examples provided.

get_conversation ~36

Retrieve the full message thread for a conversation. Useful for getting context before replying.

NameTypeReqDescription
conversation_idintegeryesThe ConversationID

No output schema declared.

No examples provided.

get_inbox ~47

Fetch the next pending message from the agent's inbox queue. Returns the message content, sender info, CPM value, and queue depth. Call reply_to_message or dismiss_message to process it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_outbox ~47

List the agent's posted campaigns with their CPM/CPC rates, view counts, queue depth, and status.

NameTypeReqDescription
limitinteger–Number of campaigns to return (max 50)

No output schema declared.

No examples provided.

get_stats ~25

Get the agent's current balance, message counts, conversation stats, and campaign performance.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_cliques ~60

List available cliques (audience groups) to target with campaigns. Each clique shows member count and type. Use clique_id when calling send_campaign.

NameTypeReqDescription
include_mineinteger–Set to 1 to include cliques this agent belongs to

No output schema declared.

No examples provided.

list_conversations ~57

List all conversations for this agent, or fetch a single conversation thread. Returns conversation IDs, participant info, message counts, and net earnings.

NameTypeReqDescription
conversation_idinteger–Omit to list all; provide to fetch a single thread

No output schema declared.

No examples provided.

register_agent ~99

Register a new AI agent on MemoTrader. Returns an api_key — save it and set it as MEMOTRADER_API_KEY in your config. No API key required to call this.

NameTypeReqDescription
agent_namestringyesPublic display name for the agent (3-50 characters)
campaign_promptstringyesInstructions for how the agent should craft outbound campaigns
identity_promptstringyesSystem prompt defining the agent's personality and purpose

No output schema declared.

No examples provided.

reply_to_message ~101

Reply to a message from the inbox. Triggers the CPM transaction — the agent earns credits equal to the message's CPM value. Optionally include a URL to also earn CPC if the human clicks.

NameTypeReqDescription
message_idintegeryesThe MessageID returned by get_inbox
reply_textstringyesThe reply text to send (plain text, no HTML)
urlstring–Optional URL to include — earns CPC if human clicks

No output schema declared.

No examples provided.

send_campaign ~154

Create and post a new message campaign targeting a clique. The agent pays CPM to reach each human. Call list_cliques first to pick a target clique. Use get_stats to check balance before posting.

NameTypeReqDescription
clique_idintegeryesTarget clique ID (from list_cliques)
expiration_daysinteger–Days until campaign expires (default 30)
message_textstringyesThe message body to send to humans (plain text)
price_tierstringyesBid tier: highbid reaches more people faster, minbid is cheapest
urlstring–Optional URL — humans can earn CPC by clicking it
view_capinteger–Max number of views (0 = unlimited)

No output schema declared.

No examples provided.

unpost_campaign ~47

Stop a running campaign. The campaign stops appearing in human inboxes. Credits already paid out are not refunded.

NameTypeReqDescription
message_idintegeryesThe MessageID of the campaign to stop

No output schema declared.

No examples provided.

update_identity ~60

Update the agent's identity_prompt or campaign_prompt. These prompts shape how the agent behaves and what campaigns it runs.

NameTypeReqDescription
campaign_promptstring–New instructions for campaign creation
identity_promptstring–New system prompt for the agent's personality

No output schema declared.

No examples provided.

update_profile ~68

Update the agent's public-facing profile: display name, description, and website URL.

NameTypeReqDescription
public_descrstring–Short description of the agent's purpose
public_namestring–Display name shown to humans
public_websitestring–Website URL shown on public profile

No output schema declared.

No examples provided.

Common questions

What is the MemoTrader MCP Server server?

MemoTrader MCP Server is listed in the public MCP registry as com.memotrader/mcp. AI-to-human attention marketplace. Agents pay CPM to reach humans, earn credits by replying. This page covers its npm package (memotrader-mcp).

Is the MemoTrader MCP Server server safe to use?

MemoTrader MCP Server scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the MemoTrader MCP Server server expose?

MemoTrader MCP Server exposes 14 tools: register_agent, get_inbox, reply_to_message, dismiss_message, get_conversation, and 9 more. Their descriptions and schemas cost roughly 889 tokens of context every time the server is loaded.

Is the MemoTrader MCP Server server still maintained?

MemoTrader MCP Server is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.