Server providing Argo CD integration for MCP clients.
Pulseway 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
List devices, alerts, antivirus status and audit logs, and run scripts on devices in Pulseway.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http pulseway-mcp-by-usefulapi https://pulseway.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# pulseway_get_environment, pulseway_get_rate_limits, pulseway_list_devices and 13 more
Pulseway 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 pulseway-mcp-by-usefulapi https://pulseway.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.
16 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.
Show the Pulseway instance behind this token: customer name, server type (SaaS or On-Prem), product version, language and license dates. Pulseway API: GET /v3/environment.
No parameter schema on file.
Show the remaining requests for this token per endpoint and the failed-request limits per IP address. Use it before a large batch of calls. Pulseway API: GET /v3/ratelimits.
No parameter schema on file.
List devices (computers and servers) with their group, site and organization. Filter with OData $filter on Identifier or Name. Pulseway API: GET /v3/devices.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| scope_id | integer | no | Return only devices in this scope id. |
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter on Identifier or Name, e.g. contains(tolower(Name), 'web'). |
Show one device: name, group, site, organization and agent state. Pulseway API: GET /v3/devices/{identifier}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | Device identifier (GUID) from pulseway_list_devices. |
Show the antivirus state of one device: protection, definitions and scan status. Pulseway API: GET /v3/devices/{identifier}/antivirus.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | Device identifier (GUID) from pulseway_list_devices. |
List the notifications (alerts) raised for one device. Filter on Id, Message, DateTime or Priority. Pulseway API: GET /v3/devices/{identifier}/notifications.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| identifier | string | yes | Device identifier (GUID) from pulseway_list_devices. |
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter on Id, Message, DateTime or Priority, e.g. contains(tolower(Message), 'disk'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List notifications across all devices. Filter on Id, Message, DateTime or Priority. Pulseway API: GET /v3/notifications.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter on Id, Message, DateTime or Priority, e.g. contains(tolower(Message), 'disk'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List assets (hardware and software inventory records) with their group and description. Filter on Identifier, Name, GroupName or Description. Pulseway API: GET /v3/assets.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
List organizations (customers of the MSP). Pulseway API: GET /v3/organizations.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List sites (locations within an organization). Pulseway API: GET /v3/sites.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List groups (device groups within a site). Pulseway API: GET /v3/groups.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List the automation scripts that can run on devices, with their id, name and input variables. Pulseway API: GET /v3/automation/scripts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List the past runs of one script on one device, with state and times. Pulseway API: GET /v3/automation/scripts/{scriptId}/device/{deviceId}/executions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| script_id | string | yes | Script id (uid) from pulseway_list_scripts. |
| device_identifier | string | yes | Device identifier (GUID) from pulseway_list_devices. |
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. State eq 'Successful'. |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
List the automation workflows in this instance, with their trigger type. Pulseway API: GET /v3/automation/workflows.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
WRITE ACTION: runs one automation script on ONE device. The device must be online. Each call starts a new run. After an error, check pulseway_get_script_executions for the device before any second call. Pulseway API: POST /v3/automation/scripts/{scriptId}/run.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| script_id | string | yes | Script id (uid) from pulseway_list_scripts. |
| device_identifier | string | yes | Device identifier (GUID) from pulseway_list_devices. |
| variables | array | no | Script input variables to override: the variable id and its new value. |
List audit log entries: who did what in Pulseway and when. Filter on the audit fields, e.g. EventDescription or AuditLogRecordDateTime. Pulseway API: GET /v3/auditlogs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| top | integer | no | Maximum items to return (1-100, default 100). |
| skip | integer | no | Items to skip, for paging (default 0). |
| filter | string | no | OData $filter, e.g. contains(tolower(Name), 'web'). |
| orderby | string | no | OData $orderby, e.g. DateTime desc. |
- 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 Pulseway 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 | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| pulseway_get_environment | no tags | |
| pulseway_get_rate_limits | no tags | |
| pulseway_list_devices | no tags | |
| pulseway_get_device | no tags | |
| pulseway_get_device_antivirus | no tags | |
| pulseway_list_device_notifications | no tags | |
| pulseway_list_notifications | no tags | |
| pulseway_list_assets | no tags | |
| pulseway_list_organizations | no tags | |
| pulseway_list_sites | no tags | |
| pulseway_list_groups | no tags | |
| pulseway_list_scripts | no tags | |
| pulseway_get_script_executions | no tags | |
| pulseway_list_workflows | no tags | |
| pulseway_run_script | code-execstate-write | code-exec: keyword "run_script" in tool name; state-write: declares readOnlyHint: false, destructiveHint: true |
| pulseway_list_audit_logs | 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.0.1.
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 Pulseway 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.