# Perm (npm · @pipeworx/mcp-perm)

PERM MCP — US green-card labor certification data from DOL PERM (Program Electronic Review…

- Trust score: 82/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-perm/perm-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-perm/perm-mcp)
- npm · `@pipeworx/mcp-perm`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm.md), [page](https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-perm`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-perm).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 688 tokens (~229/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Perm MCP server?

Perm runs locally as an npm package, launched with npx -y @pipeworx/mcp-perm. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-perm -- npx -y @pipeworx/mcp-perm
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-perm": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-perm"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-perm": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-perm"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-perm -- npx -y @pipeworx/mcp-perm
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-perm": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-perm"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-perm --command npx --arg -y --arg @pipeworx/mcp-perm
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-perm:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-perm"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-perm": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-perm"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-perm -t stdio -c npx -a -y @pipeworx/mcp-perm
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-perm": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-perm"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-04 (score 67, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-30 (score 79)

First indexed and scored.

## MCP tools (3)

### `perm_employer_certifications` (~206 tokens)

Check whether a US employer sponsors green cards (PERM labor certification) and profile their sponsorship, from DOL PERM (Form ETA-9089) disclosures. Answers 'does company X sponsor green cards' for recruiting and candidate advising. Returns the number of certified PERM filings, offered-wage range (min / median / max), the top sponsored job titles, and top worksite locations for the employer. Filter by year (DOL federal fiscal year, Oct-Sep); defaults to the latest full year. Employer name is matched as the disclosed legal name (e.g. 'Microsoft Corporation', 'Amazon.com Services LLC').

Input parameters:

- `employer` (string, required): Employer name to look up, e.g. "Microsoft", "Oracle", "Amazon".
- `year` (number|string): Filing year (e.g. 2025). Defaults to the most recent full year this pack has data for. Interpreted as DOL federal fiscal year (Oct-Sep).

### `perm_salary` (~230 tokens)

Look up real green-card (PERM) offered wages for a job title from DOL PERM disclosures — a market wage benchmark backed by actual certified filings (not estimates). Answers 'what do green-card-sponsored software engineers earn at company X / in city Y'. Filter by job title, and optionally by employer, city, and year. Returns wage statistics (count, min / median / average / max) plus a sample of individual records (employer, title, wage, location, dates).

Input parameters:

- `city` (string): Optional worksite city, e.g. "SEATTLE" or "AUSTIN".
- `employer` (string): Optional employer name to scope to, e.g. "Meta".
- `job_title` (string, required): Job title to search, e.g. "software engineer", "data scientist". Matched as a substring of the disclosed title.
- `limit` (number|string): Max sample records to return (default 15, max 50).
- `year` (number|string): Filing year (e.g. 2025). Defaults to the most recent full year.

### `perm_top_sponsors` (~201 tokens)

Find which US employers sponsor the most green cards (PERM labor certifications) for a given job title (optionally in a specific city) — a candidate-sourcing / target-account signal for recruiting. Answers 'which companies sponsor the most data engineers for green cards' or 'top PERM sponsors for nurses'. Returns employers ranked by certified PERM filings for the role, each with their filing count and median offered wage. Backed by real DOL PERM disclosures.

Input parameters:

- `city` (string): Optional worksite city to scope to, e.g. "AUSTIN" or "NEW YORK".
- `job_title` (string, required): Job title to rank sponsors for, e.g. "data engineer", "physical therapist".
- `limit` (number|string): Max employers to return (default 15, max 50).
- `year` (number|string): Filing year (e.g. 2025). Defaults to the most recent full year.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 67
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79

## Common questions

### What is the Perm MCP server?

Perm is an MCP server listed in the public MCP registry as io.github.pipeworx-io/perm. PERM MCP, US green-card labor certification data from DOL PERM (Program Electronic Review… This page covers its npm package (@pipeworx/mcp-perm).

### Is the Perm MCP server safe to use?

Perm scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Perm MCP server expose?

Perm exposes 3 tools: perm_employer_certifications, perm_salary, perm_top_sponsors. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.

### Is the Perm MCP server still maintained?

Perm is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Perm MCP server under?

Perm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Perm MCP server?

VerifyMCP ran 16 checks on Perm, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-perm
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-perm
- Repository: https://github.com/pipeworx-io/mcp-perm
- Website: https://pipeworx.io/packs/perm
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-perm/pipeworx-mcp-perm