Skip to content

Sirveil Exposure

by sirveil-ai · remote · no sign-in to list tools · v1.0.0 · published by GitHub user sirveil-ai

Is this person indexed on that data-broker domain? A three-state verdict, with the evidence.

Changes · 1
CompareRegistry entry

1 tool: 1 change things.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http sirveil-exposure https://ai.sirveil.ai/api/v1/mcp --header 'Authorization: <your-authorization>'

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

1 tool

Changes things 1Claude Code: ask
  • verify_indexedAsks whether a named person is indexed on one data-broker domain, and returns the evidence.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Asks whether a named person is indexed on one data-broker domain, and returns the evidence. Returns one of exactly three states: `indexed` (a matching listing was found), `not_indexed` (the domain was searched and nothing matched), or `indeterminate` (searched, but the evidence was too weak to call). `indeterminate` is a real answer — do NOT report it to the user as "not found", because that claims an absence that was not observed. This reports INDEX PRESENCE only. The broker page is not fetched, so a listing that has been removed but is still in the search index will read as `indexed`.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http sirveil-exposure https://ai.sirveil.ai/api/v1/mcp --header 'Authorization: <your-authorization>'

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__sirveil-exposure__verify_indexed"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as sirveil-exposure. Review it before you use it.