mcp-pulse

io.github.ondraulehla/mcp-pulse · v0.1.1 · agents-and-memory

mcp-pulse is healthy: it completed an MCP handshake in 2393 ms and exposes 4 tools.

Health and token cost of every remote MCP registry server, probed daily. Look up, search, or probe.

Endpoint: https://mcp-pulse.ulehla.dev/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency2393 ms
Last checked (UTC)2026-10-15T06:15:50.283Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T06:15:50.283ZHealthy2393

Tools (4)

lookup_serverLatest probe of one server from the official MCP registry: status, protocol, tool count, exact token cost of its tool definitions in Claude, latency. Accepts the registry name (io.github.owner/name) or the server URL.
search_serversFind servers by words in name, title, description or host, with optional filters, sorted by exact Claude token cost by default. Returns up to 20 servers per page; page numbers go to 20, after that pass the `next` cursor from the previous answer.
check_serverConnects to an MCP server URL now (initialize and tools/list, no credentials, 10 s timeout) and reports status, protocol, tools and the token cost of the tool definitions: exact in Claude when the counter is available, else an estimate from the schema size. For registry servers prefer lookup_server.
registry_summaryAggregates of the latest daily run: how many servers answer, token cost percentiles, protocol versions, heaviest servers.