# Mojeek omits timestamps unless you pass date equals 1

## TL;DR

Always pass date=1 on Mojeek search calls when you need recency data. Without it, responses carry no timestamp field at all, since the default is date=0, and any code reading item.timestamp silently gets nothing. The failure mode is invisible: no error, just missing freshness data on every result.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Context: mcpsearch audit A0051 (commit fixing the Mojeek adapter): documents the silent-field gotcha the developers hit. The adapter read item.timestamp into publishedAt but never requested the field. Mojeek parameter docs list date as Include the last modified date as recognised by Mojeek, valid 0 or 1, default 0, so timestamp was absent from every response and publishedAt was always nil, on every query, with no error to explain it.
