Dejo
PYPI · DEJO-MCP
A browser your AI agent remembers. Learn a site once, replay it in one call, zero model calls.
Available components
Last scanned (14 minutes ago)
Scores higher than 59% of PyPI servers
Category Browser Automation
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 890 tokens (~178/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability check failed: the tool surface changed between 0.1.2 and 0.2.0: 13 tool removals, 3 breaking changes, 2 additions. See how to fix → Fail
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 23 Oct 26 +2
- Stability: unverified → fail ▼ security
- Tool coverage: 0% → 44% ▲ functional
- Schema quality: 360 → 178 ▲ functional
- Package version: 0.1.2 → 0.2.0 functional
- 19 Oct 26 50
First indexed and scored.
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 23 Oct 2026 · Analysed pypi/dejo-mcp@0.2.0
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 | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
dejo_login ~118
Sign in to a website, website login, SSO, Google sign-in, one-time code. Opens a visible browser window so the USER signs in; never type a password you were not given. Call with site, tell the user to sign in there, then call again with done=true. Signs in the current profile only, and it stays signed in.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean | – | user insists, though a sign-in page still shows |
| done | boolean | – | the user says they are signed in |
| site | string | yes | – |
No output schema declared.
No examples provided.
dejo_manage ~109
Change what Dejo remembers about a website. do=forget removes a site (or one task) for good; do=note keeps a fact that is not a step (needs 2FA, use the finance account); do=share offers a trail to other agents (typed values never leave); do=borrow takes a shared trail.
| Name | Type | Req | Description |
|---|---|---|---|
| do | string | yes | – |
| site | string | yes | – |
| task | string | – | – |
| text | string | – | the fact, for note |
No output schema declared.
No examples provided.
dejo_memory ~92
What Dejo remembers about websites. Read only. what=sites lists every trail and its health; what=show gives one trail's steps; what=map lists pages seen on a site (with path: that page's controls); what=commons lists trails other agents shared.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | – |
| site | string | – | – |
| task | string | – | – |
| what | string | yes | – |
No output schema declared.
No examples provided.
dejo_profile ~68
Website profiles and roles: customer, vendor, admin. A profile is a whole signed-in browser; several stay signed in side by side. With a name: switch to it (made on first use). Without: list them. Trails are shared by every profile.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
No output schema declared.
No examples provided.
dejo_run ~382
Use for ANY website task: read a value, fill a form, download, check a page. A real browser with memory: a task done once is replayed later with no page reading. Call with site, task and url. Known task: Dejo replays it and returns the answer. New task: Dejo opens the url and returns the page, one line per element, each with a ref (e12). Then call again with steps, one per line. They run in order. Dejo stops at the first step that fails and returns the page there. Steps: go URL click T | fill T "text" | select T "option" | check T | press Enter read T as name (the value you will report) expect url "part" | expect text "words" | expect see T look words (show the page, these words first) Also: back, hover T, wait T, upload T "file", tab N. T is a ref, or role "name" (link "Travel"), text "...", label "...", css "...". Add first, last or nth 3 to mean that place in a list, not that item. Write click! (or fill! etc.) for a step that buys, pays, sends, deletes or submits. Passed steps are kept. When all steps pass and one is a read (or a file downloads), the task is saved. done=true saves a task that reads nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| done | boolean | – | – |
| profile | string | – | signed-in role to use, e.g. admin |
| site | string | yes | domain or URL |
| steps | string | – | step lines, see above |
| task | string | yes | the job in plain words; the trail's name |
| url | string | – | where to start |
No output schema declared.
No examples provided.
How do I install the Dejo MCP server?
Dejo runs locally as a PyPI package, launched with uvx dejo-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 · dejo-mcp
claude mcp add dejohq-dejo-mcp -- uvx dejo-mcp
What is the Dejo MCP server?
Dejo is an MCP server listed in the public MCP registry as io.github.dejohq/dejo-mcp. A browser your AI agent remembers. Learn a site once, replay it in one call, zero model calls. This page covers its PyPI package (dejo-mcp).
Is the Dejo MCP server safe to use?
Dejo scores 52 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 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 Dejo MCP server expose?
Dejo exposes 5 tools: dejo_run, dejo_login, dejo_profile, dejo_memory, dejo_manage. Their descriptions and schemas cost roughly 769 tokens of context every time the server is loaded.
Is the Dejo MCP server still maintained?
Dejo is still listed as active in the MCP registry. We last reached this channel on 23 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 Dejo MCP server under?
Dejo declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.