LogoScout

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

Brand trademark scanner and intellectual property auditor.

The publisher's own server: Official Logo.dev MCP

VerifiedSSEWeb executableBusiness & Commerce

Overview

AI-generated overview

LogoScout is a remote MCP server for brand trademark scanning and intellectual property auditing, with premium features settled via a payment signature.

What you can do
Scan brands for trademark conflicts and audit intellectual property exposure through the server's tools, which are not itemized in the listing. Premium settlement is handled through a payment-signature header carrying a Base64-encoded EIP-3009 TransferWithAuthorization signature. The server is reached as a remote endpoint over SSE rather than installed locally.
When to use it
Consider it when an assistant needs to check brand names or logos for trademark conflicts, or to audit intellectual property exposure, and a remote hosted service is acceptable.
Requirements
A remote MCP connection to the hosted endpoint over SSE; no local runtime or package is needed. Premium settlement requires a payment-signature header containing a Base64-encoded EIP-3009 TransferWithAuthorization signature. No authentication is declared.
Before you install
Premium use involves payment: the payment-signature header carries a signed transfer authorization, so treat it as a sensitive credential and be aware that using it can move funds. The server is third-party hosted, so queries and any submitted brand data go to that operator. Tool behavior is not documented in the listing.

Installation

In SourceWeft

  1. Open LogoScout 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%2Flogoscout/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": {
    "logoscout": {
      "type": "sse",
      "url": "https://logoscout-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 Logo integrations