// SCAN REPORT

Vetroscope MCP

20 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 3 Jul 2026

0 can modify or destroy data

20 read-only

20 tools total

Community server · catalogue entry verified 03/07/2026

How to control Vetroscope MCP ↓

TOOL MAP

What Vetroscope MCP exposes to your agents

Read (20) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Vetroscope MCP

PolicyLayer is an MCP gateway — it sits between your AI agents and Vetroscope MCP, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "get_app_breakdown": {
    "limits": [
      {
        "counter": "get_app_breakdown_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Vetroscope MCP — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON VETROSCOPE →

Instant setup, no code required.

FULL CATALOGUE

All 20 Vetroscope MCP tools

READ 20 tools

Read get_app_breakdown Per-project breakdown for a single app over a period, with sub-projects nested when present (e.g. individual Y Read get_app_stats Deeper statistics for a single app: lifetime totals (days active, first/last seen, average per active day), pe Read get_calendar Dense per-day series of active and passive seconds for a period. Default period is Read get_category_breakdown Rolls up app totals into broad categories (editor, browser, adobe, communication, gaming, productivity, creati Read get_current_status Most recent activity: what app / project / sub-project the tracker last logged, how many seconds ago, and whet Read get_device_breakdown Time per device for users who run Vetroscope across multiple machines (or paired with the browser extension). Read get_focus_heatmap Returns a dense 168-cell grid (7 weekdays × 24 hours) of active foreground seconds. Reveals when you usually d Read get_goal_achievements Historical record of goals the user hit — one row per (goal, day). Each row carries a snapshot of the goal as Read get_goals_progress Current progress on the user Read get_listening_history Top tracks and top artists across native music apps and browser music sites for the period, plus per-day liste Read get_media_links Lists canonical deep-links Vetroscope captured for media the user actually played — Spotify Read get_music_split Splits the period Read get_report Aggregate Vetroscope time report for a period: total active seconds, top apps, and top projects (with sub-proj Read get_sessions Continuous activity blocks reconstructed from the raw 30s entries — the natural grain for Read get_tag_breakdown Time-spent report for a single tag over a period: top apps and projects under the tag, daily series, active/pa Read get_tag_stats Deeper statistics for a single tag — the tag counterpart to get_app_stats. Lifetime totals (days active, first Read list_markers User-placed markers on the Vetroscope timeline (timestamp, optional end_timestamp for regions, label, color, i Read list_projects Every (app, project) pair ever recorded with all-time totals, days active, and first/last seen. Optional case- Read query_entries Filtered list of raw tracking entries. Useful for digging into specific projects, tags, or finding what window

FAQ

Questions about Vetroscope MCP

Is the Vetroscope MCP server safe to use without restrictions? +

The Vetroscope MCP server is primarily read-only with 20 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Vetroscope MCP server expose? +

20 tools across 1 categories: Read. 20 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Vetroscope MCP? +

Register the Vetroscope MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Vetroscope MCP tool call.

Deterministic rules across all 20 Vetroscope MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON VETROSCOPE →

Instant setup, no code required.

20 Vetroscope MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.