Plan, schedule and generate SEO articles on a content calendar. Ask your agent to show what is scheduled this month, plan a topic cluster, move or retitle a planned article, or write one now. Article generation runs unattended on its publish date, so the calendar keeps working after you close the terminal.

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 29 (97%). Median response 891 ms, 95th percentile 2,261 ms.

Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 9% and higher on readiness than 24%.

From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure

MCP readiness

D · 45/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here C, 40.4/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	0/10	Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint	15/25	Endpoint requires authentication or payment (1455 ms).
Protocol revision	0/10	No protocol revision reported by initialize.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	14.5/15	29/30 probes succeeded over 30 days (97%).
Tool declaration	0/10	No tools listed by tools/list.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1455 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-12.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.

Readiness: Higher than 24% of peers; This listing 45 · peer median 81
Latency: Faster than 9% of peers; This listing 1,014 ms · peer median 349 ms

Where it loses the most points, and how to win them back

Valid MCP handshake −10 — Complete the MCP handshake without errors.
Now: Handshake needs credentials (HTTP 401); not readable anonymously.
Live MCP endpoint −10 — Answer initialize and tools/list at the declared endpoint.
Now: Endpoint requires authentication or payment (1455 ms).
Protocol revision −10 — Support the current protocol revision.
Now: No protocol revision reported by initialize.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-02 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/timothe/growth-calendar/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/timothe/growth-calendar/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://timothe.ai/growth-calendar

Listed at (smithery)

https://timothe.ai/growth-calendar