Sirveil Exposure is listed as active in the registry but did not answer our last check. It exposes 1 tools.
Is this person indexed on that data-broker domain? A three-state verdict, with the evidence.
Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.
claude mcp add sirveil-exposure --transport http https://ai.sirveil.ai/api/v1/mcp
https://ai.sirveil.ai/api/v1/mcp
[mcp_servers.sirveil-exposure]
url = "https://ai.sirveil.ai/api/v1/mcp"
{
"mcpServers": {
"sirveil-exposure": {
"url": "https://ai.sirveil.ai/api/v1/mcp"
}
}
}
{
"servers": {
"sirveil-exposure": {
"type": "http",
"url": "https://ai.sirveil.ai/api/v1/mcp"
}
}
}
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
verify_indexed
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://ai.sirveil.ai/api/v1/mcp | streamable-http | answering | 79 ms | 10 min ago |
Independent rule and fee data on 71 prop trading firms, every figure with its evidence state.
Perforce P4 MCP Server is a MCP server that integrates with the Perforce P4 version control system.
Find MCP servers in the MCP Rating index and connect on demand, with env vars scoped per server.
Where informed investors disagree, the evidence each side stands on, and the date that settles it.
Maps every service that sends email as a domain, with the public record behind each one.
Bounded genomic data from archives and indexed files, with versioned reference evidence.
Read-only pre-sign evidence for onchain agents: route quality, MEV exposure, clear/caution verdict.
What is known to be broken in an MCP server or API operation, with the check that found it.
Answers built from our own checks of this server.