Fenn

sh.fennPublished by fenn.shOfficial publisherv1.0.0Updated Nov 2, 2026

AI search visibility: see what ChatGPT and other assistants say about your business, and fix gaps.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingBusiness & Commerce

Overview

AI-generated overview

Fenn is a remote MCP server that lets an assistant read your AI search visibility report, draft fixes, and hand off publishing for your approval.

What you can do
  • Read your AI visibility report, how each tracked question is answered, rank checks, keyword gaps, site audit issues and backlinks
  • Review suggested fixes, their prompts, and your fix tasks
  • Start tracking a new question or keyword
  • Draft a fix without changing anything on your site
  • Request execution or publishing of a fix, which returns a link for you to approve in Fenn
When to use it
Useful when you want an assistant to check what ChatGPT and other AI assistants say about your business, find gaps, and prepare website fixes while keeping approval of any live change in your own hands.
Requirements
Remote Streamable HTTP endpoint; nothing to install. Requires a Fenn account and API key sent in the Authorization header as a Bearer token, created in Fenn under Settings, MCP.
Before you install
The API key is a secret sent in the Authorization header; keep it out of shared logs and configs. Read tools are described as free, but drafting and tracking create records in your Fenn account. Executing or publishing a fix is gated: the agent only returns a link and the change proceeds after you approve it in Fenn.

Installation

In SourceWeft

  1. Open Fenn 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/sh.fenn%2Ffenn/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": {
    "fenn": {
      "type": "http",
      "url": "https://api.fenn.sh/mcp"
    }
  }
}

README

Fenn MCP server

Connect your AI agent to Fenn, which checks what ChatGPT and other AI assistants tell your customers about your business. When you're left out, Fenn drafts what your website needs, and you approve every change.

This is a remote MCP server. There is nothing to install or run.

https://api.fenn.sh/mcp

Transport: Streamable HTTP. Auth: a Fenn API key sent as Authorization: Bearer aeo_sk_.... Make one in Fenn under Settings → MCP (https://app.fenn.sh/settings/mcp).

Connect

Claude Code

bash
claude mcp add fenn --transport http https://api.fenn.sh/mcp \  -H "Authorization: Bearer aeo_sk_..."

Cursor, VS Code, Claude Desktop and other MCP clients: add a server with the URL above and the Authorization header set to your API key.

What your agent can do

Every tool says on its first line which kind it is:

  • Read (free): your AI visibility report, how each tracked question is answered, rank checks, keyword gaps, site audit issues, backlinks, suggested fixes and their prompts, and your fix tasks
  • Draft: start tracking a question or keyword, and draft a fix; nothing changes on your site
  • Gated: executing a fix or publishing never happens from the agent. The call returns a link, and the change goes ahead only when you approve it in Fenn.

Links

Source: README.md at commit fb1e362

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. v1.0.0LatestOct 18, 2026

Score

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

    Declare a license in the repository or the registry entry.