Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Slack MCP slack_search_public returns corrupted timestamps [1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54074•Fetched 2026-04-28 06:39:55
View on GitHub
Comments
1
Participants
1
Timeline
4
Reactions
0
Author
mtoccemtocce
Participants
mtoccemtocce
Timeline (top)
labeled ×3commented ×1

mcp__claude_ai_Slack__slack_search_public returns messages whose displayed timestamps are mangled. Search content and filters work correctly, but the timestamp field is unreadable, breaking any workflow that uses search to build a timeline or assess recency.

slack_read_channel and slack_read_thread return correct timestamps for the same messages — the bug is isolated to slack_search_public's output formatter.

Root Cause

mcp__claude_ai_Slack__slack_search_public returns messages whose displayed timestamps are mangled. Search content and filters work correctly, but the timestamp field is unreadable, breaking any workflow that uses search to build a timeline or assess recency.

slack_read_channel and slack_read_thread return correct timestamps for the same messages — the bug is isolated to slack_search_public's output formatter.

Fix Action

Workaround

Use slack_read_channel (or slack_read_thread) for any timestamp-sensitive workflow. Treat slack_search_public result timestamps as opaque; re-fetch via channel-read for the real time.

🤖 Generated with Claude Code

RAW_BUFFERClick to expand / collapse

Summary

mcp__claude_ai_Slack__slack_search_public returns messages whose displayed timestamps are mangled. Search content and filters work correctly, but the timestamp field is unreadable, breaking any workflow that uses search to build a timeline or assess recency.

slack_read_channel and slack_read_thread return correct timestamps for the same messages — the bug is isolated to slack_search_public's output formatter.

Environment

  • Claude Code CLI on macOS, Opus 4.7 (1M context)
  • MCP namespace: mcp__claude_ai_Slack__* (claude.ai-connected Slack)
  • Verified: 2026-04-27

Reproduction

The same message returned by both slack_read_channel and slack_search_public has different timestamp formatting:

Via slack_read_channel (channel C0AQM6JGY1H, #ndas-plan-group):

Changyu Gao: "Hi, team. When I tried to 'connect to jira', it doesn't work for me." [2026-04-23 01:52:50 PDT]

Via slack_search_public with query in:#ndas-plan-group:

Changyu Gao: "Hi, team. When I tried to 'connect to jira', it doesn't work for me." 56310778-08-11

The 56310778-08-11 value is rendered in YYYY-MM-DD form, but year 56,310,778 is nonsense. The value is not:

  • A Unix epoch (would be ~1.78 billion in 2026)
  • A real Slack ts (would be a float like 1745384000.123456)
  • Any consistent transform of either

The pattern across results suggests a numeric Slack message ID is being split on punctuation and emitted as date components by the search-results formatter. Other search results showed similarly mangled values: 56322999-08-18, 56267808-06-27, 56303312-01-20.

Impact

  • Cannot use slack_search_public to build a timeline or assess recency.
  • Cannot tell when a search-found message was sent without re-fetching via slack_read_channel.
  • after: / before: date filters in the query string DO appear to filter correctly — verified by cross-checking against slack_read_channel. Only the displayed timestamps in the response are wrong.

What works

  • slack_read_channel — proper [YYYY-MM-DD HH:MM:SS TZ] timestamps
  • slack_read_thread — proper timestamps
  • slack_read_user_profile — works
  • slack_search_channels — works
  • slack_search_public query semantics (in:, after:, from:) — work; only timestamps corrupted

Workaround

Use slack_read_channel (or slack_read_thread) for any timestamp-sensitive workflow. Treat slack_search_public result timestamps as opaque; re-fetch via channel-read for the real time.

🤖 Generated with Claude Code

extent analysis

TL;DR

The slack_search_public function is returning mangled timestamps, which can be worked around by using slack_read_channel or slack_read_thread to fetch the correct timestamps.

Guidance

  • Verify that the issue is isolated to the slack_search_public output formatter by comparing the timestamps returned by slack_read_channel and slack_read_thread for the same messages.
  • Use slack_read_channel or slack_read_thread to fetch the correct timestamps for any timestamp-sensitive workflow.
  • Treat slack_search_public result timestamps as opaque and do not rely on them for building timelines or assessing recency.
  • Note that the after: and before: date filters in the query string appear to filter correctly, despite the displayed timestamps being wrong.

Example

No code snippet is provided as the issue is related to the output formatting of the slack_search_public function.

Notes

The root cause of the issue is likely a bug in the output formatter of the slack_search_public function, which is causing the numeric Slack message ID to be split on punctuation and emitted as date components.

Recommendation

Apply workaround: use slack_read_channel or slack_read_thread to fetch the correct timestamps, as the slack_search_public function is returning mangled timestamps. This is because the workaround allows for accurate timestamp retrieval, which is essential for building timelines and assessing recency.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#ISR setup#authentication setup#request error#file not found#serialization error

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Slack MCP slack_search_public returns corrupted timestamps [1 comments, 1 participants]