Agent-Native Google Calendar - manage events, sync, and public booking

What we measured

Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 348 ms, 95th percentile 657 ms.

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

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

MCP readiness

D · 41/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, 48.0/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 (960 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)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	0/10	No tools listed by tools/list.
Verified identity	7/10	Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (960 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 5% of peers; This listing 41 · peer median 81
Latency: Faster than 48% of peers; This listing 363 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 (960 ms).
Protocol revision −10 — Support the current protocol revision.
Now: No protocol revision reported by initialize.

How many agent tools actually work · All statistics

Adoption signals

Public signals from outside this directory, shown for context. They do not change search order or grades.

GitHub: ★ 7,674 · 706 forks; last push 2026-11-11
Site rank (Tranco): #600,667 of the top 1M; agent-native.com · list of 2026-11-11

Listed in

Directories this entry was found in.

mcp-registry since 2026-09-10 wellknown since 2026-09-26 ↗ agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

https://calendar.agent-native.com/mcp

JSON-RPC initialize probe

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

Homepage

https://www.agent-native.com/apps/calendar

Source code

https://github.com/BuilderIO/agent-native