MCP.Market

Action1 MCP server

by wyre-technology·io.github.wyre-technology/action1-mcp·v1.1.5·3 stars
No reviews yet

Action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API.

B75/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B75/100

full report

Adoption
Growing

3 stars

Reviews

Write one

Nobody has reviewed Action1 yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Action1 tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-11-02 · same rubric, same numbers if you re-run it

no findings
  • –Code scanpackage could not be scannedn/a
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 75/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Action1 compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
75/100
higher than 45% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers

Install Action1 in Claude Code, Cursor or VS Code

claude mcp add action1-mcp -- docker run -i --rm ghcr.io/wyre-technology/action1-mcp:v1.1.5
Add to Cursor

What the publisher says

From the Action1 repository's README, as published. We do not edit it. Read it on GitHub

Action1 MCP Server

MCP server for Action1 — endpoint inventory, patch visibility, and policy automation via the Model Context Protocol.

Read-only in v1. Deploy / automation surface is intentionally separated to a later release for blast-radius reasons (a bad policy push can brick endpoint fleets).

Tools

API surface maps to PSAction1 (Action1's MIT-licensed PowerShell module). When the v1 surface earns its keep, write tools (deploy, requery, package upload) come in v2 behind separate review.

Interactive Device Card (MCP Apps)

action1getendpoint renders as an interactive device-summary card in MCP Apps hosts (Claude Desktop/web) — status, OS, user, IP, agent version, reboot-required, and missing-update counts at a glance; plain-JSON behavior is unchanged in other hosts. The card is read-only (matching the v1 tool surface), neutral by default, and brandable via window.BRAND injection or MCPBRAND env vars (MCPBRANDNAME, MCPBRANDLOGOURL, MCPBRANDPRIMARYCOLOR, MCPBRANDACCENTCOLOR, MCPBRANDBG, MCPBRAND_TEXT) — no rebuild needed.

Usage

Claude Desktop (MCPB)

Install via the MCPB bundle from the latest release.

Required credentials (created in Action1 → Settings → API Credentials, non-recoverable on creation — copy immediately):

  • API Key (Client ID)
  • Secret
  • Region (NorthAmerica default; also Europe, AsiaPacific, Australia)
  • Optional default organization id (for single-tenant use)

Stdio (direct)

ACTION1_API_KEY=... \
ACTION1_SECRET=... \
ACTION1_REGION=NorthAmerica \
ACTION1_DEFAULT_ORG_ID=org-... \
npx -y github:WYRE-AI/action1-mcp

HTTP (gateway mode)

MCP_TRANSPORT=http PORT=8080 AUTH_MODE=gateway \
  docker run -p 8080:8080 ghcr.io/wyre-ai/action1-mcp:latest

Per-request credentials via headers:

  • X-Action1-API-Key
  • X-Action1-Secret
  • X-Action1-Region
  • X-Action1-Default-Org-Id

Architecture

src/
├── index.ts                  # stdio + HTTP transports, tool dispatch
├── card.builder.ts           # MCP Apps device-card normalization + brand injection
├── resources.ts              # resources/list + resources/read (ui:// device card)
├── generated/
│   └── device-card-html.ts   # committed vite single-file bundle (npm run build:ui)
├── sdk/
│   └── action1-client.ts     # embedded REST + OAuth client (factor-out candidate
│                             # if surface crosses ~20 tools / 2+ domains)
├── utils/
│   ├── client.ts             # credential resolution (env vs gateway headers)
│   └── types.ts              # DomainHandler interface
├── domains/                  # one file per resource type
│   ├── organizations.ts
│   ├── endpoints.ts
│   ├── policies.ts
│   └── updates.ts
└── __tests__/                # domain tests + MCP Apps contract tests
ui/                           # device-card source (index.html + device-card.ts)

Per-request credential isolation via AsyncLocalStorage — concurrent requests in HTTP mode never share credentials through process.env.

Development

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Action1: common questions

Is Action1 MCP server safe?
Mostly: it is graded B (75/100). Read the Action1 safety report
How do I install Action1?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Action1 need an API key?
Yes. The registry entry asks for ACTION1_CLIENT_SECRET.
Is Action1 maintained?
The last commit was 6 days ago (2026-10-29). The latest release is v1.1.5.
How does Action1 compare with other MCP servers?
safety score 75/100 (higher than 45% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.

More from wyre-technology →