MCP server health, State of MCP census

Meet.bot MCP

bot.meet/mcp

AI-native scheduling and booking: check availability, book meetings, share links.

healthy checked 2026-07-02 · 6/7 checks passed · keyless

Checks

The exact rows akashi check bot.meet/mcp prints, from the 2026-07-02 census.

Check	Status	Detail
registry status	pass	active
server.json valid	pass	validates against its declared JSON Schema
repo reachable	skip	no repository declared
remote reachable	pass	HTTP 200 via initialize
MCP conformance	pass	initialize handshake ok
tools/list	pass	8 tools: get_scheduling_pages, get_page_info, get_available_slots, book_meeting, health_check, list_webhooks, set_webhook, delete_webhook
at least one live entrypoint	pass	1 alive

Evidence

Repository

No repository declared.

Packages

No packages declared.

Remote endpoints

https://mcp.meet.bot
streamable-http · reachable· HTTP 200· initialize_ok

8 tools: get_scheduling_pages, get_page_info, get_available_slots, book_meeting, health_check, list_webhooks, set_webhook, delete_webhook

server.json

validagainst its declared schema

One of 14559 servers in the 2026-07-02 State of MCP census: 11582 healthy (79.6%), 2212 degraded (15.2%), 596 dead (4.1%), 169 unknown (1.2%).

Verify it yourself

This page is a static read of one dated probe. Run the same check locally, any time, with no key:

$ akashi check bot.meet/mcp

Install Akashi - single Go binary, zero keys, MIT licensed.

Is this your server?

Claiming a server (an auto-refreshing badge and a verified publisher profile) is coming soon. Until then, embed the verified-on-date badge yourself with akashi check bot.meet/mcp --badge.

Open data, CC BY 4.0. How this census works - denominator, tiers, and what each check does.