MCP.Market

Vidalytics MCP server

online · 100% uptime
by vidalytics.com·com.vidalytics/mcp·v0.4.1
No reviews yet

Manage your Vidalytics videos and analytics from your AI assistant.

A98/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A98/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Vidalytics yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vidalytics tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 245ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 30 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 98/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vidalytics compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
98/100
higher than 99% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
286 ms
faster than 49% of 30,031 servers

Install Vidalytics in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://api.vidalytics.com/public/v1/mcp
Add to Cursor

What the publisher says

From the Vidalytics repository's README, as published. We do not edit it. Read it on GitHub

@vidalytics/mcp

One-command setup that connects your AI coding assistant to Vidalytics video analytics data via the Model Context Protocol.

Works with Claude (CLI & Desktop), Windsurf, Cursor, and any other MCP-compatible client.

Setup

npx @vidalytics/mcp install

That's it. The installer detects which AI clients you have installed, lets you pick which ones to configure, and wires them up. Restart the client — a browser window will open for OAuth authorization on first use.

Cursor

Or via the installer:

npx @vidalytics/mcp install --client cursor

Or manually — add this to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "vidalytics": {
      "url": "https://api.vidalytics.com/public/v1/mcp"
    }
  }
}

Restart Cursor. On first use a browser window opens for OAuth authorization with your Vidalytics account — no API key or environment variables to set.

What it does

  • Detects installed MCP clients (Claude CLI, Claude Desktop, Windsurf, Cursor) by checking config files, app directories, binaries in $PATH, and app bundles (e.g. /Applications on macOS)
  • Presents an interactive checklist (detected clients pre-selected) so you configure exactly the ones you want — or pick them non-interactively with --client
  • Adds Vidalytics as an MCP server in each selected client's config
  • Verifies after writing: the config is valid and the MCP server is reachable
  • Non-interactive terminals (CI) and any explicit selection flag (--client, --all, --yes) skip the checklist and behave predictably

Available tools

Once connected, your AI assistant gains access to:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vidalytics: common questions

Is Vidalytics MCP server safe?
Yes, by our scan: it is graded A (98/100). Read the Vidalytics safety report
How do I install Vidalytics?
It runs remotely at api.vidalytics.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Vidalytics need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Vidalytics maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.4.1.
Is Vidalytics up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Vidalytics compare with other MCP servers?
safety score 98/100 (higher than 99% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 286 ms (faster than 49% of 30,031 servers). Full comparison.