Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
BigTime MCP by usefulapi 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.
93/100
tool-list score
24
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read staff, projects, clients, time, expenses and invoices; create time entries in BigTime.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bigtime-mcp-by-usefulapi https://bigtime.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# bigtime_list_staff, bigtime_get_staff, bigtime_list_projects and 21 more
BigTime MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 598 servers
usefulapi598 servers
25 categories
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. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bigtime-mcp-by-usefulapi https://bigtime.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
24 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.
List staff members (id = staff sid, name, email). Good first call. BigTime API: GET /staff.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| show_inactive | boolean | no | Include inactive records (default false). |
Get one staff member by staff sid. BigTime API: GET /staff/detail/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_sid | integer | yes | Staff sid (from bigtime_list_staff). |
| view | string | no | Detail level (default Basic). |
List projects (id, name, client, status). BigTime API: GET /project.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| show_inactive | boolean | no | Include inactive records (default false). |
Get one project by sid, with budget, dates and billing setup. BigTime API: GET /project/detail/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_sid | integer | yes | Project sid (from bigtime_list_projects). |
| view | string | no | Detail level (default Basic). |
List the staff assigned to a project. BigTime API: GET /project/team/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_sid | integer | yes | — |
List clients (id, name, client id). BigTime API: GET /client.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| show_inactive | boolean | no | Include inactive records (default false). |
Get one client by sid. BigTime API: GET /client/detail/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_sid | integer | yes | Client sid (from bigtime_list_clients). |
| view | string | no | Detail level (default Basic). |
List the tasks of one project. BigTime API: GET /task/listByProject/{ProjectSid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_sid | integer | yes | — |
| show_completed | boolean | no | Include completed tasks (default false). |
List the tasks assigned to one staff member. BigTime API: GET /task/ListByStaffer/{StaffSid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_sid | integer | yes | — |
| show_completed | boolean | no | Include completed tasks (default false). |
Get one task by sid. BigTime API: GET /task/detail/{TaskSid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_sid | integer | yes | — |
| view | string | no | Detail level (default Basic). |
List the time entries of one staff member in a date range. BigTime API: GET /time/Sheet/{staffsid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_sid | integer | yes | — |
| start_date | string | yes | — |
| end_date | string | yes | — |
| view | string | no | Use Detailed for all fields. |
List the time entries logged on one project in a date range. BigTime API: GET /time/ByProject/{Id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_sid | integer | yes | — |
| start_date | string | yes | — |
| end_date | string | yes | — |
| is_approved | boolean | no | Only approved (true) or unapproved (false) entries. |
| view | string | no | — |
Get one time entry by sid. BigTime API: GET /time/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| time_sid | integer | yes | — |
Get the hours per day for one staff member in a date range. BigTime API: GET /time/TotalByDay/{staffsid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_sid | integer | yes | — |
| start_date | string | yes | — |
| end_date | string | yes | — |
Get one expense entry by sid. BigTime API: GET /expense/detail/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| expense_sid | integer | yes | — |
List expense reports. BigTime API: GET /expense/reports.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| show_all | boolean | no | Show all reports, not only open ones. |
List issued invoices in a date range. BigTime API: GET /invoice/history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | — |
| end_date | string | yes | — |
List draft invoices, optionally in a date range. BigTime API: GET /invoice/drafts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | — |
| end_date | string | no | — |
Get one invoice by sid. BigTime API: GET /invoice/detail/{sid}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoice_sid | integer | yes | — |
List the invoices of one client in a date range. BigTime API: GET /invoice/GetInvoicesByClientId.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_sid | integer | yes | — |
| start_date | string | no | — |
| end_date | string | no | — |
List payments received in a date range. BigTime API: GET /payment/history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | yes | — |
| end_date | string | yes | — |
Get the definition (fields and filters) of a saved report. BigTime API: GET /report/detail/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | integer | yes | — |
Run a saved BigTime report and return its rows. Pass the report filters as a JSON object, for example {"DT_BEGIN":"2026-01-01","DT_END":"2026-01-31"}. Read only. BigTime API: POST /report/data/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| report_id | integer | yes | — |
| filters | object | no | Report filter values. |
WRITE: log time for a staff member on a project. Creates a new time entry in BigTime (it does not replace one). Set mark_submitted to submit it for approval at once. BigTime API: POST /time.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| staff_sid | integer | yes | Staff sid the time belongs to. |
| project_sid | integer | yes | Project sid to log against. |
| date | string | yes | Work date, yyyy-mm-dd. |
| hours | number | yes | Hours worked, for example 1.25. |
| notes | string | no | Notes for the entry. |
| task_sid | integer | no | Optional task sid on the project. |
| mark_submitted | boolean | no | Submit the entry for approval (default false). |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 BigTime MCP by usefulapi 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: —
ATool-list grade · score 93 / 100
Release 1.3.2 · scanned 7 Nov 2026
Graded from the tools this server lists, not from its source code.
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 score93
Findings0 threat · 0 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest616722590538c655dc6a7bf6aed317766cd4c86b74f0c7b9ab8829b65b05c772
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bigtime_list_staff | no tags | |
| bigtime_get_staff | no tags | |
| bigtime_list_projects | no tags | |
| bigtime_get_project | no tags | |
| bigtime_get_project_team | no tags | |
| bigtime_list_clients | no tags | |
| bigtime_get_client | no tags | |
| bigtime_list_project_tasks | no tags | |
| bigtime_list_staff_tasks | no tags | |
| bigtime_get_task | no tags | |
| bigtime_get_timesheet | no tags | |
| bigtime_list_project_time | no tags | |
| bigtime_get_time_entry | no tags | |
| bigtime_get_daily_totals | no tags | |
| bigtime_get_expense | no tags | |
| bigtime_list_expense_reports | no tags | |
| bigtime_list_invoices | no tags | |
| bigtime_list_draft_invoices | no tags | |
| bigtime_get_invoice | no tags | |
| bigtime_list_client_invoices | no tags | |
| bigtime_list_payments | no tags | |
| bigtime_get_report_definition | no tags | |
| bigtime_run_report | no tags | |
| bigtime_create_time_entry | state-write | state-write: declares destructiveHint: true |
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 digest616722590538c655
Scanned2026-11-07
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
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.3.2.
1.3.2
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 BigTime MCP by usefulapi 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.