# MightyS Pulse (remote · pulse.mightys.dev)

Read your MightyS Pulse app analytics: users, signals, retention, funnels and errors.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

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

## Channel facts

- Endpoint: `https://pulse.mightys.dev/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## 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-11-21.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1557 tokens (~173/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the MightyS Pulse MCP server?

MightyS Pulse is a hosted endpoint at https://pulse.mightys.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-mightys-pulse 'https://pulse.mightys.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-mightys-pulse": {
      "url": "https://pulse.mightys.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-mightys-pulse": {
      "type": "http",
      "url": "https://pulse.mightys.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-mightys-pulse]
url = "https://pulse.mightys.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-mightys-pulse": {
      "type": "remote",
      "url": "https://pulse.mightys.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-mightys-pulse --url 'https://pulse.mightys.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-mightys-pulse:
    url: "https://pulse.mightys.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-mightys-pulse": {
      "Transport": "http",
      "Url": "https://pulse.mightys.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-mightys-pulse -t streamable-http -u 'https://pulse.mightys.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-19 (score 77, +1)

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

### 2026-11-18 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 76, +40)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-11-16 (score 36)

First indexed and scored.

## MCP tools (9)

### `list_apps` (~40 tokens)

List apps

Lists the apps this token can read: id, name, organization, platforms and the time of the last signal. Call this first to get an app_id.

### `get_overview` (~187 tokens)

App overview

Users, sessions (a session ends after 30 minutes without a signal), signals, average session length and the top signal types of one app in a period. The same numbers as the portal overview.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `from` (string|null): Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
- `period` (string): today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.
- `to` (string|null): Optional end (exclusive), RFC 3339 instant with offset; use with from.

### `top_signals` (~188 tokens)

Top signal types

The most frequent signal types of one app in a period, with counts and first and last time seen.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `from` (string|null): Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
- `limit` (integer): How many types, 1 to 50 (default 10).
- `period` (string): today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.
- `to` (string|null): Optional end (exclusive), RFC 3339 instant with offset; use with from.

### `signal_breakdown` (~256 tokens)

Signal breakdown

Values of one property (or system field such as app_version, os_version, platform, country, device_model, locale) for one signal type of one app in a period, with counts.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `from` (string|null): Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
- `limit` (integer): How many values, 1 to 50 (default 10).
- `period` (string): today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
- `property` (string, required): A props key (for example screen) or a system field (app_version, os_version, platform, country, device_model, locale).
- `signal_type` (string, required): The signal type, for example screen.open.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.
- `to` (string|null): Optional end (exclusive), RFC 3339 instant with offset; use with from.

### `get_retention` (~182 tokens)

Retention

Weekly retention cohorts of one app: how many users (or sessions when the app sends no user) come back in the following weeks. Plans without retention answer with an error.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `from` (string|null): Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
- `period` (string): today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.
- `to` (string|null): Optional end (exclusive), RFC 3339 instant with offset; use with from.

### `get_funnel` (~236 tokens)

Funnel

A funnel of 2 to 8 signal types in order: how many sessions (or users) reached each step within the window. Plans without funnels answer with an error.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `from` (string|null): Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
- `period` (string): today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
- `scope` (string): session (default) or user.
- `steps` (array, required): Signal types in order, 2 to 8.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.
- `to` (string|null): Optional end (exclusive), RFC 3339 instant with offset; use with from.
- `window_hours` (number): Hours to complete the funnel, 1 to 8760 (default 24).

### `check_install` (~113 tokens)

Check an install

Did any signal (or one signal type) arrive from this app in the last minutes, test and real ones? Answers the count, the last time, the SDK names and versions, and how many were test (debug) signals. Call it after installing the SDK.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `minutes` (integer): Look back this many minutes, 1 to 1440 (default 10).
- `signal_type` (string|null): Optional signal type to look for.

### `get_schema` (~86 tokens)

Signal schema

What this app sends: signal types of the last 30 days with their counts, the props keys of the 8 most frequent types, and the system fields you can break down or filter by.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.

### `get_errors` (~190 tokens)

Errors and crashes

Errors and crashes of one app in a period: crash-free sessions, crashes, errors and affected users, the same per app version, and the 20 largest error groups. The same numbers as the portal Errors screen.

Input parameters:

- `app_id` (string, required): App id from list_apps.
- `from` (string|null): Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
- `period` (string): today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
- `test_mode` (boolean): true reads test (debug) signals only; false (default) reads real signals only.
- `to` (string|null): Optional end (exclusive), RFC 3339 instant with offset; use with from.

## Diagnostics

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

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 76
- 2026-11-17: 76
- 2026-11-16: 36

## Common questions

### What is the MightyS Pulse MCP server?

MightyS Pulse is an MCP server listed in the public MCP registry as dev.mightys/pulse. Read your MightyS Pulse app analytics: users, signals, retention, funnels and errors. This page covers its hosted endpoint (https://pulse.mightys.dev/mcp).

### Is the MightyS Pulse MCP server safe to use?

MightyS Pulse scores 77 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 MightyS Pulse MCP server expose?

MightyS Pulse exposes 9 tools: list_apps, get_overview, top_signals, signal_breakdown, get_retention, and 4 more. Their descriptions and schemas cost roughly 1,478 tokens of context every time the server is loaded.

### Does the MightyS Pulse MCP server require authentication?

Yes. MightyS Pulse asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the MightyS Pulse MCP server still maintained?

MightyS Pulse is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the MightyS Pulse MCP server?

VerifyMCP ran 13 checks on MightyS Pulse, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://pulse.mightys.dev/mcp
- Authorisation metadata: https://pulse.mightys.dev/.well-known/oauth-protected-resource/mcp
- Website: https://pulse.mightys.dev/docs/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/dev-mightys-pulse/pulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-mightys-pulse/pulse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-mightys-pulse/pulse.json
- HTML version of this page: https://verifymcp.io/servers/dev-mightys-pulse/pulse
