Is io.github.wyre-technology/action1-mcp safe to use?

io.github.wyre-technology/action1-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.

How do I install io.github.wyre-technology/action1-mcp?

io.github.wyre-technology/action1-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.wyre-technology/action1-mcp do?

io.github.wyre-technology/action1-mcp provides 4 tools: Tools, Usage, Development, License. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.wyre-technology/action1-mcp?

io.github.wyre-technology/action1-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.

Is io.github.wyre-technology/action1-mcp actively maintained?

io.github.wyre-technology/action1-mcp is actively maintained — last commit was 1 day ago. It has 2 GitHub stars.

io.github.wyre-technology/action1-mcp

github

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

2 88.3k/wk 4 tools GitHub npm

No known CVEs

Apache-2.0 license

Actively maintained

Last commit 1d ago

Works with most clients

Transport: stdio, sse, http

4 tools · ~88 tok

Grade A · 0.0% of 200K ctx

MCPpedia last refreshed this data 14h ago

Edit this pageView history

io.github.wyre-technology/action1-mcp is an MCP server that action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 92/100 on MCPpedia's security, maintenance and efficiency rubric.

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-wyre-technology-action1-mcp": {
      "args": [
        "-y",
        "github"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wyre-technology-action1-mcp)](https://mcppedia.org/s/io-github-wyre-technology-action1-mcp)

Read me

What io.github.wyre-technology/action1-mcp does

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

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'github' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

92/100across 5 weighted dimensions

How we score →

0255075100

−8

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked github against OSV.dev.

Inventory

Tools (4)

Click any tool to inspect its schema.

~88 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wyre-technology/action1-mcp safe to use?: io.github.wyre-technology/action1-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install io.github.wyre-technology/action1-mcp?: io.github.wyre-technology/action1-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.wyre-technology/action1-mcp do?: io.github.wyre-technology/action1-mcp provides 4 tools: Tools, Usage, Development, License. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.wyre-technology/action1-mcp?: io.github.wyre-technology/action1-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.wyre-technology/action1-mcp actively maintained?: io.github.wyre-technology/action1-mcp is actively maintained — last commit was 1 day ago. It has 2 GitHub stars.

Similar servers

Others in developer-tools

View all →

Context797

Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors

61.2k 2

Mcp Gitlab96

MCP server for using the GitLab API

1.9k 12

Supabase MCP Server96

Manage Supabase projects — databases, auth, storage, and edge functions

2.9k 4

Chrome Devtools Mcp96

Chrome DevTools for coding agents

49.7k 10

MCP Security Weekly

Get CVE alerts and security updates for io.github.wyre-technology/action1-mcp and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Developer Tools

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, sse, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-wyre-technology-action1-mcp": {
      "args": [
        "-y",
        "github"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-wyre-technology-action1-mcp)](https://mcppedia.org/s/io-github-wyre-technology-action1-mcp)

Read me

What io.github.wyre-technology/action1-mcp does

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

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'github' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

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

Tool	Description
`action1_navigate`	Discover available tools by domain (organizations / endpoints / policies / updates)
`action1_list_organizations`	List Action1 tenants accessible to the configured credentials
`action1_list_endpoints`	List managed devices in an organization
`action1_get_endpoint`	Get a single endpoint by id
`action1_list_missing_updates`	List missing OS/application patches across endpoints — Action1's headline value-prop
`action1_list_policies`	List automation / policy / remediation rules

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)

action1_get_endpoint 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 MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_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

npm install
npm run b

... [View full README on GitHub](https://github.com/wyre-technology/action1-mcp#readme)

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

92/100across 5 weighted dimensions

How we score →

0255075100

−8

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked github against OSV.dev.

Inventory

Tools (4)

Click any tool to inspect its schema.

~88 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.wyre-technology/action1-mcp safe to use?: io.github.wyre-technology/action1-mcp has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under Apache-2.0.
How do I install io.github.wyre-technology/action1-mcp?: io.github.wyre-technology/action1-mcp supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.wyre-technology/action1-mcp do?: io.github.wyre-technology/action1-mcp provides 4 tools: Tools, Usage, Development, License. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.wyre-technology/action1-mcp?: io.github.wyre-technology/action1-mcp is compatible with claude-desktop, cursor, claude-code. It uses stdio and sse and http transport.
Is io.github.wyre-technology/action1-mcp actively maintained?: io.github.wyre-technology/action1-mcp is actively maintained — last commit was 1 day ago. It has 2 GitHub stars.