Skip to content

Password Change Management MCP server

pw.chg/password-change-managementchg.pwstreamable-httpv1.0.1Scanned

MCP tools for password and account management

14 tools: 1 can delete or cancel things, 1 do something that can't be undone, 7 change things and 5 only read.

Tools: 1 delete, 1 irreversible, 7 write, 5 read.
  • Reads private data · 3
  • Reads text others write · 1
  • Can send data out · 3
  • 7 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Password Change Management MCP server can do

The Password Change Management MCP server is published by chg.pw, a domain the MCP Registry verified. It has 14 tools. It can delete or cancel things (1 tool: backup), do things that cannot be undone, such as sending, paying or publishing (send) and create or change data (7 tools: shell, git_clone, browser_navigate, memory_write and 3 more). 5 tools only read.

3 tools read private data (filesystem, read_file and list_directory); 1 tool brings in text other people can write (browser_navigate); 3 tools can send data out of your system (git_clone, browser_navigate and send). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 7 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

14 tools

Deletes or cancels 1Claude Code: deny
  • backupArchive a directory tree into a backup file2 findings

    Why it is in this group

    • The description's first verb is "archive": a word for removing or ending something.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "backup" read-only (readOnlyHint: true), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "archive": a word for removing or ending something.

      What this check looks for
    • Warn

      The server marks "backup" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "archive": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    Archive a directory tree into a backup file

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Can't be undone 1Claude Code: ask
  • sendSend a message payload through the configured transportCan send data out1 finding

    Why it is in this group

    • The name "send" says "send": a word for sending, and what is sent cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe name "send" says "send": it sends or publishes something to other people.

    Findings

    • Warn

      The server marks "send" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "send" says "send": a word for sending, and what is sent cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    Send a message payload through the configured transport

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Changes things 7Claude Code: ask
  • browser_navigateOpen a URL in a configured browser automation sessionReads text others writeCan send data out1 finding

    Why it is in this group

    • The name "browser_navigate" says "navigate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe name "browser_navigate" says "navigate" and "browser": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "open" and "url": it reads web pages, which anyone can write.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "browser_navigate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "browser_navigate" says "navigate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Open a URL in a configured browser automation session

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • git_cloneClone a git repository into a local directoryCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    Clone a git repository into a local directory

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • memory_writeWrite a value into the server-side memory store1 finding

    Why it is in this group

    • The name "memory_write" says "write": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "memory_write" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "memory_write" says "write": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Write a value into the server-side memory store

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • network_infoReport host interfaces and listening TCP portsNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Report host interfaces and listening TCP ports

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • shellExecute a shell command and capture its output1 finding

    Why it is in this group

    • The description's first verb is "execute": a word for a change.
    • The input takes a statement or command to run (input.command), which can change anything it can reach.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "shell" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "execute": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Execute a shell command and capture its output

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • sync_dataSynchronize telemetry bundles to the configured backend1 finding

    Why it is in this group

    • The name "sync_data" says "sync": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "sync_data" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "sync_data" says "sync": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Synchronize telemetry bundles to the configured backend

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • user_profileReport the current user account and profile fieldsNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Report the current user account and profile fields

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • config_getResolve a configuration key from the environmentNo findings

    Why it is in this group

    • The name "config_get" says "get": a word for reading.
    Description, as the server wrote it
    Resolve a configuration key from the environment

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • filesystemRead files and directories from the host filesystemReads private dataNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "file": it reads files.
    Description, as the server wrote it
    Read files and directories from the host filesystem

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_directoryList directory entries with basic metadataReads private dataNo findings

    Why it is in this group

    • The name "list_directory" says "list": a word for reading.

    What it can reach

    • private-dataThe name "list_directory" says "list" and "directory": it reads files.
    • private-dataThe description's first sentence says "list" and "directory": it reads files.
    Description, as the server wrote it
    List directory entries with basic metadata

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • memory_readRead a value from the server-side memory storeNo findings

    Why it is in this group

    • The name "memory_read" says "read": a word for reading.
    Description, as the server wrote it
    Read a value from the server-side memory store

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • read_fileRead the contents of a single fileReads private dataNo findings

    Why it is in this group

    • The name "read_file" says "read": a word for reading.

    What it can reach

    • private-dataThe name "read_file" says "read" and "file": it reads files.
    • private-dataThe description's first sentence says "read" and "file": it reads files.
    Description, as the server wrote it
    Read the contents of a single file

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

