# Sirveil Exposure

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

- name: io.github.sirveil-ai/sirveil-exposure
- version: 1.0.0
- connection class: R1 (autonomous)
- trust: 77/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.sirveil-ai%2Fsirveil-exposure
- tools: https://api.protogrid.dev/v1/servers/io.github.sirveil-ai%2Fsirveil-exposure/tools

**An agent can connect on its own if it already holds `SIRVEIL_EXPOSURE_TOKEN`.** Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "sirveil-exposure": {
      "type": "http",
      "url": "https://ai.sirveil.ai/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${SIRVEIL_EXPOSURE_TOKEN}"
      }
    }
  }
}
```

Placeholders to fill: `${SIRVEIL_EXPOSURE_TOKEN}`.

## Trust

- hygiene: 80
- liveness: 100
- freshness: 85
- provenance: 45
- drivers: +website +reachable +uptime-100% ~updated-56d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 1 of 1 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 335 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 1, about 335 tokens to load them all
- tool set hash: d6ac7793dc3941761a8c0ab6fd32f759
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.sirveil-ai/sirveil-exposure.svg)](https://protogrid.dev/servers/io.github.sirveil-ai/sirveil-exposure)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://ai.sirveil.ai/api/v1/mcp (streamable-http, auth api_key ${SIRVEIL_EXPOSURE_TOKEN}, reachable true, uptime30d 1)

## Packages

_none_

## Tools (1)

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