invisit

dev.invisitPublished by invisit.devOfficial publisherv1.0.0Updated Nov 5, 2026

Cookieless web analytics: traffic, sources, AI referrals, funnels, heatmaps and web vitals.

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP server for Invisit, a cookieless web analytics service, letting an assistant read traffic, sources, AI referrals, funnels, heatmaps and web vitals.

What you can do
  • Read website traffic and visitor metrics from an Invisit account
  • Inspect traffic sources and AI referral data
  • Review funnel performance and conversion steps
  • Look at heatmap and web vitals data for pages
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when you want an assistant to answer questions about a site's analytics — where visitors come from, how funnels convert, or how pages perform on web vitals — without leaving the chat or exporting reports by hand.
Requirements
A remote endpoint at app.invisit.dev over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared. An Invisit account with analytics data for the site is implied.
Before you install
Access is granted through OAuth to an Invisit account, so the assistant can read that account's analytics data; review the scopes granted during sign-in. No write, payment or secret-handling behavior is described in the available information.

Installation

In SourceWeft

  1. Open invisit 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/dev.invisit%2Finvisit/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": {
    "invisit": {
      "type": "http",
      "url": "https://app.invisit.dev/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. v1.0.0LatestNov 5, 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.