_ registry / mcp streamable-http · checked 54m ago

vendorwatch

https://vendor.watch

Registry code: e7e81b206333573a

api record

Check a vendor before you sign: DPA coverage, subprocessors, certifications, data locations, AI use.

from a public catalogue that lists it, not from the operator

endpoint
https://vendor.watch/api/v1/mcp
protocol
streamable-http ·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 vendorwatch live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is vendorwatch free to use?
No — it asks for a key or a login before it will serve.
What tools does vendorwatch have?
4 tools: check_portfolio, get_vendor_profile, find_vendor, list_vendor_changes_since.
Is vendorwatch 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
233ms

last good check

priced tools
0

of 4 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 4 tools
3 auth-required 1 never probed 3 of 4 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.

  • get_vendor_profile auth-required 54m ago

    Get one vendor's documentation profile: DPA coverage by law, number of subprocessors, certifications, data locations, transfer safeguards and AI use. Give the slug from find_vendor, or the vendor's name or domain. Spends one lookup.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "The vendor's name, written in full (for example the name on its website)."
        },
        "slug": {
          "type": "string",
          "maxLength": 200,
          "description": "The vendor's VendorWatch identifier, as returned by find_vendor."
        },
        "domain": {
          "type": "string",
          "maxLength": 200,
          "description": "The vendor's website domain, or any host under it (for example app.example.com)."
        }
      }
    }
    arguments 21 lines
  • find_vendor auth-required 54m ago

    Find a vendor in the VendorWatch catalogue by its exact name or website domain. Returns up to 5 candidates (slug, name, category). Free: no lookup is spent.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 200,
          "description": "The vendor's name, written in full (for example the name on its website)."
        },
        "domain": {
          "type": "string",
          "maxLength": 200,
          "description": "The vendor's website domain, or any host under it (for example app.example.com)."
        }
      }
    }
    arguments 16 lines
  • list_vendor_changes_since auth-required never probed

    List the vendors in your VendorWatch portfolio whose record changed on or after a date (profile updated, DPA analysed, DPA document changed). Free: no lookup is spent. 50 vendors a page; read the new profile with get_vendor_profile.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "since"
      ],
      "properties": {
        "since": {
          "type": "string",
          "maxLength": 10,
          "description": "A date, YYYY-MM-DD. Changes on or after this date are listed."
        },
        "cursor": {
          "type": "string",
          "maxLength": 200,
          "description": "The `next` value from the previous page, to read the following page."
        }
      }
    }
    arguments 19 lines
  • check_portfolio unknown 54m ago

    Check a list of up to 25 vendors (names, domains or both) and get one profile each. Spends one lookup per vendor answered; a name that matches nothing costs nothing.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "vendors"
      ],
      "properties": {
        "vendors": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "name": {
                "type": "string",
                "maxLength": 200,
                "description": "The vendor's name, written in full (for example the name on its website)."
              },
              "domain": {
                "type": "string",
                "maxLength": 200,
                "description": "The vendor's website domain, or any host under it (for example app.example.com)."
              }
            }
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "Up to 25 vendors, each with a name, a domain or both."
        }
      }
    }
    arguments 30 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 e7e81b206333573a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e7e81b206333573a/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/e7e81b206333573a/badge.svg)](https://brick.blue/agent/e7e81b206333573a?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
80%

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.