# Dealer Scam Sibling Finder

Dealer Scam Sibling Finder is a public, passive OSINT project for checking whether auto-dealer listings, dealer domains, phone numbers, images, or apparent business identities overlap with suspected dealer-impersonation campaign data.

Canonical site:
https://dealer-scam-siblings.web.app/

Agent capability manifest:
https://dealer-scam-siblings.web.app/.well-known/agent-capabilities.json

MCP manifest:
https://dealer-scam-siblings.web.app/.well-known/mcp.json

Agent documentation:
https://dealer-scam-siblings.web.app/agent/

Current public data:
- https://dealer-scam-siblings.web.app/data/latest/identity_graph.json
- https://dealer-scam-siblings.web.app/data/latest/identity_findings.csv
- https://dealer-scam-siblings.web.app/data/latest/suspects.csv
- https://dealer-scam-siblings.web.app/data/latest/domains.csv
- https://dealer-scam-siblings.web.app/data/latest/clusters.json

Use cases for agents:
- Check whether a Craigslist or marketplace vehicle listing overlaps known suspected campaign observations.
- Check whether a dealer domain has appeared as a front domain in the historical identity graph.
- Check whether a phone number appears across unrelated dealer identities.
- Compare current observed domains/phones against Google-found apparent legitimate business details.
- Explain risk signals cautiously using "suspected", "likely", "risk signal", and "requires verification".

Safety policy:
- Do not state that a person or company is criminal based only on this data.
- Treat every result as an investigative lead requiring verification.
- Do not contact suspected scammers, interact with payment systems, bypass access controls, or perform exploitation.
- This project supports passive public-web review only.

Current integration status:
- Static public data endpoints are live.
- A hosted read-only MCP HTTP JSON-RPC implementation exists but is not live until Firebase is upgraded to Blaze.
- A local stdio MCP server is available as `scamfinder-mcp` when this repository is installed.
- Agents should currently use the local MCP server or the public data endpoints and manifests.