
Mcp Geraguard
io.github.geraservicesukPublished by GitHub account geraservicesukv0.1.1Updated Oct 24, 2026
Privacy protection: scans, tracker detection, data broker opt-outs.
Overview
A local MCP server that connects an assistant to the GeraGuard PrivacyGuard API for privacy scans, tracker detection and data broker opt-outs.
- What you can do
- Run privacy scans through the GeraGuard PrivacyGuard service and review the results with the assistant's help. Detect trackers and surface what they collect. Manage data broker opt-outs so personal data is removed from broker listings. The manifest lists no individual tools, so exact operations are not documented here.
- When to use it
- Worth adding when you want an assistant to check your exposure to trackers and data brokers and to help carry out opt-out requests, rather than doing that work manually in the GeraGuard service.
- Requirements
- Runs as a local process over stdio, installed from the npm package @gera-services/mcp-geraguard, so Node.js is needed. It talks to the PrivacyGuard API; the base URL can be overridden with the GERAGUARD_API_URL environment variable and defaults to the GeraGuard API host. Network access is required. No authentication is declared in the manifest.
Installation
In SourceWeft
- Open Mcp Geraguard in the dashboard and add it to a workspace.
- 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
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.