Web3 Sentiment

io.github.EvozimPublished by GitHub account Evozimv1.0.0Updated Oct 24, 2026

Web3 social sentiment aggregator analyzing crypto trends.

The publisher's own server: Web3TV MCP Server

VerifiedSSEWeb executableWeb Search & ScrapingFinance

Overview

AI-generated overview

A remote MCP server that aggregates Web3 social sentiment to help an assistant analyze crypto trends.

What you can do
Aggregate Web3 social sentiment data to analyze crypto trends and market mood. Premium settlement is handled through a payment-signature header, so paid access appears to be part of the service. No individual tools are documented, so the exact operations are not described.
When to use it
Useful when an assistant needs a read on social sentiment around crypto assets or Web3 topics, for example to gauge market mood or track trending narratives.
Requirements
A remote SSE endpoint; no local runtime or package is needed. Premium settlement requires a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. No other accounts or environment variables are declared.
Before you install
The payment-signature header is a secret signing credential tied to an on-chain payment authorization; treat it as sensitive and avoid exposing it. Premium use involves payment, so spending may occur. Sentiment data comes from a third party and should be verified before acting on it.

Installation

In SourceWeft

  1. Open Web3 Sentiment in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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/io.github.Evozim%2Fweb3-sentiment/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": {
    "web3-sentiment": {
      "type": "sse",
      "url": "https://web3-sentiment-mcp.vercel.app/api/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.0LatestSep 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.

Other Web3 integrations