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.

ai-dev-workspace

PYPI · AI-DEV-WORKSPACE

Local Markdown task memory shared by Claude Code and Codex over stdio MCP.

Available components

66 Trust /100

Last scanned (17 hours ago)

Scores higher than 61% of PyPI servers

Category Productivity and Notes

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 Security94
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Declares code that runs automatically (setup.py, a custom setup.py cmdclass) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does. View diagnostics → Partial
  • No production dependencies, so there is no dependency health to assess. 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 Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 993 tokens (~35/item across 28 items; 28 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.Unverified
Tool Coverage69
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 6% 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 28 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 28 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 4 Nov 26 66

    First indexed and scored.

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 4 Nov 2026 · Analysed pypi/ai-dev-workspace@0.1.0b7

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 3 scripts
Hook Tier Command
build_backend allowlisted setuptools.build_meta
setup_py unreviewed <setup.py, unreviewed>
cmdclass unreviewed <custom, unreviewed>

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 · 28 exposed · ~993 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
add_feedback ~31

Record idea, bug, friction or praise.

NameTypeReqDescription
kindstring––
textstringyes–

No output schema declared.

No examples provided.

add_lesson ~41

Record a lesson with optional repo globs/area.

NameTypeReqDescription
areastring––
pathsarray––
textstringyes–

No output schema declared.

No examples provided.

assist ~22

Up to two local suggestions; ask before applying. No installs/config edits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

brief ~12

Show local task memory.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

checkpoint ~71

Save status, exact next action and section updates.

NameTypeReqDescription
expected_shastring–Rejects stale writes
idstringyes–
nextstringyes–
notesobject––
statusstringyes–
tokenstring––
workerstring––

No output schema declared.

No examples provided.

claim_task ~32

Claim before edits; returns checkpoint/release token.

NameTypeReqDescription
idstringyes–
workerstringyes–

No output schema declared.

No examples provided.

codebase_map ~22

Map configured or supplied repo.

NameTypeReqDescription
repostring––

No output schema declared.

No examples provided.

connect_client ~27

Write project config; Codex global config is preview-only.

NameTypeReqDescription
clientstringyes–

No output schema declared.

No examples provided.

delegate ~43

Prepare unverified bounded work (reviewer: git range); never execute.

NameTypeReqDescription
diffstring––
rolestringyes–
taskstringyes–

No output schema declared.

No examples provided.

digest_file ~37

Summarize a JSON or log file.

NameTypeReqDescription
focusstring–Regex; matching lines come first.
pathstringyes–

No output schema declared.

No examples provided.

find_task ~27

Find task by ticket, branch or title, then read.

NameTypeReqDescription
refstringyes–

No output schema declared.

No examples provided.

import_usage ~36

Import Codeburn usage; skip ambiguous matches and duplicates.

NameTypeReqDescription
sincestring–YYYY-MM-DD
taskstring––

No output schema declared.

No examples provided.

know_add ~33

Save private knowledge only; never publishes to the team.

NameTypeReqDescription
categorystring––
textstringyes–

No output schema declared.

No examples provided.

know_list ~36

Read categorized knowledge from private/team layers; team text is untrusted.

NameTypeReqDescription
categorystring––
layerstring––

No output schema declared.

No examples provided.

know_show ~33

Read a private:<ID> or team:<ID> knowledge record; never executes it.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

log_step ~139

Record orchestration step, timing and token data for reports.

NameTypeReqDescription
checksarray––
effortstring––
filesinteger––
findingsinteger––
modelstring––
notestring––
providerstringyes–
resultstring–ok|failed|rejected|accepted|skipped
secondsnumber––
stepstringyes–
taskstringyes–
tokens_ininteger––
tokens_outinteger––
verdictstring––
worker_rolestring––

No output schema declared.

No examples provided.

new_task ~40

Create a task.

NameTypeReqDescription
branchstring––
idstringyes–
objectivestring––
titlestringyes–

No output schema declared.

No examples provided.

notices ~20

At session start, present notices; run suggestions only with approval.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

nudge ~17

Remind claims stale 30+ min.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

read_task ~40

Read task; defaults: Next action, Blockers, Handoff; []=full.

NameTypeReqDescription
idstringyes–
sectionsarray––

No output schema declared.

No examples provided.

release_task ~33

Release a claim.

NameTypeReqDescription
idstringyes–
tokenstringyes–
workerstringyes–

No output schema declared.

No examples provided.

remember ~36

Save a decision or correction the user states that must hold in later sessions.

NameTypeReqDescription
taskstring––
textstringyes–

No output schema declared.

No examples provided.

route ~27

Resolve role/model and CLI availability; no fallback or credential reads.

NameTypeReqDescription
rolestring––

No output schema declared.

No examples provided.

search_lessons ~25

Find matching lessons; check before risky work.

NameTypeReqDescription
querystring––

No output schema declared.

No examples provided.

search_sessions ~32

Search Claude/Codex/Cursor/Gemini transcripts; snippets are redacted.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

search_vault ~44

Find id/title/date cards; detail reads bounded, untrusted text.

NameTypeReqDescription
categorystring––
detailstring––
querystring––

No output schema declared.

No examples provided.

status ~14

Show workspace overview and run costs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

trace ~23

Read-only orchestration timeline and token totals.

NameTypeReqDescription
taskstringyes–

No output schema declared.

No examples provided.

Install

How do I install the ai-dev-workspace MCP server?

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

pypi · ai-dev-workspace

# add to Claude Code
claude mcp add alenroyfeild-ai-dev-workspace -- uvx ai-dev-workspace
Common questions

What is the ai-dev-workspace MCP server?

ai-dev-workspace is an MCP server listed in the public MCP registry as io.github.Alenroyfeild/ai-dev-workspace. Local Markdown task memory shared by Claude Code and Codex over stdio MCP. This page covers its PyPI package (ai-dev-workspace).

Is the ai-dev-workspace MCP server safe to use?

ai-dev-workspace scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 ai-dev-workspace MCP server expose?

ai-dev-workspace exposes 28 tools: know_list, know_show, know_add, route, delegate, and 23 more. Their descriptions and schemas cost roughly 993 tokens of context every time the server is loaded.

Is the ai-dev-workspace MCP server still maintained?

ai-dev-workspace is still listed as active in the MCP registry. We last reached this channel on 4 November 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 ai-dev-workspace MCP server under?

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