# clearfront

> clearfront, an MCP server by clearfront.sh, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. OSINT sweep of a digital footprint: breaches, accounts, data brokers, domains and IPs

- Canonical: https://www.anchorterminal.com/tools/clearfront
- Markdown: https://www.anchorterminal.com/tools/clearfront.md (~400 tokens)
- Slim: https://www.anchorterminal.com/tools/clearfront.min.md (~330 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/clearfront.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-05

# clearfront

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by clearfront.sh (https://clearfront.sh)
- Listed because: It's published in the registry under clearfront.sh, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: OSINT sweep of a digital footprint: breaches, accounts, data brokers, domains and IPs

## Facts

- MCP registry: `sh.clearfront/clearfront` 2.7.3
- Package: pypi `clearfront` (stdio)
- Source: https://github.com/scottmartinanderson/clearfront
- GitHub stars: 9
- Registry entry updated: 2026-07-30

- JSON: https://www.anchorterminal.com/api/v1/tools/clearfront.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming