Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
mite is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
100/100
trust score
17
downloads a day
local
runs on your machine
653
downloads in 30d
What it does
mite time tracking: server-side reports, time entries, master data. Read-only by default.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'MITE_ACCOUNT=${MITE_ACCOUNT}' --env 'MITE_API_KEY=${MITE_API_KEY}' --transport stdio stefan39-mite-mcp '--' npx -y mite-mcp-server
# 2 — ask your agent for something these tools do
# mite_create_time_entry, mite_get_time_entry, mite_list_time_entries and 8 more
It needs MITE_ACCOUNT, MITE_API_KEY: this reads them from your environment, so export them first.
mite costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 1 server
Stefan391 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts mite as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads MITE_ACCOUNT (mite account name, the subdomain of <account>.mite.de), MITE_API_KEY (Personal mite API key) from your environment each time it starts the server, so the value stays out of its config: export them in your shell profile (macOS, Linux), or run setx MITE_ACCOUNT …, setx MITE_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'MITE_ACCOUNT=${MITE_ACCOUNT}' --env 'MITE_API_KEY=${MITE_API_KEY}' --transport stdio stefan39-mite-mcp '--' npx -y mite-mcp-serverReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: MITE_ACCOUNT — mite account name, the subdomain of <account>.mite.de; MITE_API_KEY — Personal mite API key. You set them in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Creates a new time entry for the user of the API key; use it to book time, mite_update_time_entry to change an existing entry and mite_start_tracker to run a timer on one. Returns the created entry with its id, hours (not minutes) and revenue in currency units (null if none). Needs mode write…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date_at | no | Date of the entry as YYYY-MM-DD, e.g. 2026-10-29. Default: today. | |
| hours | no | — | |
| note | no | — | |
| project_id | no | — | |
| service_id | no | — | |
| dry_run | yes | — |
Fetches one time entry from mite by its id; use it when the id is known, otherwise find entries with mite_list_time_entries. Returns date, hours, revenue in currency units (null if none), billable and locked flags, customer, project, service, user and note. Fails with "not found" if no time…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | Id of the time entry, e.g. 1234567. Required. |
Lists single time entries from mite for a period, newest first, optionally filtered by customer, project, service, user, billable or locked. Use it to find individual entries or their ids; for totals use mite_report, for one known entry use mite_get_time_entry. Each row has hours, revenue in…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | array | no | — |
| project_id | array | no | — |
| service_id | array | no | — |
| user_id | array | no | — |
| billable | boolean | no | true = only billable, false = only non-billable, e.g. true. Default: both. |
| locked | boolean | no | true = only locked, false = only unlocked, e.g. false. Default: both. |
| limit | integer | no | Entries per page, 1–1000, e.g. 50. Default: 100. |
| page | integer | no | Page number, starting at 1, e.g. 2. Default: 1. |
Aggregated report from mite: hours, revenue and share of hours, grouped by 1 to 3 of … for a period, on the mite server so whole years work. For the fixed project-by-month view use mite_report_projects_by_month, for billable share use mite_report_billable_ratio, for budgets use…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_by | array | yes | — |
Billable hours, non-billable hours and the billable share in percent for a period, optionally per …, aggregated on the mite server. For revenue or other groupings use mite_report. Returns hours and a ratio in percent with one decimal, per group and as a total. Read-only, no paging, default…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group_by | string | no | — |
Budget, consumption, remaining budget and percent used per project over the whole project life, not for a period; for hours or revenue in a period use mite_report. Minute budgets are in hours, cent budgets in currency units (consumption = revenue); budget, remaining and percent are null for…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | array | no | — |
Aggregated report from mite: hours and revenue per project and month for a period, grouped on the mite server so whole years work without reading single entries. For other groupings or totals use mite_report; for single entries use mite_list_time_entries. Returns rows of month (YYYY-MM),…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| customer_id | array | no | — |
| project_id | array | no | — |
| service_id | array | no | — |
| user_id | array | no | — |
| billable | boolean | no | true = only billable entries, false = only non-billable entries. Default: both. |
Starts the mite time tracker on an existing time entry, so mite counts the running time onto it; use mite_tracker_status to see what is running and mite_create_time_entry first if no entry exists yet. Returns running: true and the time entry id; the hours are not returned, read them later…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | — |
Stops the mite time tracker on a time entry, which keeps the time counted so far; use mite_tracker_status to see which entry is running and mite_start_tracker to start one. Returns running: false and the time entry id; the hours are not returned, read them with mite_get_time_entry. Needs…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | — |
Tells whether the mite time tracker is currently running for the key's user and, if so, on which time entry. Returns running and, when it runs, time_entry_id, the start time since and minutes, the entry's total so far in minutes. Read-only and takes no input; to look at that entry in full…
No parameter schema on file.
Shows the mite account, the user behind the API key and its role, plus the mode and tools this server offers. Call it first to learn what you are allowed to do; for projects use mite_list_projects, for customers mite_list_customers. Returns account name, title and currency, the user id, name…
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install mite or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 100 / 100
Release 1.0.1 · scanned 30 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest3e1eeff11b0bed82cf83adf5b471d2e149941ac1abbe76ea03fb565ce388a867
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
No tool surface was enumerated, so there is nothing to attribute a capability to.
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest3e1eeff11b0bed82
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.0.1. Pin a release below and the command asks for exactly that one.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish mite can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.