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.

DrissionPage MCP

PYPI · DRISSIONPAGE-MCP

Local browser automation for MCP clients powered by DrissionPage.

Available components

+1 this week 96 Trust /100

Last scanned (17 hours ago)

Scores higher than 99% 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
  • 1 of 43 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to jumodada/Drissionpage-MCP-Server). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 36 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability89
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 4571 tokens (~65/item across 70 items; 69 tools + 1 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 70 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.

  • 15 Oct 26 +1

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

  • 13 Oct 26 +12
    • Known CVEs: unverified → pass ▲ security
    • Dependency health: unverified → 0.99 ▲ functional
  • 12 Oct 26 −12
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 0.99 → unverified ▼ functional
  • 6 Oct 26 −2
    • Stability: pass → 0.83 functional
  • 4 Oct 26 0
    • Stability: 0.97 → pass security
  • 3 Oct 26 +1

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

  • 1 Oct 26 +1

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

  • 29 Sept 26 +11
    • Provenance: unverified → pass ▲ security
    • The attested source repository moved: jumodada/Drissionpage-MCP-Server security
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/drissionpage-mcp@0.8.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo jumodada/Drissionpage-MCP-Server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/jumodada/Drissionpage-MCP-Server/.github/workflows/publish-mcp-registry.yml@refs/tags/v0.8.5
Rekor log index 2546208681
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:3468ff41b895b2dc66ef3b26d48f4d17dd9ca4b03a7416f7db8e5a2e381febc1

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 43 packages
Packages resolved 43
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 69 exposed · ~4,553 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
page_pointer_move ~115

Move the viewport pointer to exact CSS pixel coordinates without pressing a button, using either one direct move or a bounded natural trajectory.

NameTypeReqDescription
elementstring–Human-readable element or interaction description
profilestring–Movement profile: direct emits one exact move; natural emits a deterministic 24-step eased cubic Bezier path with bounded 8-14ms intervals and an exact endpoint
xnumberyesViewport X coordinate in CSS pixels
ynumberyesViewport Y coordinate in CSS pixels

Structured output declared, but exposes no named fields.

No examples provided.

page_refresh ~13

Refresh the current page

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

page_resize ~40

Resize the browser window to specified dimensions

NameTypeReqDescription
heightintegeryesHeight of the browser window
widthintegeryesWidth of the browser window

Structured output declared, but exposes no named fields.

No examples provided.

page_screenshot ~31

Take an inline screenshot of the current page

NameTypeReqDescription
full_pageboolean–Take a full page screenshot

Structured output declared, but exposes no named fields.

No examples provided.

page_screenshot_save ~58

Save a screenshot to a local path under DP_MCP_SCREENSHOT_ROOT

NameTypeReqDescription
full_pageboolean–Take a full page screenshot
pathstringyesLocal file path under DP_MCP_SCREENSHOT_ROOT to save screenshot

Structured output declared, but exposes no named fields.

No examples provided.

page_scroll ~84

Scroll the current page by direction or to a position.

NameTypeReqDescription
directionstring–Scroll direction or target: down, up, left, right, top, bottom, half, position.
pixelsinteger–Pixel distance for directional scrolling.
xinteger–X coordinate for direction=position.
yinteger–Y coordinate for direction=position.

Structured output declared, but exposes no named fields.

No examples provided.

page_snapshot ~82

Return a bounded page outline with text excerpt, headings, links, buttons, inputs, forms, and recommended selectors.

NameTypeReqDescription
include_htmlboolean–Include bounded outerHTML excerpts for summarized elements
max_elementsinteger–Maximum total headings/links/buttons/inputs/forms to return
max_text_charsinteger–Maximum page text excerpt characters to return

Structured output declared, but exposes no named fields.

No examples provided.

shadow_find ~57

Find one element inside a shadow root exposed by the supported DrissionPage runtime.

NameTypeReqDescription
host_selectorstringyesSelector for the shadow host element.
selectorstringyesSelector inside the shadow root.
timeoutnumber––

Structured output declared, but exposes no named fields.

No examples provided.

shadow_find_all ~66

Find repeated elements inside a shadow root exposed by the supported DrissionPage runtime.

NameTypeReqDescription
host_selectorstringyesSelector for the shadow host element.
include_htmlboolean––
limitinteger––
selectorstringyesSelector inside the shadow root.

Structured output declared, but exposes no named fields.

No examples provided.

storage_clear ~41

Clear one key or all items from localStorage/sessionStorage.

NameTypeReqDescription
areastring––
keystring–Optional key. Empty clears the area.

Structured output declared, but exposes no named fields.

No examples provided.

storage_get ~69

Read localStorage or sessionStorage by key or as a bounded map, with values redacted unless explicitly requested.

NameTypeReqDescription
areastring––
include_valuesboolean–Return storage values instead of redacting non-empty values.
keystring–Optional key. Empty returns all keys.

Structured output declared, but exposes no named fields.

No examples provided.

storage_set ~52

Set one localStorage/sessionStorage item. The value is not echoed.

NameTypeReqDescription
areastring––
keystringyes–
valuestringyesString value to store. Not echoed in result.

Structured output declared, but exposes no named fields.

No examples provided.

tab_close ~47

Close a browser tab by id from tab_list without closing the whole browser.

NameTypeReqDescription
tab_idstringyesMCP tab id from tab_list, or the underlying DrissionPage native tab id.

Structured output declared, but exposes no named fields.

No examples provided.

tab_list ~21

List browser tabs tracked by the current DrissionPage MCP session.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

tab_switch ~43

Switch the active browser tab by id from tab_list.

NameTypeReqDescription
tab_idstringyesMCP tab id from tab_list, or the underlying DrissionPage native tab id.

Structured output declared, but exposes no named fields.

No examples provided.

wait_for_element ~81

Wait for an element to appear on the page. Bare selectors are treated as CSS; use text:... for text matching.

NameTypeReqDescription
selector–yesCSS selector or XPath to wait for. Bare selectors are CSS; use text:... for text matching or explicit tag:/css:/xpath:/@attr locators.
timeoutnumber–Timeout in seconds

Structured output declared, but exposes no named fields.

No examples provided.

wait_for_url ~46

Wait for the current URL to contain a substring

NameTypeReqDescription
timeoutnumber–Timeout in seconds
url_patternstringyesSubstring or pattern expected in the current URL

Structured output declared, but exposes no named fields.

No examples provided.

wait_time ~28

Wait for a specific amount of time

NameTypeReqDescription
secondsnumberyesNumber of seconds to wait

Structured output declared, but exposes no named fields.

No examples provided.

wait_until ~139

Wait for observable page state: element present/visible/hidden/detached/clickable/stable, text contains/matches, or URL contains/matches.

NameTypeReqDescription
conditionstringyesCondition to wait for
intervalnumber–Polling interval in seconds
namestring–Attribute or property name for attribute/property conditions
selector––CSS/XPath/DrissionPage locator for element or text conditions
stable_msinteger–Element stability window for the stable condition
timeoutnumber–Timeout in seconds
valuestring–Expected value or substring/regular expression, depending on condition

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the DrissionPage MCP server?

DrissionPage MCP runs locally as a PyPI package, launched with uvx drissionpage-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 · drissionpage-mcp

# add to Claude Code
claude mcp add jumodada-drissionpage-mcp -- uvx drissionpage-mcp
Common questions

What is the DrissionPage MCP server?

DrissionPage MCP is listed in the public MCP registry as io.github.jumodada/drissionpage-mcp. Local browser automation for MCP clients powered by DrissionPage. This page covers its PyPI package (drissionpage-mcp).

Is the DrissionPage MCP server safe to use?

DrissionPage MCP scores 96 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. Its build provenance is signed and verified. 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 DrissionPage MCP server expose?

DrissionPage MCP exposes 69 tools: page_navigate, page_navigate_with_http_auth, page_go_back, page_go_forward, page_refresh, and 64 more. Their descriptions and schemas cost roughly 4,553 tokens of context every time the server is loaded.

Is the DrissionPage MCP server still maintained?

DrissionPage MCP 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 DrissionPage MCP server under?

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