Personal Data Map Dsar Audit

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.2Updated Oct 24, 2026

Reads a migration, Prisma schema, Django model or TypeORM entity and marks every column a subject ac

The publisher's own server: audit.domains - Domain Valuation

VerifiedSTDIODesktop onlyDatabasesSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that reads a migration, Prisma schema, Django model or TypeORM entity and marks every column a data subject can access.

What you can do
  • Reads schema and migration files such as Prisma schemas, Django models, TypeORM entities or SQL migrations.
  • Marks the columns that a data subject can access, supporting a personal-data map and DSAR audit.
  • No individual tools are listed in the manifest, so the exact operations are not documented.
When to use it
Useful when you want an assistant to help map personal data in an existing codebase's schema and prepare for data-subject access requests or privacy audits.
Requirements
Runs as a local process on the user's machine via npx from the npm package; desktop only, not web-executable. No authentication, environment variables or headers are declared.
Before you install
The README does not describe this server's usage and instead contains unrelated theme-project text, so the documented behaviour is thin. It reads schema and migration files, which may reveal data model details; review before pointing it at private repositories.

Installation

In SourceWeft

  1. Open Personal Data Map Dsar Audit in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.2LatestSep 18, 2026
  2. v0.1.1Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Audit integrations