Xeve MCP Server

xeve-mcp-server npm v1.0.0

Published by xeveio — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
C
77/100
Last scanned
Trust
C · 77/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
C Why this grade threat 78 − adoption risk = 77/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 22 = 78. What the published surface and source actually contain:

PointsWhat was foundCategory
−22 Hardcoded JSON Web Token in server code MTC-SRC-008 exfiltration

2. Client adoption risk — 78 − 1 = 77. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Grade capped: 1 confirmed high finding → grade capped at C. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Hardcoded JSON Web Token in server code (dist/index.js)MTC-SRC-008

A live-looking JSON Web Token is hardcoded in `dist/index.js:7`. Secrets in source ship to everyone who installs the package and are a direct credential leak.

Evidence: JSON Web Token: eyJh…(redacted)

Fix: Remove the secret, rotate it, and load credentials from the environment or a secret store.

Location: server dist/index.js

Tools 24

Each tool and what it can reach — statically extracted from the published source.

  • compare_periodsno sensitive capability
  • get_app_usageno sensitive capability
  • get_calendarno sensitive capability
  • get_coding_summaryno sensitive capability
  • get_context_switchesno sensitive capability
  • get_correlationsno sensitive capability
  • get_daily_trendno sensitive capability
  • get_devicesno sensitive capability
  • get_focus_streaksno sensitive capability
  • get_github_activityno sensitive capability
Show 14 more tools ↓
  • get_goalsno sensitive capability
  • get_health_summaryno sensitive capability
  • get_heart_rateno sensitive capability
  • get_hourly_activityno sensitive capability
  • get_insightsno sensitive capability
  • get_locationsno sensitive capability
  • get_meetingsno sensitive capability
  • get_music_historyno sensitive capability
  • get_notificationsno sensitive capability
  • get_productivity_summaryno sensitive capability
  • get_recent_sessionsno sensitive capability
  • get_streak_datano sensitive capability
  • get_website_breakdownno sensitive capability
  • get_whoop_recoveryno sensitive capability

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.0 latest C 77/100 1 1.8.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: C · 77/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/xeve-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/xeve-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/xeve-mcp-server"><img src="https://mcptrustchecker.com/registry/xeve-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/xeve-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan xeve-mcp-server --online

Use the free API → How scoring works

More in Developer Tools