Mossgate Mcp

dev.mossgatePublished by mossgate.devv0.1.1Updated Oct 24, 2026

mcp stdio server exposing mossgate trust and rue render apis with x402 usdc payment

VerifiedSTDIODesktop onlyFinanceSecurity & MonitoringMedia & Design

Overview

AI-generated overview

Exposes paid Mossgate trust and Rue render APIs to an MCP agent, with each tool call settled in USDC on Base.

What you can do
A local stdio MCP server that wraps two paid HTTP APIs. It offers token_verdict, wallet_profile and token_report for token and wallet risk checks, plus render, which turns a URL or HTML into a PDF, PNG or JPEG returned as base64. Payment is handled per call through x402 v2 in USDC on Base, signed gaslessly by a funded wallet.
When to use it
Use it when an assistant needs on-demand token or wallet risk checks, or needs to render web pages or HTML into documents and images, and you are willing to fund a wallet that pays per call. It suits agent workflows where paid API access is acceptable.
Requirements
Node.js 18 or newer, run locally over stdio by an MCP client (npm package mossgate-mcp, or npx). A funded EVM wallet private key must be supplied as the environment variable MOSSGATE_BUYER_PK, holding USDC on Base; no ETH is needed for gas. Optional overrides: MOSSGATE_RPC, MOSSGATE_TRUST_URL, MOSSGATE_RENDER_URL. Network access to the Mossgate APIs is required.
Before you install
MOSSGATE_BUYER_PK is a private key for a wallet holding real funds; anyone who obtains it can spend that balance, so keep it out of version control and use a dedicated, low-balance wallet. Every tool call spends USDC automatically, so costs accrue without a per-call confirmation. Requests send the queried addresses, URLs or HTML to third-party Mossgate endpoints.

Installation

In SourceWeft

  1. Open Mossgate Mcp 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

mossgate-mcp

a model context protocol (mcp) stdio server that exposes two live paid apis to any mcp-enabled agent:

  • mossgate trust (https://api.mossgate.dev) token and wallet risk checks
  • rue render (https://rue.mossgate.dev) url/html to pdf/png/jpeg

payment is x402 v2, usdc on base. the operator who runs this server funds a wallet, and every tool call spends a little usdc from it. the wallet signs an eip-3009 authorization gaslessly, so it needs only usdc, no eth for gas.

tools

  • token_verdict(address, chain=base) quick risk verdict for a token contract
  • wallet_profile(address, chain=base) behavioural risk profile for a wallet
  • token_report(address, chain=base) full token report
  • render(url|html, format=pdf|png|jpeg) render a page, returns a base64 file

install

sh
cd mcp-servernpm install

node 18+ is required.

fund the wallet

  1. create or reuse an evm wallet (any tool that gives a 0x private key).
  2. send it usdc on base (contract 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913). a few dollars covers many calls. no eth is needed, gas is sponsored by the facilitator.
  3. export the private key as an env var (never commit it):
sh
export MOSSGATE_BUYER_PK=0xyourprivatekey

optional overrides: MOSSGATE_RPC (base rpc url), MOSSGATE_TRUST_URL, MOSSGATE_RENDER_URL.

run standalone

sh
MOSSGATE_BUYER_PK=0x... node index.js

the server speaks mcp over stdio. it is meant to be launched by an mcp client, not used by hand.

claude desktop / mcp client config

add this to your mcp client config (for claude desktop: ~/.config/Claude/claude_desktop_config.json on linux, or ~/Library/Application Support/Claude/claude_desktop_config.json on macos):

json
{    "mcpServers": {        "mossgate": {            "command": "node",            "args": ["/absolute/path/to/products/mcp-server/index.js"],            "env": {                "MOSSGATE_BUYER_PK": "0xyourprivatekey"            }        }    }}

restart the client. the four tools appear and each call is paid automatically from the funded wallet.

verify it starts (no paid calls)

this lists the tools over stdio without touching the apis or spending anything:

sh
printf '%s\n' \'{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"probe","version":"0"}}}' \'{"jsonrpc":"2.0","method":"notifications/initialized"}' \'{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' \| node index.js

run without cloning

this package is on npm, so agents and clients can run it via npx with no clone or install. set the command to npx and args to ["-y", "mossgate-mcp"] in the client config:

json
{    "mcpServers": {        "mossgate": {            "command": "npx",            "args": ["-y", "mossgate-mcp"],            "env": {                "MOSSGATE_BUYER_PK": "0xyourprivatekey"            }        }    }}

Source: README.md at commit 92b12fe

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% 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
  • License10 pts

    Declare a license in the repository or the registry entry.