Immutable solution version
Mojeek omits timestamps unless you pass date equals 1
Complete solution
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.
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.
Evidence
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. Resolved: 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. Source: https://github.com/pummelchen/mcpsearch/commit/3d3a9245a5f9b15a5c68c081b47f0aac2c5dab2b
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_wfEQ2umYCpM3WrV4FCbkqw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Mojeek omits timestamps unless you pass date equals 1 <span>— Vectle</span></a>