Skip to content

MCP servers › ai.monity › monity

MCP server · registry snapshot 2026-11-09 · last tested 2026-11-09

monity MCP server

Registry name ai.monity/monity

monity.ai — the publisher's title

by monity.ai · domain (the registry's namespace rule)npm ↗Website ↗

Let your AI watch web pages, alert you to changes, and show what any page said on any past date. — the publisher's description

3 of 6 record checks metRead-only · tools listed 2026-11-09version 1.0.2MITstandard input/output, streamable HTTP27 tools

Summary

ai.monity/monity is a remote and local MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the domain monity.ai. On 2026-11-09 ProtocolProbe connected to it in read-only mode and read its inventory: 27 tools, 4 resources and 0 prompts.

Record checks

3 of 6 record checks met · 3 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • met: Package names its licence with a standard (SPDX) identifier
  • met: The version the registry lists can be installed and is not withdrawn
  • not met: npm package carries build provenance (attestation)
  • not met: No known critical or high advisory in the package or its dependencies
  • #11,658 of 20,610 packages by monthly downloads, tied with 30 others
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
remote and local package
Transport
standard input/output, streamable HTTP
Your own values
for the package, a secret: MONITY_API_KEY
Sign-in
none needed to open a session
Package
npm · listed version current
License
MIT
Dependencies
2 packages with a critical or high advisory (0 critical, 2 high)
Tools
27
Last tested
2026-11-09

Tool list size

16,320 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (27 tools). Counted with Anthropic's token counter on 2026-11-09, from the tool list we read on 2026-11-09. Median across 28,560 counted servers: 2,657 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-09 (api.monity.ai), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.2).

Add to your client

Observed fact

This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (load_editor_preview, save_task_editor, create_monitor, update_monitor, delete_monitor and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-09.

Worth knowing before you connect it

  • 2 packages with a critical or high advisory (0 critical, 2 high) in its dependencies (as resolved on 2026-11-09).

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-09
Mode
read-only (no tool calls)
Latest version
1.0.2, published 2026-11-08 (registry, as of the 2026-11-09 snapshot)
First listed version
2026-11-08 (earliest version still in the registry; older removed versions would be earlier)
Version history
3 versions listed, all on 2026-11-08; 3 in the 90 days before the 2026-11-09 snapshot.
Most recent 3 versions
  • 1.0.2 · 2026-11-08
  • 1.0.1 · 2026-11-08
  • 1.0.0 · 2026-11-08
(versions still listed in the registry only)
Registry data
snapshot 2026-11-09
Package and repository
checked 2026-11-09
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn. Does not apply: repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-08, listed on 2026-11-09 with version 1.0.2 (published 2026-11-08).

Source: the official MCP Registry list on 2026-11-08 and on 2026-11-09.

What it is

What does this server offer?

Observed inventory
27tools
4resources
0prompts

None of its 27 tools are described as changing anything. For 27 the reading was uncertain, so no mark is shown.

  • get_editor_capabilities

    “Whether this connection may open the embedded task editor.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • open_task_editor

    “Open the existing Monity task editor.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs
    • uuidstring
    • workspaceIdinteger
  • load_editor_preview

    “Fetch the configured public page in Monity and run its browser steps for an editor preview; does not save a task.”

    Publisher declares: read-only no · destructive yes · open-world yes

    2 inputs, 2 required
    • sessionIdstringrequired
    • settingsobjectrequired
  • get_editor_preview

    “Read the current editor-owned preview status and screenshot.”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 2 required
    • sessionIdstringrequired
    • previewIdstringrequired
  • cancel_editor_preview

    “Cancel the current editor-owned preview.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 2 required
    • sessionIdstringrequired
    • previewIdstringrequired
  • save_task_editor

    “Save the settings explicitly submitted in the task editor.”

    Publisher declares: read-only no · destructive yes · open-world yes

    2 inputs, 2 required
    • sessionIdstringrequired
    • settingsobjectrequired
  • list_monitorson 29 other servers

    “List the website monitors (tasks) in the monity.ai account: name, monitored URL, type, active state, labels, and last/next check times.”

    Publisher declares: read-only yes · destructive no · open-world no

    14 inputs
    • pageinteger“Page number (default 1)”
    • limitinteger“Results per page (default 25, max 100)”
    • searchstring“Search monitor name or URL, case insensitive”
    • sortstring“Task list sort order; default newest created”
    • activeboolean“Filter by active state”
    • labelstring“Filter by label name”
    • workspaceIdinteger“Only monitors in this workspace (from list_workspaces)”
    • frequenciesarray“Only monitors checking at one of these frequencies (minutes, as strings)”
    • thresholdsarray“Only monitors with one of these change thresholds”
    • compareTypesarray“Only monitors of these compare types”
    • labelIdsarray“Only monitors carrying one of these labels (ids from list_labels)”
    • createdOnstring“Only monitors created on this date (yyyy-mm-dd, UTC)”
    • lastAlertFromstring“Only monitors whose last change is on or after this ISO date”
    • lastAlertTostring“Only monitors whose last change is on or before this ISO date”
  • “List the labels on monitors in the monity.ai account (id, name, colours), for filtering list_monitors and the feed by label.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • “Get one monitor's configuration summary by uuid (type, frequency, threshold, extractor, labels, skills and their alert rules, timestamps).”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
  • get_latest_result

    “Get a monitor's most recent completed check: status, whether it alerted, the extracted output (current and previous value), AI summary, and artifact URLs (screenshots, diff image, HTML snapshot).”

    Publisher declares: read-only yes · destructive no · open-world no

    1 input, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
  • get_check_historyon 2 other servers

    “List a monitor's past checks (newest first): timestamps, status, alerted flag, percent difference, errors.”

    Publisher declares: read-only yes · destructive no · open-world no

    10 inputs, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
    • statusstring“Filter by status: ALERT_SENT, CHANGE, NO_CHANGE, or ERROR”
    • fromstring“ISO date lower bound (inclusive)”
    • tostring“ISO date upper bound (inclusive)”
    • pageinteger“Page number (default 1)”
    • limitinteger“Results per page (default 10 here, max 100)”
    • includeHiddenboolean“Include changes the user hid (hide_change).”
    • detailboolean“Each check in full, with its evidence links, as get_check returns it.”
    • sortstring“Order (default newest first)”
    • taskPanelboolean“List what the Monity task panel lists: no skipped checks, failed checks only when the monitor alerts on errors.”
  • “Get the full detail of one specific check by id, shown as evidence the user can inspect: before/after screenshots with a comparison slider, the highlighted difference, the AI summary of what changed,…”

    Publisher declares: read-only yes · destructive no · open-world no

    2 inputs, 2 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
    • checkIdstringrequired“Check id (from get_check_history)”
Show 15 more tools
  • view_check_screenshot

    “Returns the actual screenshot image from a check, so you can SEE the monitored page rather than infer it from a diff percentage.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
    • checkIdstring“Check id (from get_check_history), or 'latest' for the most recent completed check.”
    • viewstring“Which image: 'current' (default), 'previous', or 'diff' with changes highlighted”
    • maxWidthinteger“Longest width to scale to, default 1200, max 4000”
    • maxHeightinteger“Height bound, default 3000, max 4000.”
  • “Who is connected and what their monity.ai plan allows: plan name, credit refresh date, active monitors used and slots left per workspace, check credits left (a check normally costs one), and the chec…”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • list_workspaceson 49 other servers

    “List the account’s workspaces (business accounts hold several; personal accounts have one).”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • get_recent_changeson 25 other servers

    “Account-wide feed of completed checks, newest first, each already carrying its monitor (name + URL), the AI summary of what changed, and the extracted output.”

    Publisher declares: read-only yes · destructive no · open-world no

    9 inputs
    • alertedOnlyboolean“true (default) returns only checks that detected a change and alerted; false returns every completed check”
    • fromstring“ISO date lower bound, inclusive — e.g.”
    • tostring“ISO date upper bound (inclusive)”
    • labelstring“Only monitors carrying this label”
    • monitorUuidstring“Restrict to a single monitor (from list_monitors)”
    • statusstring“Explicit status filter: ALERT_SENT, CHANGE, NO_CHANGE or ERROR.”
    • pageinteger“Page number (default 1)”
    • limitinteger“Results per page (default 25, max 100)”
    • includeHiddenboolean“Include changes the user hid (hide_change) or their team hid in Monity (teamHidden: true).”
  • open_monity

    “Show the pages the user watches and what changed on them: open the user's monity.ai home, every monitor with its state and last check, and the latest changes with screenshots.”

    Publisher declares: read-only yes · destructive no · open-world no

    Takes no inputs.

  • create_monitoron 22 other servers

    “Watch a web page and alert the user when it changes: price drops, restocks, new posts or listings, status changes, competitor updates, any 'tell me when this page changes'.”

    Publisher declares: read-only no · destructive no · open-world yes

    15 inputs, 1 required
    • websiteUrlstringrequired“Absolute http(s) URL of the page to monitor”
    • selectorstring“CSS selector of ONE element to watch instead of the whole page (e.g.”
    • labelsarray“Label names to file the monitor under (up to 10); existing labels with the same name are reused.”
    • namestring“Monitor name (defaults to the URL host/path)”
    • compareTypestring“Comparison mode (default AUTO)”
    • frequencystring“Minutes between checks, as a string: '5', '15', '30', '60' (hourly), '180', '360', '720', '1440' (daily), '10080' (weekly), '302400' (monthly).”
    • notifyWhenstring“Natural-language alert condition evaluated by AI on every check, e.g.”
    • notifyConditionsarray“Deterministic alert conditions on the extracted output (no AI credits).”
    • jsonPathstring“For JSON API endpoints: JSONPath to the value to monitor, e.g.”
    • outputExtractorstring“How to extract the monitored value from the page text: NUMBER pulls the first number (good for prices), REGEX applies outputExtractorPattern, NONE keeps the fu…”
    • outputExtractorPatternstring“Regular expression for outputExtractor: REGEX — bare pattern or /pattern/flags; the first capture group (or full match) becomes the monitored output, e.g.”
    • keywordsstring“TEXT monitors only: comma-separated keywords to watch for, e.g.”
    • keywordsActionstring“TEXT monitors only: alert when keywords are ADDED to the page (default) or REMOVED from it”
    • actionsarray“Ordered list of interactions to perform before each check, e.g.”
    • workspaceIdinteger“Workspace to create the monitor in (from list_workspaces): one of the workspaces this connection may use.”
  • update_monitoron 16 other servers

    “Update an existing monitor: rename, change frequency, pause/resume, or change its alert conditions, extraction, pre-check actions, skills and their alert rules.”

    Publisher declares: read-only no · destructive yes · open-world yes

    13 inputs, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
    • namestring“New monitor name”
    • frequencystring“Minutes between checks, as a string: '5', '15', '30', '60' (hourly), '180', '360', '720', '1440' (daily), '10080' (weekly), '302400' (monthly).”
    • activeboolean“true resumes checks, false pauses them”
    • notifyWhenstring or null“Natural-language alert condition evaluated by AI on every check, e.g.”
    • notifyConditionsarray or null“Deterministic alert conditions on the extracted output (no AI credits).”
    • jsonPathstring or null“For JSON API endpoints: JSONPath to the value to monitor, e.g.”
    • outputExtractorstring“How to extract the monitored value from the page text: NUMBER pulls the first number (good for prices), REGEX applies outputExtractorPattern, NONE keeps the fu…”
    • outputExtractorPatternstring or null“Regular expression for outputExtractor: REGEX — bare pattern or /pattern/flags; the first capture group (or full match) becomes the monitored output, e.g.”
    • keywordsstring or null“TEXT monitors only: comma-separated keywords to watch for, e.g.”
    • keywordsActionstring“TEXT monitors only: alert when keywords are ADDED to the page (default) or REMOVED from it”
    • actionsarray or null“Ordered list of interactions to perform before each check, e.g.”
    • labelsarray or null“Label names for the monitor (up to 10).”
  • “Check an active monitor's page now instead of waiting for its schedule.”

    Publisher declares: read-only no · destructive no · open-world yes

    1 input, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
  • delete_monitoron 16 other servers

    “Permanently delete a monitor with all its checks, screenshots and HTML copies.”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
  • hide_change

    “Hide one detected change from this user's history and recent changes (for example a false alarm).”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 2 required
    • uuidstringrequired“Monitor uuid”
    • checkIdstringrequired“Check id of the change (from get_recent_changes or get_check_history)”
  • unhide_change

    “Show a change the user hid with hide_change in their history and recent changes again.”

    Publisher declares: read-only no · destructive no · open-world no

    2 inputs, 2 required
    • uuidstringrequired“Monitor uuid”
    • checkIdstringrequired“Check id of the hidden change”
  • pause_monitoron 9 other servers

    “Pause a monitor (stops scheduled checks; history is kept).”

    Publisher declares: read-only no · destructive yes · open-world no

    1 input, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
  • resume_monitoron 7 other servers

    “Resume a paused monitor.”

    Publisher declares: read-only no · destructive no · open-world yes

    1 input, 1 required
    • uuidstringrequired“Monitor uuid (from list_monitors)”
  • “The person's Monity feed: alerted changes they have not marked read, newest first, with the unread count.”

    Publisher declares: read-only yes · destructive no · open-world no

    5 inputs
    • cursorstring“From the previous page's nextCursor”
    • limitinteger“Items per page (default 20, max 50)”
    • includeReadboolean“Also list changes already marked read”
    • labelIdsarray“Only changes on monitors carrying one of these labels (ids from list_labels)”
    • includeHiddenboolean“Also list changes the team hid in Monity (teamHidden: true).”
  • mark_feed_read

    “Mark one change read (it leaves the feed), unread again, or everything in the feed read.”

    Publisher declares: read-only no · destructive no · open-world no

    3 inputs
    • checkIdstring“The change to mark; omit with all: true”
    • allboolean“Mark everything in the feed read”
    • unreadboolean“Put checkId back as unread”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-09.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
90% of 96
Tools with a description
100% of 27
Typical description length
309 characters

The tool set

Counted from the listing

Tools
27
Size of the list
about 11,942 tokens for an agent to load (characters ÷ 4)
Naming
27 of 27 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the npm package monity-mcp

This entry needs values of your own (marked < > or { } in the config below), so there is no one-click link: paste the config and fill them in.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
  "mcpServers": {
    "monity": {
      "command": "npx",
      "args": [
        "-y",
        "monity-mcp@0.5.0"
      ],
      "env": {
        "MONITY_API_KEY": "<MONITY_API_KEY>"
      }
    }
  }
}
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "monity": {
      "command": "npx",
      "args": [
        "-y",
        "monity-mcp@0.5.0"
      ],
      "env": {
        "MONITY_API_KEY": "<MONITY_API_KEY>"
      }
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "monity": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "monity-mcp@0.5.0"
      ],
      "env": {
        "MONITY_API_KEY": "${input:monity-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "monity-api-key",
      "description": "MONITY_API_KEY",
      "password": true
    }
  ]
}
Claude Code
claude mcp add --env "MONITY_API_KEY=<MONITY_API_KEY>" --transport stdio monity -- npx -y monity-mcp@0.5.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "monity": {
      "command": "npx",
      "args": [
        "-y",
        "monity-mcp@0.5.0"
      ],
      "env": {
        "MONITY_API_KEY": "<MONITY_API_KEY>"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "monity": {
      "command": "npx",
      "args": [
        "-y",
        "monity-mcp@0.5.0"
      ],
      "env": {
        "MONITY_API_KEY": "<MONITY_API_KEY>"
      }
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.monity]
command = "npx"
args = ["-y", "monity-mcp@0.5.0"]

[mcp_servers.monity.env]
"MONITY_API_KEY" = "<MONITY_API_KEY>"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "monity": {
      "command": "npx",
      "args": [
        "-y",
        "monity-mcp@0.5.0"
      ],
      "env": {
        "MONITY_API_KEY": "<MONITY_API_KEY>"
      }
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -e "MONITY_API_KEY=<MONITY_API_KEY>" -- npx -y monity-mcp@0.5.0
  • Replace <MONITY_API_KEY> with your own values; the entry marks MONITY_API_KEY as secret, so keep the file out of version control.
  • This runs the publisher's code on your machine (npx). Read its README first.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-09 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://api.monity.ai/plugins/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "monity": {
      "url": "https://api.monity.ai/plugins/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "monity": {
      "type": "http",
      "url": "https://api.monity.ai/plugins/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"monity","type":"http","url":"https://api.monity.ai/plugins/mcp"}'
Claude Code
claude mcp add --transport http monity https://api.monity.ai/plugins/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "monity": {
      "type": "streamableHttp",
      "url": "https://api.monity.ai/plugins/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "monity": {
      "httpUrl": "https://api.monity.ai/plugins/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.monity]
url = "https://api.monity.ai/plugins/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "monity": {
      "url": "https://api.monity.ai/plugins/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://api.monity.ai/plugins/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists
0.5.0
Latest stable
0.5.0
Status
current
Withdrawn
no

Source: registry.npmjs.org · 2026-11-09. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

critical0high2moderate0low0

Counted in the full dependency tree as resolved on 2026-11-09 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity
sha512-qkO0OmYs4XybUnouO…
Signature
signed
License
MIT

Source: the package registry · 2026-11-09.

Usage

Downloads
309 in the last month

Source: api.npmjs.org · 2026-11-09.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

Registry entry

  • Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-10.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.

Own host

  • security.txt. No security.txt at https://api.monity.ai/.well-known/ (HTTP 404, 2026-11-10). No security.txt at https://monity.ai/.well-known/ (HTTP 404, 2026-11-10). Source: api.monity.ai/.well-known/security.txt · read 2026-11-10.
  • A2A agent card. No A2A agent card at https://api.monity.ai/.well-known/ (HTTP 404, 2026-11-10). No A2A agent card at https://monity.ai/.well-known/ (HTTP 404, 2026-11-10). Source: api.monity.ai/.well-known/agent-card.json · read 2026-11-10.

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint api.monity.ai/plugins/mcpSession openedmatchesour test · 2026-11-09
A secret is declared as requiredOpened a session without any credentialdiffersour test · 2026-11-09
Version 0.5.0 on npmExists and can be installedmatchesnpm · 2026-11-09

Choosing

Record checks

Public records · not a safety rating

3 of 6 record checks met · 3 do not apply

  • #11,658 of 20,610 packages by monthly downloads, tied with 30 others
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • MetPackage names its licence with a standard (SPDX) identifierMIT
  • MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
  • Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
  • Not metNo known critical or high advisory in the package or its dependencies2 packages in its dependencies with a critical or high advisory (npm audit counts packages, not advisories).What changes this check: npm's documentation describes listing a project's dependency advisories with npm audit and applying compatible dependency updates. npm: npm audit

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-09. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about ai.monity/monity

Answered from the data above

Who publishes ai.monity/monity?

The registry ties the namespace ai.monity to the domain monity.ai; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Is ai.monity/monity safe to install?

We do not rate servers as safe or unsafe. 3 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has packages with advisories (2 high; npm audit). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does ai.monity/monity need an API key or sign-in?

It opened a session without any credential on 2026-11-09. The registry entry declares a required secret.

Has ai.monity/monity been security tested?

Partly. 4 of the 15 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Is the listed version current?

Yes. The registry lists 0.5.0, the latest stable release on npm.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-09
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

4 exercised11 not run (reason given)3 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 4 of the 15 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 4
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes, except for a server whose operator has claimed it and given permission (that server's page says so); an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 3
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-09, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 2,207 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 27 tools, 4 resources, 0 prompts.
  4. 8,650 msFinished: 4 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-09; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-11-09
MCP capability
resources, tools
our test · 2026-11-09
Transport
standard input/output, streamable HTTP
registry · 2026-11-09
Required credentials
requires a secret
registry · 2026-11-09 · no declaration is not a guarantee
Package registry
registry · 2026-11-09
Freshness
0–30 days
registry updatedAt · 2026-11-09
Lifecycle status
registry · 2026-11-09
License class
package registry · 2026-11-09
Integrity hash
declared (sri)
package registry · 2026-11-09
Signature / provenance
signed
package registry · 2026-11-09
Dependency advisories
high
npm audit · 2026-11-09
Popularity
309 downloads a month
package registry · 2026-11-09
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
either (remote or your machine)
where it runs, from the hosting type · 2026-11-09

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “ai.monity/monity: MCP server record.” Data checked 2026-11-09. https://protocolprobe.com/mcp/servers/ai.monity/monity

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 3 of 6 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/ai.monity/monity)](https://protocolprobe.com/mcp/servers/ai.monity/monity)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology