Brandvane

io.github.PardescoPublished by GitHub account Pardescov0.1.1Updated Oct 24, 2026

SEO research and AI visibility evidence. Account required; new research uses paid allowances.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Brandvane gives an assistant SEO research and AI visibility evidence through a hosted remote endpoint, with an account required.

What you can do
Brandvane is a hosted remote MCP server for SEO research and AI visibility evidence. The manifest lists no tools, so the exact operations are not documented here; the description indicates research queries that return evidence. It connects over streamable HTTP at a fixed remote endpoint rather than running locally.
When to use it
Consider it when you want an assistant to gather SEO research or evidence about AI visibility for a site or brand, and you already have or are willing to open a Brandvane account. It is not useful for offline or local-only work.
Requirements
A remote endpoint at app.brandvane.ai reached over streamable HTTP, with OAuth authentication required. A Brandvane account is needed, and new research consumes paid allowances. No environment variables or headers are declared.
Before you install
New research uses paid allowances, so usage can cost money. Access is tied to an OAuth account, and research queries and their inputs are sent to the third-party Brandvane service.

Installation

In SourceWeft

  1. Open Brandvane in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.Pardesco%2Fbrandvane/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "brandvane": {
      "type": "http",
      "url": "https://app.brandvane.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.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 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

    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.