1. Conduid
  2. Developer Tools
  3. VibeTrack AI Coding Behavior Analyzer
MCP server · Developer Tools

VibeTrack AI Coding Behavior Analyzer

by · github.com/Manavarya09/VibeTrack-AI-Coding-Behavior-Analyzer

A tool that tracks how people use AI coding tools and detects addictive / deep engagement patterns

Unclaimed last commit 6 months ago devtools
InstallView source
34Low

Scored 4 months ago · breakdown

About VibeTrack AI Coding Behavior Analyzer

VibeTrack AI Coding Behavior Analyzer is an MCP server published by Manavarya09 in the Developer Tools category: a tool that tracks how people use AI coding tools and detects addictive / deep engagement patterns.

The repository has 8 stars and 0 forks, with the last commit 6 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/Manavarya09/VibeTrack-AI-Coding-Behavior-Analyzer

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about VibeTrack AI Coding Behavior Analyzer

Powered by Claude · Grounded in docs

I know everything about VibeTrack AI Coding Behavior Analyzer. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About VibeTrack AI Coding Behavior Analyzer

How do I install VibeTrack AI Coding Behavior Analyzer?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is VibeTrack AI Coding Behavior Analyzer safe to use with an AI agent?

Its trust score is 34 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is VibeTrack AI Coding Behavior Analyzer still maintained?

The last commit was 6 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.