Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

MightyS Pulse

REMOTE · PULSE.MIGHTYS.DEV

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

77 Trust /100

Last scanned (12 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

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 Security89
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 19 Nov 26 +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.

  • 18 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 17 Nov 26 +40
    • Transport: unverified → pass ▲ security
    • 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. security
    • MCP protocol: unverified → pass ▲ functional
    • 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 functional
  • 16 Nov 26 36

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://pulse.mightys.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=pulse.mightys.dev CN=YE2,O=Let's Encrypt,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA384 63538904a62a9e6a52dc42aa9a32744817b
SANs: pulse.mightys.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of pulse.mightys.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
mightys.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer realm="MightyS Pulse"

Bearer realm="MightyS Pulse"
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
referrer-policy no-referrer

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://pulse.mightys.dev/mcp Verified 200
http (plaintext) http://pulse.mightys.dev/mcp HTTPS enforced 308 https://pulse.mightys.dev/mcp
MCP tools · 9 exposed · ~1,478 tokens

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 →

Tool Tokens
check_install ~113

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
minutesinteger–Look back this many minutes, 1 to 1440 (default 10).
signal_typestring|null–Optional signal type to look for.

No output schema declared.

No examples provided.

get_errors ~190

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
fromstring|null–Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
periodstring–today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.
tostring|null–Optional end (exclusive), RFC 3339 instant with offset; use with from.

No output schema declared.

No examples provided.

get_funnel ~236

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
fromstring|null–Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
periodstring–today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
scopestring–session (default) or user.
stepsarrayyesSignal types in order, 2 to 8.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.
tostring|null–Optional end (exclusive), RFC 3339 instant with offset; use with from.
window_hoursnumber–Hours to complete the funnel, 1 to 8760 (default 24).

No output schema declared.

No examples provided.

get_overview ~187

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
fromstring|null–Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
periodstring–today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.
tostring|null–Optional end (exclusive), RFC 3339 instant with offset; use with from.

No output schema declared.

No examples provided.

get_retention ~182

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
fromstring|null–Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
periodstring–today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.
tostring|null–Optional end (exclusive), RFC 3339 instant with offset; use with from.

No output schema declared.

No examples provided.

get_schema ~86

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.

No output schema declared.

No examples provided.

list_apps ~40

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

signal_breakdown ~256

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.

NameTypeReqDescription
app_idstringyesApp id from list_apps.
fromstring|null–Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
limitinteger–How many values, 1 to 50 (default 10).
periodstring–today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
propertystringyesA props key (for example screen) or a system field (app_version, os_version, platform, country, device_model, locale).
signal_typestringyesThe signal type, for example screen.open.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.
tostring|null–Optional end (exclusive), RFC 3339 instant with offset; use with from.

No output schema declared.

No examples provided.

top_signals ~188

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

NameTypeReqDescription
app_idstringyesApp id from list_apps.
fromstring|null–Optional start, RFC 3339 instant with offset (for example 2026-11-01T00:00:00Z); use with to.
limitinteger–How many types, 1 to 50 (default 10).
periodstring–today, yesterday, 7d, 30d or 90d (UTC days, today included). Ignored when from and to are given.
test_modeboolean–true reads test (debug) signals only; false (default) reads real signals only.
tostring|null–Optional end (exclusive), RFC 3339 instant with offset; use with from.

No output schema declared.

No examples provided.

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.

remote · pulse.mightys.dev

# add to Claude Code
claude mcp add --transport http dev-mightys-pulse 'https://pulse.mightys.dev/mcp'
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.