# PERM Tracker (remote · permtracker.app)

PERM, prevailing wage and H-1B case status, DOL's queue and the visa bulletin, from federal records

- Trust score: 88/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `permtracker.app`: 88/100 (this document), [markdown](https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker.md), [page](https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker)

## Channel facts

- Endpoint: `https://permtracker.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 778 tokens (~111/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the PERM Tracker MCP server?

PERM Tracker is a hosted endpoint at https://permtracker.app/mcp, so there is nothing to install locally. 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 --transport http app-permtracker-perm-tracker 'https://permtracker.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-permtracker-perm-tracker": {
      "url": "https://permtracker.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-permtracker-perm-tracker": {
      "type": "http",
      "url": "https://permtracker.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-permtracker-perm-tracker]
url = "https://permtracker.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-permtracker-perm-tracker": {
      "type": "remote",
      "url": "https://permtracker.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-permtracker-perm-tracker --url 'https://permtracker.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-permtracker-perm-tracker:
    url: "https://permtracker.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-permtracker-perm-tracker": {
      "Transport": "http",
      "Url": "https://permtracker.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-permtracker-perm-tracker -t streamable-http -u 'https://permtracker.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-permtracker-perm-tracker": {
      "type": "http",
      "url": "https://permtracker.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-02 (score 88, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 87, 0)

- [functional regression] Schema quality: 667 → 778
- [functional] New tool “find_soc_code”

### 2026-10-29 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (7)

### `lookup_case` (~127 tokens)

Look up a case

One DOL case by number: status, filing date, employer, job and, once decided, DOL's decided record. PERM (G-100-...), prevailing wage (P-100- to P-203-...), H-1B LCA (I-200-...) and H-2A, H-2B or CW-1 numbers. Example: {"case_number": "G-100-26045-123456"}.

Input parameters:

- `case_number` (string, required): As DOL prints it, e.g. G-100-26045-123456.

### `estimate_decision` (~119 tokens)

Estimate a PERM decision date

When a pending PERM case is likely to be decided, with a range, the model used and its caveats. Pass a case number, or a filing date for a case in analyst review. An estimate, not a promise. Examples: {"case_number": "G-100-26045-123456"} or {"filed": "2026-01-15"}.

Input parameters:

- `case_number` (string): A PERM case number.
- `filed` (string): Filing date, YYYY-MM-DD, when there's no case number.

### `queue_status` (~53 tokens)

PERM and prevailing wage queues

DOL's processing times today: the month each PERM and prevailing wage queue is working on, average days to a decision, and how many PERM cases are pending from each filing month. Takes no arguments: {}.

### `visa_bulletin` (~74 tokens)

Visa bulletin

A visa bulletin's employment and family final action and dates for filing charts, as printed. The newest by default; months back to June 2005. Examples: {} for the newest, or {"month": "2026-10"}.

Input parameters:

- `month` (string): YYYY-MM. Leave out for the newest.

### `search_sponsors` (~95 tokens)

Find an employer, law firm or occupation

Search DOL's PERM records by name. Returns each match's record and the slug that employer_profile takes. Example: {"kind": "employer", "name": "Microsoft"}.

Input parameters:

- `kind` (string, required): One of "employer", "law firm" or "occupation" (singular).
- `name` (string, required): Part of the name, 2 to 120 characters, e.g. Microsoft.

### `employer_profile` (~134 tokens)

An employer's, law firm's or occupation's PERM record

Cases in DOL's published files (certified, denied, median days to a decision, filings in the last 12 months, and for an occupation the median offered wage), plus how many of its cases are pending at DOL right now and at which stage. Find the slug with search_sponsors first. Example: {"kind": "employer", "slug": "microsoft-corporation"}.

Input parameters:

- `kind` (string, required): One of "employer", "law firm" or "occupation" (singular).
- `slug` (string, required): From search_sponsors, e.g. google-llc.

### `find_soc_code` (~111 tokens)

Find a job's SOC code

The SOC occupation codes employers filed a job title under in DOL's PERM, prevailing wage and LCA files, with each code's share of the title's filings; or a code's title, and for a 2010 code the 2018 codes it became. Examples: {"query": "data scientist"} or {"query": "15-1132"}.

Input parameters:

- `query` (string, required): A job title or a SOC code, e.g. data scientist or 15-2051.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker#diagnostics

## Score history

- 2026-11-05: 88
- 2026-11-04: 88
- 2026-11-03: 88
- 2026-11-02: 88
- 2026-11-01: 88
- 2026-10-31: 87
- 2026-10-30: 87
- 2026-10-29: 87
- 2026-10-28: 86
- 2026-10-27: 86
- 2026-10-26: 85
- 2026-10-25: 85
- 2026-10-24: 84
- 2026-10-23: 84
- 2026-10-22: 83
- 2026-10-21: 83
- 2026-10-20: 82
- 2026-10-19: 82
- 2026-10-18: 81
- 2026-10-17: 81
- 2026-10-16: 80
- 2026-10-15: 80
- 2026-10-14: 80
- 2026-10-13: 79
- 2026-10-12: 79
- 2026-10-10: 78
- 2026-10-07: 76
- 2026-10-04: 75
- 2026-10-03: 75

## Common questions

### What is the PERM Tracker MCP server?

PERM Tracker is an MCP server listed in the public MCP registry as app.permtracker/perm-tracker. PERM, prevailing wage and H-1B case status, DOL's queue and the visa bulletin, from federal records. This page covers its hosted endpoint (https://permtracker.app/mcp).

### Is the PERM Tracker MCP server safe to use?

PERM Tracker scores 88 out of 100 on VerifyMCP. 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 Tracker MCP server expose?

PERM Tracker exposes 7 tools: lookup_case, estimate_decision, queue_status, visa_bulletin, search_sponsors, and 2 more. Their descriptions and schemas cost roughly 713 tokens of context every time the server is loaded.

### Does the PERM Tracker MCP server require authentication?

No. We connected to PERM Tracker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the PERM Tracker MCP server still maintained?

PERM Tracker 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 did VerifyMCP test on the PERM Tracker MCP server?

VerifyMCP ran 13 checks on PERM Tracker, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://permtracker.app/mcp
- Website: https://permtracker.app/developers
- Changelog RSS feed: https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker.json
- HTML version of this page: https://verifymcp.io/servers/app-permtracker-perm-tracker/permtracker