_ registry / mcp http-sse · checked 20h ago

privacyboard-vendors

https://privacyboard.io

Registry code: 0024a1ff1577912f

api record

Privacyboard's public catalog of 1298 SaaS tools, each checked by opening the vendor's own pages: where the data processing agreement is, the tool's usual GDPR role, where data is hosted (with the source and date), Data Privacy Framework certification and how to declare the tool. Cite the "page" link of each vendor you use. The facts describe the vendor's documents, not whether anyone is compliant; this is not legal advice.

endpoint
https://privacyboard.io/mcp/vendors
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is privacyboard-vendors live?
Yes — it answered the hub's last check (checked 20h ago). It answered 100% of checks over the last 30 days.
Is privacyboard-vendors free to use?
Yes — the hub reached it with no key and no payment.
What tools does privacyboard-vendors have?
3 tools: get_vendor, list_vendor_categories, search_vendors.
Is privacyboard-vendors safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
175ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
2 open 1 never probed 2 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_vendor_categories open 20h ago

    The categories of the catalog (CRM, email, analytics, hosting…) with how many verified tools each has.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {}
    }
    arguments 5 lines
  • search_vendors open 20h ago

    Find SaaS tools in the Privacyboard catalog by name, website or category (for example "stripe", "email", "analytics").

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 50,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "default": "",
          "maxLength": 100,
          "description": "Tool name, website or category word"
        },
        "category": {
          "enum": [
            "analytics",
            "hosting",
            "development",
            "customer-support",
            "security",
            "crm",
            "ai-services",
            "project-management",
            "collaboration",
            "communications",
            "payments",
            "email-marketing",
            "reviews-loyalty",
            "scheduling",
            "e-commerce",
            "forms",
            "hr-payroll",
            "monitoring",
            "sales-engagement",
            "accounting",
            "email",
            "database",
            "automation",
            "social-media",
            "authentication",
            "cms",
            "learning",
            "recruiting",
            "video-conferencing",
            "infrastructure",
            "electronic-signature",
            "design",
            "shipping",
            "advertising",
            "consent-management",
            "media",
            "file-storage",
            "expense-management",
            "search",
            "seo"
          ],
          "type": "string",
          "description": "Limit to one category slug from list_vendor_categories"
        }
      }
    }
    arguments 64 lines
  • get_vendor unknown 20h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "vendor"
      ],
      "properties": {
        "vendor": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Tool name, catalog slug or website, such as \"Stripe\" or \"hubspot.com\""
        }
      }
    }
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0024a1ff1577912f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0024a1ff1577912f/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0024a1ff1577912f/badge.svg)](https://brick.blue/agent/0024a1ff1577912f?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.