Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Chronicle Online 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.
What it does
Read employees, absences, clockings, shifts and overtime in Chronicle Online.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http chronicle-online-mcp-by-usefulapi https://chronicle-online.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# chronicleonline_list_employees, chronicleonline_get_employee, chronicleonline_list_absences and 12 more
Chronicle Online 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.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 chronicle-online-mcp-by-usefulapi https://chronicle-online.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
15 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 employees (and contractors, visitors, agency staff) with their badge ids, names and cost centre. Good first call to find an employee id. Chronicle API: GET /api/Employees.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
Get one employee by id. Chronicle API: GET /api/Employees/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The numeric id of the record. |
List absences configured in Chronicle (for example holiday, sickness and other absence entries). Chronicle API: GET /api/Absences.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
Get one absence by id. Chronicle API: GET /api/Absences/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The numeric id of the record. |
List the absence types (holiday, sickness, absence and others) that Chronicle uses. Chronicle API: GET /api/AbsenceTypes.
No parameter schema on file.
List absentee records: the per-employee records of absence taken. Chronicle API: GET /api/AbsenteeRecords.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List real clockings: the IN and OUT punches recorded at the terminals and apps. Chronicle API: GET /api/RealClockings.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
Get one real clocking by id. Chronicle API: GET /api/RealClockings/{id}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | integer | yes | The numeric id of the record. |
List shift patterns defined in Chronicle. Chronicle API: GET /api/Shifts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List shifts scheduled to employees between two dates (both required). Chronicle API: GET /api/ScheduledShifts?startDate&endDate.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| startDate | string | yes | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| endDate | string | yes | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List work records (worked time per employee) between two dates. Optional employee filter. Chronicle API: GET /api/WorkRecords.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employeeId | integer | no | Filter by employee id. |
| startDate | string | no | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| endDate | string | no | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List daily overtime per employee between two dates. Chronicle API: GET /api/DailyOvertime.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employeeId | integer | no | Filter by employee id. |
| startDate | string | no | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| endDate | string | no | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List weekly overtime per employee between two dates. Chronicle API: GET /api/WeeklyOvertime.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| employeeId | integer | no | Filter by employee id. |
| startDate | string | no | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| endDate | string | no | ISO 8601 date or date-time, e.g. 2026-11-01 or 2026-11-01T00:00:00Z. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List cost centres used to group employees and time. Chronicle API: GET /api/CostCentres.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
List employees who have left (leavers). Chronicle API: GET /api/Leavers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchQuery | string | no | Free-text search filter, as the API accepts it. |
| orderBy | string | no | Sort order, as the API accepts it (for example a field name). |
| skip | integer | no | Number of records to skip, for paging (default 0). |
| take | integer | no | Number of records to return, for paging. |
- 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 Chronicle Online MCP by usefulapi or to call it, at any volume.
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.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
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.
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. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| chronicleonline_list_employees | no tags | |
| chronicleonline_get_employee | no tags | |
| chronicleonline_list_absences | no tags | |
| chronicleonline_get_absence | no tags | |
| chronicleonline_list_absence_types | no tags | |
| chronicleonline_list_absentee_records | no tags | |
| chronicleonline_list_real_clockings | no tags | |
| chronicleonline_get_real_clocking | no tags | |
| chronicleonline_list_shifts | no tags | |
| chronicleonline_list_scheduled_shifts | no tags | |
| chronicleonline_list_work_records | no tags | |
| chronicleonline_list_daily_overtime | no tags | |
| chronicleonline_list_weekly_overtime | no tags | |
| chronicleonline_list_cost_centres | no tags | |
| chronicleonline_list_leavers | no tags |
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
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.
No release note was published with this version.
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.
Any signed-in account that does not publish Chronicle Online 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.
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.