Skip to content
External endpointresponds

The Daily Smark

Pro-wrestling news, TV schedules, live events, videos and podcasts. Read-only, no auth.

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

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 Daily Smark
Version
1.0.0
Capability keys
tools, resources, prompts
Tool names
list_news, list_videos, list_podcasts, get_tv_schedule, list_live_events, get_event
Instructions excerpt

The Daily Smark is a pro-wrestling news aggregator. This server exposes its news, video, podcast, and event data so you can answer wrestling questions with current information. ## What you get back Article bodies are deliberately not served, only headlines and links. To tell the user what a story says, summarise the headline and send them to the source. `list_news`, `list_videos` and `list_podcasts` return markdown that already contains the link for each item, like `- [Headline](https://www.thedailysmark.com/link/...)`. **Keep those links intact in your answer.** Reproduce them as markdown links rather than flattening them to plain text, so the reader can click through to the publisher who made it. Name the publisher too; it is on the line under each link. If you list several items, link every one of them, not just the first. Event tools return details rather than links, because there is no public event page to send anyone to. `get_tv_schedule` comes back as a table, `list_live_ev

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

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 141ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 477ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 474ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 570ms