9 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__password-change-management__browser_navigate"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:18 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
9
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 9 tools that change things (1 destructive, 1 irreversible, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.chg.pw/: tools/list returned 14 tools to an anonymous client, including backup (destructive), send (irreversible), shell (write), git_clone (write), browser_navigate (write) and 4 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 2 to 9

Findings

Matches of fixed checks, with the text they matched.

7 warn
  • Warnshell

    The server marks "shell" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "execute": a word for a change.

    What this check looks for
  • The server marks "browser_navigate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "browser_navigate" says "navigate": a word for a change.

    What this check looks for
  • The server marks "memory_write" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "memory_write" says "write": a word for a change.

    What this check looks for
  • Warnbackup

    The server marks "backup" read-only (readOnlyHint: true), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "archive": a word for removing or ending something.

    What this check looks for
  • Warnbackup

    The server marks "backup" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "archive": a word for removing or ending something.

    What this check looks for
  • The server marks "sync_data" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "sync_data" says "sync": a word for a change.

    What this check looks for
Show 1 more finding
  • Warnsend

    The server marks "send" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "send" says "send": a word for sending, and what is sent cannot be taken back.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools14 added, 4 removed.+14 added−4 removedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 9.View diff
    • Tools that change things, listed without credentials: 2 to 9

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http password-change-management https://mcp.chg.pw/
claude mcp add --transport http password-change-management https://mcp.chg.pw/

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__password-change-management__filesystem",
      "mcp__password-change-management__read_file",
      "mcp__password-change-management__list_directory",
      "mcp__password-change-management__memory_read",
      "mcp__password-change-management__config_get"
    ],
    "ask": [
      "mcp__password-change-management__shell",
      "mcp__password-change-management__git_clone",
      "mcp__password-change-management__browser_navigate",
      "mcp__password-change-management__memory_write",
      "mcp__password-change-management__user_profile",
      "mcp__password-change-management__network_info",
      "mcp__password-change-management__sync_data",
      "mcp__password-change-management__send"
    ],
    "deny": [
      "mcp__password-change-management__backup"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as password-change-management. Review it before you use it.

Capability tags behind 6 rules
  • mcp__password-change-management__filesystem private-data
  • mcp__password-change-management__read_file private-data
  • mcp__password-change-management__list_directory private-data
  • mcp__password-change-management__git_clone outbound
  • mcp__password-change-management__browser_navigate untrusted-input, outbound
  • mcp__password-change-management__send outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/pw.chg/password-change-management/verify?hash=663a94b22e4fd3feb81f6978649e561ba9af63ab83f63112d27dcd66f18333af" | jq -e '.changed == false'

Pinned hash 663a94b22e4f, from Nov 19, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/pw.chg/password-change-management/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for pw.chg/password-change-management
[![Anlyon Radar](https://radar.anlyon.com/badge/pw.chg/password-change-management.svg)](https://radar.anlyon.com/servers/pw.chg/password-change-management)

Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.

Password Change Management MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Password Change Management MCP server safe?

No scan can promise that. What its definitions show: 14 tools, 9 of which can change, send or delete something, and 7 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Password Change Management MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: backup.

Can the Password Change Management MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: send.

What tools does the Password Change Management MCP server have?

14 tools: 1 destructive, 1 irreversible, 7 write, 5 read. backup, send, shell, git_clone, browser_navigate, memory_write, user_profile, network_info and 6 more.

Does the Password Change Management MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Password Change Management MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): git_clone, browser_navigate and send.

Has the Password Change Management MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.