Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Morfiade

PYPI · MORFIADE-MCP

Manage local Chrome profiles on Windows: own cookies, sessions and proxy per profile.

Available components

+21 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 87% of PyPI servers

Category Browser Automation

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1781 tokens (~93/item across 19 items; 19 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Oct 26 +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.

  • 14 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 12 Oct 26 +4

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 67. That category is still filling its 30-day observation window: 12 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.

  • 3 Oct 26 +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.

  • 1 Oct 26 +1

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

  • 29 Sept 26 +1
    • Provenance: unverified → fail ▼ security
  • 28 Sept 26 −15
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +17
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.17 ▲ functional
    • Package version: 0.2.2 → 0.2.3 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Analysed pypi/morfiade-mcp@0.2.3

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 19 exposed · ~1,758 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_proxies ~83

Test the proxies of several profiles, or of every profile available to the agent when no list is given. Checks run one after another, up to about ten seconds each, so a long list takes minutes. Changes nothing. Profiles without a proxy are reported as such.

NameTypeReqDescription
profilesarray–Profile names to check; omit to check every profile available to the agent

No output schema declared.

No examples provided.

check_proxy ~67

Test one profile's proxy by making a request through it: whether it answers, the exit IP and country, and latency. Changes nothing; takes up to about ten seconds. For several profiles use check_proxies instead.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it

No output schema declared.

No examples provided.

create_profile ~195

Create a new, empty Chrome profile on disk and allow it for the agent. It is not launched: call start_profile for that. Fails if the name is already taken; use list_profiles to see existing names. Proxy, note and category can be set at once or later with set_proxy and profile_note.

NameTypeReqDescription
categorystring–Category to file the profile under; created if missing; optional
namestringyesName for the new profile; must not match an existing one
notestring–Free-text note shown in the profile table; optional
proxystring–Proxy as host:port, host:port:login:password, or scheme://login:password@host:port where scheme is http, socks4 or socks5; optional
proxy_typestring–Proxy protocol; defaults to http. Ignored when the proxy string already starts with a scheme

No output schema declared.

No examples provided.

list_profiles ~116

List the browser profiles the owner has allowed for the agent (the "API" column in Morfiade); other profiles are invisible here. For each: name, whether it is running, proxy (password hidden), proxy type, the last proxy check (alive or not, and when), category, antidetect on/off, debug_port (debug-port mode: Cloudflare checks and Google sign-in never pass with it), note and launch count. Read-only. Call it first: every other tool takes a profile name exactly as listed here.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_scripts ~42

Scripts in Morfiade's scripts folder: file name, the program that runs it, and whether that program is installed. File contents are never shown. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_trash ~38

Profiles in the recycle bin: name, when it was deleted and how much disk it takes. Read-only; use the names with restore_profile.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

page_info ~77

What the active tab of a running profile shows right now: title, address, whether loading has finished, and whether it is a Cloudflare check page. Use it after start_profile to see whether the site actually opened. Reads nothing else from the page and changes nothing.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it

No output schema declared.

No examples provided.

profile_note ~106

Read or write a profile's note. Without title and note it only reads. title is the short line shown in the profile table, note the full text; a field you pass overwrites the old value, a field you omit stays as it was.

NameTypeReqDescription
notestring–Full note text; omit to keep
profilestringyesProfile name exactly as list_profiles returns it
titlestring–Short title shown in the profile table; omit to keep

No output schema declared.

No examples provided.

profile_tags ~111

Read a profile's tags, or replace them all. Without tags it only reads. With tags the list you pass becomes the whole set: tags you leave out are removed, and an empty list clears them. To add one tag, read first and pass the old list plus the new tag.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it
tagsarray–New full list of tags, replacing the old one; omit to only read; an empty list clears all tags

No output schema declared.

No examples provided.

restore_profile ~66

Bring a profile back from the recycle bin with its cookies and sessions. If the name has been taken meanwhile, it returns as "name (2)" and nothing is overwritten; the answer says which name it got.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it

No output schema declared.

No examples provided.

set_proxy ~146

Save a proxy in a profile's settings, replacing the current one; an empty string removes it. Takes effect on the next launch: a running profile keeps its old proxy until stop_profile and start_profile. Run check_proxy afterwards to see whether it works.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it
proxystringyesProxy as host:port, host:port:login:password, or scheme://login:password@host:port where scheme is http, socks4 or socks5; empty string removes the proxy
typestring–Proxy protocol; defaults to http. Ignored when the proxy string already starts with a scheme

No output schema declared.

No examples provided.

start_profile ~124

Launch a profile: opens its real Chrome window with its own cookies, sessions and proxy. If the profile is already running, only opens the URL in a new tab of that window. Can take up to a minute and needs a valid Morfiade licence. The answer warns when the last proxy check failed or the profile runs in debug-port mode. Call page_info afterwards to see whether the page actually opened.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it
urlstring–Address to open, with scheme (https://...); optional

No output schema declared.

No examples provided.

status ~48

Morfiade version, how many profiles exist, how many the agent may use and how many are running right now. Read-only and instant; use it to check the manager is reachable before anything else.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

stop_profile ~78

Close a running profile's Chrome window. Nothing is deleted: cookies, sessions and history stay in the profile, and the next start_profile picks them up. Text typed into pages but not submitted is lost. Calling it on a stopped profile is harmless and reports already_stopped.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it

No output schema declared.

No examples provided.

sync_insert ~133

Type each window's own pinned value into the input field that has the cursor in the leading window; the same field receives it in every window. A person must click into that field first. The text is inserted into the page as typed input and cannot be undone by the tool. Windows without a pinned line get the next free one now; call sync_spread first to review who gets what.

NameTypeReqDescription
leaderstring–Profile whose window shows where to type: the field focused there receives the values in every window; defaults to the first ready window
setstringyesSet name as sync_sets lists it

No output schema declared.

No examples provided.

sync_sets ~108

Value sets for distributing across windows: lists of emails, logins or any line-based data, one line per window. Without arguments lists the sets with their line count and how many lines are still free; the values themselves are never shown. With name and lines creates a new set.

NameTypeReqDescription
linesarray–Values for the new set, one per window: emails, logins, any line-based data
namestring–Name for a new set; give together with lines

No output schema declared.

No examples provided.

sync_spread ~94

Pin one free line of a set to each ready window and report who got what. Types nothing; that is sync_insert. Safe to repeat: windows that already hold a line keep it, so an account is never registered with one email and confirmed with another.

NameTypeReqDescription
profilesarray–Profiles whose windows get a line; defaults to every ready window
setstringyesSet name as sync_sets lists it

No output schema declared.

No examples provided.

sync_windows ~56

Which open profile windows can take part in distributing values, and which value each already holds. Windows that cannot (for example, antidetect off) are listed with the reason. Read-only; call it before sync_spread and sync_insert.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trash_profile ~70

Move a profile to Morfiade's recycle bin. Nothing is erased: the profile keeps its cookies and sessions and comes back with restore_profile. A running profile is closed first. Emptying the bin is not available to the agent.

NameTypeReqDescription
profilestringyesProfile name exactly as list_profiles returns it

No output schema declared.

No examples provided.

Install

How do I install the Morfiade MCP server?

Morfiade runs locally as a PyPI package, launched with uvx morfiade-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · morfiade-mcp

# add to Claude Code
claude mcp add morfiade-app-morfiade-mcp -- uvx morfiade-mcp
Common questions

What is the Morfiade MCP server?

Morfiade is an MCP server listed in the public MCP registry as io.github.morfiade-app/morfiade-mcp. Manage local Chrome profiles on Windows: own cookies, sessions and proxy per profile. This page covers its PyPI package (morfiade-mcp).

Is the Morfiade MCP server safe to use?

Morfiade scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. 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 Morfiade MCP server expose?

Morfiade exposes 19 tools: list_profiles, status, start_profile, stop_profile, set_proxy, and 14 more. Their descriptions and schemas cost roughly 1,758 tokens of context every time the server is loaded.

Is the Morfiade MCP server still maintained?

Morfiade is still listed as active in the MCP registry. We last reached this channel on 16 October 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 Morfiade MCP server under?

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