Sirveil Exposure

io.github.sirveil-aiPublished by GitHub account sirveil-aiv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Lets an assistant check whether a person appears on a data-broker domain and get a three-state verdict with supporting evidence.

What you can do
Sirveil Exposure answers exposure questions about people and data-broker domains. Given a person and a domain, it returns a three-state verdict rather than a simple yes or no, together with the evidence behind that verdict. The manifest lists no individual tools, so the exact call surface is not documented here.
When to use it
Useful when you need to check whether someone is indexed on a particular data-broker site and want a reasoned verdict with evidence rather than a bare match.
Requirements
A remote streamable HTTP endpoint at ai.sirveil.ai. Requires a bearer API key sent in the Authorization header; keys are issued through AWS Marketplace. No local runtime or environment variables are declared.
Before you install
The API key is a live secret sent in the Authorization header and should be kept private. Each call is metered at 0.10 USD, so usage incurs real spending. Queries concern personal exposure data, which is sensitive and may be sent to a third party.

Installation

In SourceWeft

  1. Open Sirveil Exposure in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.sirveil-ai%2Fsirveil-exposure/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "sirveil-exposure": {
      "type": "http",
      "url": "https://ai.sirveil.ai/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

1

verify_indexed

Check if an identity is indexed on a data-broker domain

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`.

ParametersdobcityemailphonestatedomainrequiredstreetlastNamerequiredfirstNamerequiredmiddleName

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

83% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.