What it is
One versioned lookup contract exposed through web, CLI, MCP, and HTTP for Netherlands, United Kingdom, and United States number context.
Open-source product · v0.4.0
Phone-number evidence without identity theatre.
CallerSignal normalizes a displayed number with explicit country context, checks lawful evidence, and returns sources, gaps, confidence, and residual uncertainty instead of guessing who called.
phone intelligence MCP CLI HTTP evidence
3
country wedges
4
interfaces
Read-only
product boundary
Project notes
What it refuses to claim
A displayed number is not proof of the caller, subscriber, provider, safety, or reachability. Unknown remains unknown when evidence cannot support more.
Evidence model
Official numbering evidence comes first. Complaint aggregates remain explicitly unverified, source-scoped signals rather than automatic caller identity or guilt.
Four risk states
Results distinguish official warning, elevated signals, no risk evidence, and insufficient evidence. No risk evidence never means a number is safe.
Operational boundary
The public service is read-only: it does not accept reports, persist watches, query live subscriber data, or publish unsupported organisation declarations.
Agent-first surface
The same machine-readable semantics drive CLI, MCP, HTTP, coverage endpoints, and the website so agents do not receive a weaker or more ambiguous contract.
Coverage transparency
The service publishes which sources are eligible, current, queried, unavailable, or unable to support a risk conclusion. Corpus size and freshness remain inspectable instead of becoming invisible product authority.
Deployment reality
The hosted v0.4.0 wedge covers NL, GB, and US through one versioned contract. Additional countries or community observations require explicit source rights, privacy controls, correction paths, and abuse gates.
The website gives a usable lookup surface; GitHub remains the source for corpus transparency, versioned contracts, implementation details, and current release state.