
Littles Weekly MCP server
Which MCP servers are Littles Weekly's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-28
- Registry namecom.littlesweekly/littles-weeklyverified in the MCP registry
The registry name sits under littlesweekly.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-28
- Tools5
- Server calls itselflittles-weekly
- Server version1.0.0
- Protocol version2025-06-18
On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 154 ms.
- Its tools do every use case we checked: find checked kids events for ages 0 to 6 this weekend; compare weekend kids outings across listed cities; check event date, time and place before going.
Once connected
- For "compare weekend kids outings across listed cities", the likely first call is list_cities.
- For "check event date, time and place before going", the likely first call is get_events.
- Parameters are untyped or undescribed in 3 of 7 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score98 of 100answers 100 · does the job 100 · definitions 93 · context 100 · connects 100
- What an agent can do with it3 of 3 use cases
- Answered100% of days7 of 7 daily checks
- Median first answer156 ms
- Space in an agent's context≈ 2,411 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 93 of 100
- Typed results0 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 7
What an agent can do with it
- can do · find checked kids events for ages 0 to 6 this weekend
- can do · compare weekend kids outings across listed cities
- can do · check event date, time and place before going
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_citiesEvery city Littles Weekly covers, with its slug, current week, last-checked date and the pages it has (this-week, guide, visiting, free, free-museum-days, indoor-play, storytime, ice-skating, santa, christmas-lights, thanksgiving…
list_pagesThe pages for one city (or city "site" for site-wide pages like regional weekend getaways), with each page’s URL, last-checked date, section headings and how many FAQs and cards it has.
get_pageEverything on one Littles Weekly page, in reading order: each section (Top 5 picks, Saturday and Sunday plans, every outing, Around town favorites, free days with who gets in free, always-free places, storytimes, indoor play with ages…
get_eventsDated outings for kids 0–6 in one city: this week’s list plus dated listings from the seasonal and free pages (Santa visits, light displays, Thanksgiving, Noon Year’s Eve, free museum days). Each has dates, time, venue, address, price…
searchKeyword search across every card, outing and FAQ on Littles Weekly, in one city or all of them. Good for "Santa breakfast", "toddler time", "free museum day", "splash pad" or a venue name. Results carry the page URL (the event’s own…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"littles-weekly": {
"type": "http",
"url": "https://littlesweekly.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http littlesweekly https://littlesweekly.com/mcpclaude.ai, ChatGPT and other clients: add https://littlesweekly.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.