# mcp-pulse (remote · mcp-pulse.ulehla.dev)

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

- Trust score: 0/100 (low)
- Change this week: −66
- Registry status: deleted
- Liveness: dead
- Owner verified: no
- Last scored: 2026-10-16

> **Deleted**: this server was marked deleted in the MCP registry on 2026-10-15. Its details are retained for reference. The registry records this reason: "Renamed to io.github.ondraulehla/mcpcost."

## Components

- remote · `mcp-pulse.ulehla.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/ondraulehla-mcp-pulse/mcp-pulse.md), [page](https://verifymcp.io/servers/ondraulehla-mcp-pulse/mcp-pulse)

## Channel facts

- Endpoint: `https://mcp-pulse.ulehla.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-16.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-16 (score 0, −23)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-15 (score 23, −46)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.37 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified
- [functional] Schema quality: excellent → good

### 2026-10-14 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 68, 0)

- [functional] Server version: 0.1.2 → 0.1.3

### 2026-10-11 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 23. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-08 (score 66, +1)

- [functional regression] Schema quality: 91 → 102

### 2026-10-05 (score 65, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_server” rewrote its description, which is the text the model reads
- [security] Tool “lookup_server” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 80 → 91
- [functional] Server version: 0.1.1 → 0.1.2

## MCP tools (4)

### `lookup_server` (~71 tokens)

Look up a registry 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.

Input parameters:

- `nameOrUrl` (string, required): Registry name or https URL of the server

### `search_servers` (~127 tokens)

Search the registry board

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.

Input parameters:

- `cursor` (string): The `next` value of a previous answer, to continue from there
- `page` (integer)
- `query` (string): Words to match, three or more characters each
- `sort` (string)
- `status` (string): ok = answers and lists tools

### `check_server` (~83 tokens)

Probe a server live

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 prefer lookup_server.

Input parameters:

- `url` (string, required): https URL of the MCP endpoint

### `registry_summary` (~33 tokens)

Registry summary

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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ondraulehla-mcp-pulse/mcp-pulse#diagnostics

## Score history

- 2026-10-16: 0
- 2026-10-15: 23
- 2026-10-14: 69
- 2026-10-13: 68
- 2026-10-12: 68
- 2026-10-11: 68
- 2026-10-10: 67
- 2026-10-08: 66
- 2026-10-05: 65
- 2026-10-04: 64
- 2026-10-03: 64

## Common questions

### What is the mcp-pulse server?

mcp-pulse is listed in the public MCP registry as io.github.ondraulehla/mcp-pulse. Health and token cost of every remote MCP registry server, probed daily. Look up, search, or probe. This page covers its hosted endpoint (https://mcp-pulse.ulehla.dev/mcp).

### Is the mcp-pulse server safe to use?

mcp-pulse scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the mcp-pulse server expose?

mcp-pulse exposes 4 tools: lookup_server, search_servers, check_server, registry_summary. Their descriptions and schemas cost roughly 314 tokens of context every time the server is loaded.

### Does the mcp-pulse server require authentication?

Its publisher declares no required credentials for mcp-pulse. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the mcp-pulse server still maintained?

mcp-pulse has been deleted from the MCP registry. We last reached this channel on 15 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp-pulse.ulehla.dev/mcp
- Repository: https://github.com/ondraulehla/mcp-pulse
- Website: https://mcp-pulse.ulehla.dev/
- Changelog RSS feed: https://verifymcp.io/servers/ondraulehla-mcp-pulse/mcp-pulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/ondraulehla-mcp-pulse/mcp-pulse.json
- HTML version of this page: https://verifymcp.io/servers/ondraulehla-mcp-pulse/mcp-pulse