Privacyboard for builders MCP server
io.privacyboard/vendorsprivacyboard.iostreamable-httpv1.1.0Scanned
Cookie banner and privacy policy from a project's packages; GDPR facts on 1,290+ SaaS tools.
4 tools: 1 change things and 3 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Privacyboard for builders MCP server can do
The Privacyboard for builders MCP server is published by privacyboard.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: create_privacy_setup), but cannot delete data. 3 tools only read.
2 tools read private data (search_vendors and list_vendor_categories); 2 tools bring in text other people can write (search_vendors and list_vendor_categories).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 22, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
create_privacy_setupFor a site you are building: prepares its Privacyboard cookie banner, privacy policy and cookie policy, without an account.No findings
Why it is in this group
- The name "create_privacy_setup" says "create": a word for a change.
Description, as the server wrote it For a site you are building: prepares its Privacyboard cookie banner, privacy policy and cookie policy, without an account. Give the site’s public address and the names of its packages (from package.json, requirements.txt…; names only, never secrets or environment values). Returns the banner script to put first in <head>, the footer links, the vendors found and a claim link. Nothing goes live until the site owner opens the claim link, confirms the vendors, validates the documents and publishes: give them the link (forTheUser). Use it when the user asks for a privacy policy, a cookie banner or GDPR compliance, or before launch.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_vendorOne tool’s GDPR facts: link to its data processing agreement, usual role (processor or controller), hosting region with source, Data Privacy Framework certification, usual legal ba…No findings
Why it is in this group
- The name "get_vendor" says "get": a word for reading.
Description, as the server wrote it One tool’s GDPR facts: link to its data processing agreement, usual role (processor or controller), hosting region with source, Data Privacy Framework certification, usual legal bases, what to check and how to declare it.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_vendor_categoriesThe categories of the catalog (CRM, email, analytics, hosting…) with how many verified tools each has.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_vendor_categories" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "email": it reads mail.
- untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
Description, as the server wrote it The categories of the catalog (CRM, email, analytics, hosting…) with how many verified tools each has.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_vendorsFind SaaS tools in the Privacyboard catalog by name, website or category (for example "stripe", "email", "analytics").Reads private dataReads text others writeNo findings
Why it is in this group
- The name "search_vendors" says "search": a word for reading.
What it can reach
- private-dataThe description's first sentence says "find" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "find" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Find SaaS tools in the Privacyboard catalog by name, website or category (for example "stripe", "email", "analytics").
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://privacyboard.io/.well-known/oauth-protected-resource
- Authorization servers
- https://privacyboard.io
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added.+1 addedView diff
- Added:create_privacy_setupChanges things
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http vendors https://privacyboard.io/mcp/vendorsclaude mcp add --transport http vendors https://privacyboard.io/mcp/vendorsRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__vendors__search_vendors",
"mcp__vendors__get_vendor",
"mcp__vendors__list_vendor_categories"
],
"ask": [
"mcp__vendors__create_privacy_setup"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as vendors. Review it before you use it.
Capability tags behind 2 rules
- mcp__vendors__search_vendors private-data, untrusted-input
- mcp__vendors__list_vendor_categories private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.privacyboard/vendors/verify?hash=434e348402f75f144964b8d56fe29fef18f1da4346ebac873f89d75b1c5fecae" | jq -e '.changed == false'Pinned hash 434e348402f7, from Nov 22, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.privacyboard/vendors/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.privacyboard/vendors)Source: MCP Registry. Synced Nov 22, 2026, 01:18 UTC.
Privacyboard for builders MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Privacyboard for builders MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Privacyboard for builders MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Privacyboard for builders MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Privacyboard for builders MCP server have?
- 4 tools: 1 write, 3 read. create_privacy_setup, search_vendors, get_vendor and list_vendor_categories.
Does the Privacyboard for builders MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Privacyboard for builders MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Privacyboard for builders MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 22, 2026. Every change is on this page and in its Atom feed.