LION - Trend Intent MCP + Marketplace Visibility Audit

app.netlify.gleaming-cassata-d41682Published by gleaming-cassata-d41682.netlify.appOfficial publisherv1.1.1Updated Oct 25, 2026

x402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A remote MCP endpoint offering a trend feed and a marketplace visibility audit, paid per call with USDC on Base and no API key.

What you can do
Retrieve a trend feed of intent or trend data for an assistant to work with. Run a marketplace visibility audit. Access is metered per call through x402 payments in USDC on Base, with no API key and no PII required.
When to use it
Worth considering when you want trend signals or a marketplace visibility check inside an assistant and are set up to pay per request in USDC on Base. Less suitable if you need free access, a fixed subscription, or a documented tool list before committing.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, API key, environment variable or header is declared. A wallet able to make USDC payments on the Base network is implied by the x402 payment model.
Before you install
Each call is paid in USDC on Base, so usage spends real funds and costs should be checked before connecting. The listing declares no tools, no README and no authentication details, so the exact data returned and its handling cannot be verified from the listing.

Installation

In SourceWeft

  1. Open LION - Trend Intent MCP + Marketplace Visibility Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.netlify.gleaming-cassata-d41682%2Flion-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "lion-trend-intent-marketplace-visibility": {
      "type": "http",
      "url": "https://gleaming-cassata-d41682.netlify.app/api/mcp?src=mcpregistry_domain_v1_1"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.1.1LatestSep 16, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.