mcp-pulse

Last 30 days

Uptime

100%

Response time

180 ms typical, 180 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "mcp-pulse": {
      "type": "http",
      "url": "https://mcp-pulse.ulehla.dev/mcp"
    }
  }
}

4 tools

• lookup_server

  Latest 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_servers

  Find 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_server

  Connects 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 p

• registry_summary

  Aggregates of the latest daily run: how many servers answer, token cost percentiles, protocol versions, heaviest servers.

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks