Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Nothing to run from here
AdminPulse 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
15
tools declared
remote
at its publisher
—
calls last 7d
What it does
Read relations, invoices, tasks and documents; create tasks and log interactions in AdminPulse.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http adminpulse-mcp-by-usefulapi https://adminpulse.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# adminpulse_get_current_user, adminpulse_list_companies, adminpulse_search_relations and 12 more
AdminPulse 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 727 servers
usefulapi727 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 adminpulse-mcp-by-usefulapi https://adminpulse.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
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.
Return the AdminPulse user that the API key belongs to (name and email). Good first call to confirm the connection. GET /users/me.
No parameter schema on file.
List the companies (administrations) that this key can access, with their ids. GET /companies.
No parameter schema on file.
List relations (clients, suppliers and contacts) with paging. Filter by text, relation type (0 company, 1 sole proprietor, 2 person), tags, or include inactive. GET /relations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 0. |
| pageSize | integer | no | Results per page (1 to 100). |
| searchCriteria | string | no | Free text: name, code or other searchable field. |
| type | integer | no | Relation type: 0 company, 1 sole proprietor, 2 person. |
| withTags | string | no | Comma-separated tag names; only relations with these tags. |
| includeInactive | boolean | no | Include inactive relations. |
Get one relation with its details. Pass the relation GUID or its unique identifier such as APR00001. GET /relations/{identifier}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | Relation GUID or unique identifier, for example APR00001. |
Quick lookup of relations by name, returning a short list with their ids and unique identifiers. GET /relations/names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| searchValue | string | yes | Name or part of a name to find. |
| includeInactive | boolean | no | Include inactive relations. |
| take | integer | no | Maximum number of results (1 to 100). |
List sales invoices with paging. Filter by relation, invoice date range, or sent, paid, exported and draft status. GET /invoices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 0. |
| pageSize | integer | no | Results per page (1 to 100). |
| relationIdentifier | string | no | Relation unique identifier, for example APR00001. |
| invoiceDateFrom | string | no | Invoice date from, ddMMyyyy (as the API examples show). |
| invoiceDateUntil | string | no | Invoice date until, ddMMyyyy (as the API examples show). |
| sent | boolean | no | — |
| paid | boolean | no | — |
| exported | boolean | no | — |
| onlyDraft | boolean | no | — |
Get one invoice by its id (GUID), with its lines and payment status. GET /invoices/{invoiceId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoiceId | string | yes | Invoice id (GUID) from adminpulse_list_invoices. |
List tasks with paging. Filter by relation id, deadline range, or main task template. GET /tasks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 0. |
| pageSize | integer | no | Results per page (1 to 100). |
| relationId | string | no | Relation id (GUID). |
| deadlineFrom | string | no | Deadline from (as the API documents it). |
| deadlineUntil | string | no | Deadline until (as the API documents it). |
| mainTaskTemplateId | string | no | Main task template id (GUID). |
| languageCode | string | no | Two-letter language code for task names, for example nl. |
Get one task by its id (GUID), with its status, deadline and relation. GET /tasks/{taskId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taskId | string | yes | Task id (GUID) from adminpulse_list_tasks. |
Create a task for a relation. The deadline is ISO, for example 2026-01-31T00:00:00. Status is the number the API defines. POST /tasks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relationIdentifier | string | yes | Relation unique identifier, for example APR00001. |
| name | string | yes | Task name. |
| deadline | string | yes | Deadline in ISO format, for example 2026-01-31T00:00:00. |
| templateId | string | no | Task template id (GUID), if the task comes from a template. |
| status | integer | no | Task status number as the API defines it. |
| remark | string | no | Free text note. |
| tags | array | no | Tag names to put on the task. |
Set the status of a task found by relation, deadline and task names (no task id needed). Setting the same status again changes nothing. POST /tasks/updateStatus.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| relationIdentifier | string | yes | Relation unique identifier, for example APR00001. |
| deadline | string | yes | Deadline of the task, ddMMyyyy (for example 31122020). |
| mainTaskName | string | yes | Main task name, for example BTW listing. |
| subTaskName | string | yes | Sub task name, for example BTW listing opstellen. |
| status | integer | yes | New status number as the API defines it. |
| inapplicable | boolean | no | Mark the task as not applicable. |
| isBlocked | boolean | no | Mark the task as blocked. |
List logged interactions (calls, meetings, notes) with paging. Filter by relation, type or date. GET /interactions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 0. |
| pageSize | integer | no | Results per page (1 to 100). |
| relationId | string | no | Relation id (GUID). |
| interactionType | integer | no | Interaction type number as the API defines it. |
| dateFrom | string | no | Date from, ddMMyyyy (as the API examples show). |
| dateUntil | string | no | Date until, ddMMyyyy (as the API examples show). |
Log an interaction (for example a call or a note) on a relation. The date is ddMMyyyy and the time is HH:mm. POST /interactions/add.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | Short title of the interaction. |
| relationIdentifier | string | yes | Relation unique identifier, for example APR00001. |
| description | string | no | Longer text of the interaction. |
| interactiontype | integer | no | Interaction type number as the API defines it. |
| date | string | no | Date, ddMMyyyy. |
| time | string | no | Time, HH:mm. |
List time or cost registrations with paging. Filter by relation, invoiced state or registration date range. GET /registrations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 0. |
| pageSize | integer | no | Results per page (1 to 100). |
| relationIdentifier | string | no | Relation unique identifier, for example APR00001. |
| invoiced | boolean | no | Only invoiced (true) or only not yet invoiced (false) registrations. |
| registrationDateFrom | string | no | Registration date from, ddMMyyyy. |
| registrationDateUntil | string | no | Registration date until, ddMMyyyy. |
List document metadata (name, type, dates, tags) with paging. Filter by relation or document date range. GET /documents.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 0. |
| pageSize | integer | no | Results per page (1 to 100). |
| relationIdentifier | string | no | Relation unique identifier, for example APR00001. |
| documentDateFrom | string | no | Document date from, ddMMyyyy. |
| documentDateUntil | string | no | Document date until, ddMMyyyy. |
| tagNames | string | no | Comma-separated tag names. |
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 AdminPulse 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.5.0 · scanned 12 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 digest04f6d4b0ae8a83103cf019dc87a77771dc02f8bf28a41a3c9dd1d41519ff73a7
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 |
|---|---|---|
| adminpulse_get_current_user | no tags | |
| adminpulse_list_companies | no tags | |
| adminpulse_search_relations | no tags | |
| adminpulse_get_relation | no tags | |
| adminpulse_find_relations_by_name | no tags | |
| adminpulse_list_invoices | no tags | |
| adminpulse_get_invoice | no tags | |
| adminpulse_list_tasks | no tags | |
| adminpulse_get_task | no tags | |
| adminpulse_create_task | state-write | state-write: declares destructiveHint: true |
| adminpulse_update_task_status | no tags | |
| adminpulse_list_interactions | no tags | |
| adminpulse_add_interaction | state-write | state-write: declares destructiveHint: true |
| adminpulse_list_registrations | no tags | |
| adminpulse_list_documents | 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
Integrityfirst-seen
Surface digest04f6d4b0ae8a8310
Scanned2026-11-12
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.5.0.
1.5.0
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 AdminPulse 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.