
Wraps the byabbe.se/on-this-day API to surface historical events, births, deaths, and other notable occurrences tied to specific dates. No authentication required. The source doesn't list specific tools, but this is part of the Pipeworx gateway ecosystem, which means you can query it through their ask_pipeworx natural language interface instead of calling tools directly. Reach for this when you're building conversational agents that need historical context, trivia features, or date-aware content generation. Works through streamable HTTP transport, so you can drop the gateway URL into any MCP client config and start querying immediately.
On This Day MCP — wraps byabbe.se/on-this-day (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
get_events | Search historical events on a specific date. Provide month (1-12) and day (1-31). Returns event descriptions, years, and details. |
get_births | Find notable people born on a specific date. Provide month (1-12) and day (1-31). Returns names, birth years, and biographical details. |
get_deaths | Find notable people who died on a specific date. Provide month (1-12) and day (1-31). Returns names, death years, and biographical detail. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"onthisday": {
"url": "https://gateway.pipeworx.io/onthisday/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/onthisday/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Onthisday data" })
The gateway picks the right tool and fills the arguments automatically.
MIT