Is this person indexed on that data-broker domain? A three-state verdict, with the evidence.
Connect Remote server
claude mcp add --transport http sirveil-exposure https://ai.sirveil.ai/api/v1/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"sirveil-exposure": {
"url": "https://ai.sirveil.ai/api/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"sirveil-exposure": {
"type": "http",
"url": "https://ai.sirveil.ai/api/v1/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://ai.sirveil.ai/api/v1/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 1 found in our last check
verify_indexedAsks 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…
Headers
| Name | Description |
|---|---|
AuthorizationRequired, secret | Bearer <your Sirveil API key, sk_live_...>. Keys are issued through AWS Marketplace. Read-only, but each call is metered at 0.10 USD. |
Details
| Endpoint | https://ai.sirveil.ai/api/v1/mcp (Streamable HTTP) |
| First published | 26 Aug 2026 |
| Last updated | 26 Aug 2026 |
| Registry name | io.github.sirveil-ai/sirveil-exposure |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
