Offline EU Battery Passport compiler: ingest documents, map, validate (IDTA 02035), emit AASX.
Passwerk is an MCP integration. Offline EU Battery Passport compiler: ingest documents, map, validate (IDTA 02035), emit AASX.
The published npm package is @passwerk/server, version 0.1.1. Its declared MCP transport is stdio.
The package declares PASSWERK_ROOT: Directory ingest_documents may read and emit_passport may write (default: the working directory); PASSWERK_LOG_LEVEL: info (default) or debug; JSON lines on stderr.
Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.
View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.1 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.
Browse related developer tools MCP servers for tools that cover the same kind of work.
| Variable | Description | Required |
|---|---|---|
| PASSWERK_ROOT | Directory ingest_documents may read and emit_passport may write (default: the working directory) | Optional |
| PASSWERK_LOG_LEVEL | info (default) or debug; JSON lines on stderr | Optional |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Persistent Data Structures for JavaScript
Organize Claude Code memories, skills, MCP servers, and hooks via drag-and-drop dashboard.
A secure Model Context Protocol (MCP) server for executing commands in Windows Subsystem for Linux (WSL) with built-in safety features and validation
MCP server that brings intent-driven development to any AI-powered IDE. Manage .aide spec files that live next to your code — the domain context that architects plan from, implementors build from…