Archived listing / no verified MCP endpoint/Development

Clair listing

No MCP endpoint is published. This listing is retained for reference.

Clair audited websites built with AI tools such as Lovable, Bolt, v0 and Cursor for the French and Belgian markets. It loaded the site in a real browser and checked cookies and trackers before and after consent, GDPR notices, legal pages, exposed secret keys, security headers and accessibility; it could draft legal documents for 29 business sectors and monitor the site, with the assistant passing project context and applying fixes. The service is suspended: clair.dpdns.org returns HTTP 503 with the message that the owner suspended it, so installation is disabled and the listing is kept for reference.

Archived listingNo verified MCP endpoint is published. This page is retained for reference only.Official docs
Source checked Nov 13, 2026 No MCP endpoint Reviewed 2026-11-16
About

Where it fits

Readers checking what the suspended Clair service covered; it cannot be installed now.

  • Reference the consent and tracker checks Clair performed.
  • Reference the 29-sector legal document drafts.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The provider's page did not load when we checked. Confirm the current setup steps before troubleshooting the client.
  • Authentication fails or no tools appear. The listing does not verify the provider's credential flow; check its documentation before retrying.
  • The endpoint responds but rejects tool calls. Confirm the current address and any account, key, or payment requirement with the provider.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

Clair documentationhttps://clair.dpdns.org/guides