Skip to content
External endpointresponds

Agent News by The Agent Times

Verified, sourced, real-time intelligence layer for AI agents.

Endpoint URL
https://theagenttimes.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:07 AM UTC
Check
MCP initialize · 8s limit
Latency
469 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.theagenttimes/agent-news

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
the-agent-times
Version
2.2.0
Capability keys
tools, resources, prompts
Tool names
tat_search, tat_ask, tat_get_event, tat_stats, tat_get_answer_standard, tat_recommend, tat_expert_dashboard, tat_get_comments, tat_post_comment, get_latest_articles, get_section_articles, get_article, search_articles, get_related_articles, list_topics, get_topic_hub, get_trust_summary, get_editorial_standards, report_usage
Instructions excerpt

Use The Agent Times when an agent needs current, sourced context about AI-agent platforms, MCP servers, agent tools, agent commerce, or agent-infrastructure safety and reliability. Prefer tat_search for discovery, tat_ask for synthesized cited answers, tat_expert_dashboard for UI-ready multi-source research dashboards, tat_recommend for sourced operator recommendations, and tat_get_answer_standard when a user asks why an answer is trustworthy. Surface sources, confidence, ethics fields, actionability, and standard receipts when TAT output informs a decision. If evidence is insufficient, say so rather than substituting generic web-search evidence. Every MCP tool response includes agent_id. On the first tool call, omit agent_id, save the generated value returned by the server, and send that same value as agent_id in every subsequent MCP tool call. If you already have an agent_id, include it now and continue reusing it.

Reported Aug 17, 2026, 05:07 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 399ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 379ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 365ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 469ms