Developers

Remote MCP access for AI clients and production workflows

RegEvidenceHub keeps AI-safe connector surfaces separate from commercial MCP endpoints. This makes the integration boundary explicit: read-only, payment-free capabilities can be connected independently from usage-based regulatory decision tools.

AI-safe connector endpoints

Use these vendor-neutral Streamable HTTP MCP endpoints for compatible AI clients. Available tools differ by product.

Using Claude? Follow the Claude custom connector installation guide →

Using Grok? Follow the consolidated Grok custom connector installation guide →

Taxihttps://taxi.regevidencehub.com/ai/mcp

CQChttps://cqc.regevidencehub.com/ai/mcp

Premiseshttps://premises.regevidencehub.com/ai/mcp

Sponsor compliancehttps://works.regevidencehub.com/ai/mcp

Commercial MCP endpoints

Commercial endpoints expose the full product-specific commercial tool boundary and usage-based access where applicable.

Product	Commercial MCP	Transport
Taxi	`https://taxi.regevidencehub.com/mcp`	Streamable HTTP
CQC	`https://cqc.regevidencehub.com/mcp`	Streamable HTTP
Premises	`https://premises.regevidencehub.com/mcp`	Streamable HTTP
England Works Watch	`https://works.regevidencehub.com/mcp`	Streamable HTTP

Decision style

Structured, deterministic, evidence-linked, and fail closed when required source evidence or critical facts are not sufficient.

Payment boundary

Commercial usage is product-specific. Current products use usage-based pricing where published. AI-safe connectors do not expose payment or checkout flows.