# Password Change Management (remote · mcp.chg.pw)

MCP tools for password and account management

- Trust score: 75/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.chg.pw`: 75/100 (this document), [markdown](https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2.md), [page](https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2)

## Channel facts

- Endpoint: `https://mcp.chg.pw/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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**: 52/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 97 tokens (~24/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 4 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 current MCP spec version (2026-07-28).

## Install

### How do I install the Password Change Management MCP server?

Password Change Management is a hosted endpoint at https://mcp.chg.pw/, 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 pw-chg-password-change-management 'https://mcp.chg.pw/'
```

### Cursor

```json
{
  "mcpServers": {
    "pw-chg-password-change-management": {
      "url": "https://mcp.chg.pw/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pw-chg-password-change-management": {
      "type": "http",
      "url": "https://mcp.chg.pw/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.pw-chg-password-change-management]
url = "https://mcp.chg.pw/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pw-chg-password-change-management": {
      "type": "remote",
      "url": "https://mcp.chg.pw/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pw-chg-password-change-management --url 'https://mcp.chg.pw/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  pw-chg-password-change-management:
    url: "https://mcp.chg.pw/"
```

### Netclaw

```json
{
  "McpServers": {
    "pw-chg-password-change-management": {
      "Transport": "http",
      "Url": "https://mcp.chg.pw/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add pw-chg-password-change-management -t streamable-http -u 'https://mcp.chg.pw/'
```

### Other

```json
{
  "mcpServers": {
    "pw-chg-password-change-management": {
      "type": "http",
      "url": "https://mcp.chg.pw/"
    }
  }
}
```

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-05 (score 75, +1)

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

### 2026-11-03 (score 74, +1)

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

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

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

### 2026-10-30 (score 72, +1)

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

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

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

### 2026-10-25 (score 70, +45)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: not serving MCP → reachable
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-10-24 (score 25, −44)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.13 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

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

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

## MCP tools (4)

### `service_status` (~17 tokens)

Get the password and account management service status.

### `secrets_vault_read` (~28 tokens)

Read a named credential record from the account-management vault.

Input parameters:

- `key` (string, required)

### `production_db_query` (~23 tokens)

Query the read-only accounts view.

Input parameters:

- `sql` (string, required)

### `okta_admin_password_reset` (~29 tokens)

Request a password reset for a managed account.

Input parameters:

- `okta_username` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2#diagnostics

## Score history

- 2026-11-05: 75
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 71
- 2026-10-26: 70
- 2026-10-25: 70
- 2026-10-24: 25
- 2026-10-23: 69
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67

## Common questions

### What is the Password Change Management MCP server?

Password Change Management is an MCP server listed in the public MCP registry as pw.chg/password-change-management. MCP tools for password and account management. This page covers its hosted endpoint (https://mcp.chg.pw/).

### Is the Password Change Management MCP server safe to use?

Password Change Management scores 75 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 Password Change Management MCP server expose?

Password Change Management exposes 4 tools: service_status, secrets_vault_read, production_db_query, okta_admin_password_reset. Their descriptions and schemas cost roughly 97 tokens of context every time the server is loaded.

### Does the Password Change Management MCP server require authentication?

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

### Is the Password Change Management MCP server still maintained?

Password Change Management 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 Password Change Management MCP server?

VerifyMCP ran 13 checks on Password Change Management, 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://mcp.chg.pw/
- Website: https://mcp.chg.pw/
- Changelog RSS feed: https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/pw-chg-password-change-management/mcp-2