On This Day MCP — wraps byabbe.se/on-this-day (free, no auth)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 34 tools
Core domains (memory, subscriptions, date lookups, discovery) are clearly separable, and descriptions give explicit routing guidance. However, several tools overlap heavily: ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research all answer questions, discover_tools / suggest_questions / pipeworx_trending all aid discovery, and the five polymarket scanners plus bet_research share territory. The routing notes help, but an agent can still plausibly misselect among these near-duplicates.
Everything is snake_case, which is a plus, but the verb/noun convention is mixed: verb_noun (compare_entities, discover_tools, validate_claim), noun_noun (entity_profile, polymarket_edges), noun_verb (ai_visibility_check), and bare verbs (forget, recall). The casing is predictable but the structural pattern is not.
34 tools is heavy and sits above the comfortable range. The platform is genuinely multi-domain so breadth is partly justified, but duplicate/experimental entries (ask_pipeworx_beta) and multiple overlapping polymarket scanners inflate the count beyond what the surface strictly needs.
Coverage is broad: memory has full CRUD (remember/recall/forget), subscriptions have create/list/read/cancel, entity workflows (resolve/profile/compare/recent_changes/validate) are well covered, and the onthisday core has births/deaths/events. Minor gaps remain, such as no subscription update/edit and thin holiday/on-this-day breadth for the server's namesake theme, but agents can work around these.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "when-will-bitcoin-hit-150k"
- },
- {
- "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
- }
-]New value: +[
+ {
+ "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ },
+ {
+ "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."bet_research2 fields changedInput schema / examplesPrevious value: -[
- {
- "market": "will-bitcoin-reach-100k-in-july-2026"
- },
- {
- "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026"
- }
-]New value: +[
+ {
+ "market": "when-will-bitcoin-hit-150k"
+ },
+ {
+ "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k"
+ }
+]Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."polymarket_kalshi_spread2 fields changedInput schema / examplesPrevious value: -[
- {
- "topic": "fed"
- },
- {
- "topic": "btc"
- }
-]New value: +[
+ {
+ "topic": "fed"
+ },
+ {
+ "topic": "btc"
+ },
+ {
+ "topic": "bitcoin"
+ },
+ {
+ "topic": "fed rate decision"
+ }
+]Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."D&D 5e MCP — wraps the D&D 5th Edition API (free, no auth)
NumbersAPI MCP — wraps numbersapi.com (free, no auth)
Quotable MCP — wraps the Quotable dataset (free, no auth)
yesterdays-number MCP — wraps StupidAPIs (keyless — no credential needed)
Add one secure layer between your agents and this server.