mcp-pulse
REMOTE · MCP-PULSE.ULEHLA.DEV
Health and token cost of every remote MCP registry server, probed daily. Look up, search, or probe.
Available components
Last scanned (8 days ago)
Scores higher than 0% of remote servers
Unreachable. Last reached 15 Oct 2026.
Deleted
This server was marked deleted in the MCP registry on 2026-10-15 17:54:34.756444+00.
Its details are retained for reference, and this page is not indexed.
The registry records this reason: Renamed to io.github.ondraulehla/mcpcost.
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 −23
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Oct 26 −46
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- 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 security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Schema quality: excellent → good functional
- 14 Oct 26 +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.
- 13 Oct 26 0
- Server version: 0.1.2 → 0.1.3 functional
- 11 Oct 26 +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.
- 10 Oct 26 +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.
- 8 Oct 26 +1
- Schema quality: 91 → 102 ▼ functional
- 5 Oct 26 +1
- 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 security
- Schema quality: 80 → 91 ▼ functional
- Server version: 0.1.1 → 0.1.2 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://mcp-pulse.ulehla.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ulehla.dev | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d0ae0d82b617f36d133fd1b05e06ef5b |
| SANs: ulehla.dev, mcp-pulse.ulehla.dev, *.mcp-pulse.ulehla.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-pulse.ulehla.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| ulehla.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 301 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-pulse.ulehla.dev/mcp | Redirected | 301 | https://mcpcost.ulehla.dev/mcp |
| http (plaintext) | http://mcp-pulse.ulehla.dev/mcp | HTTPS enforced | 301 | https://mcp-pulse.ulehla.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_server Probe a server live ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | https URL of the MCP endpoint |
No output schema declared.
No examples provided.
lookup_server Look up a registry server ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| nameOrUrl | string | yes | Registry name or https URL of the server |
No output schema declared.
No examples provided.
registry_summary Registry summary ~33
Aggregates of the latest daily run: how many servers answer, token cost percentiles, protocol versions, heaviest servers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers Search the registry board ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.