PulseMCP

pulsemcp.com · MCP Registries / Discovery modeIntegrated

59 / 100Overall LLM-FriendlinessHow well an agent can use this service without handing work back to you.
Machine-Readability27 / 100
Custody / RiskUnknown
ConfidenceProvisional

Overall = mean of Interrupt Score 91 and Machine-Readability 2759 / 100. The badge is set by the Interrupt Score alone — how scoring works.

Confidence: Provisional (0.3) — Based on Tier 0/1 evidence only (passive checks, no live transaction attempt) — treat the number as a triage signal, not a verified outcome.

Custody posture hasn't been assessed yet.

What your agent can do here

A plain-English read on the probe evidence — each verdict links to the finding behind it.

Agent-readiness: Partially — an AI agent can use PulseMCP, but needs a human at signup — a CAPTCHA blocks it; little machine-readable surface.

Machine-Readability Score

Four check groups, equal weight: machine interfaces (OpenAPI, MCP server, llms.txt), browsing efficiency, element discoverability, and discovery/agent access (retrieval-bot robots.txt access, sitemap, schema.org). Each check is tagged with how strong the real-world evidence is that it changes agent behavior — proven, plausible, or emerging — grades are honesty labels, they never weight the score. A separate signal about ease of integration — it never enters the Interrupt Score or badge above.

27 / 100
Tier 2 not tested. No live signup/checkout attempt has run against this vendor yet — this is not the same as "no Tier 2 interrupts found." Either the vendor hasn't opted in to Tier 2 consent, or an automated ToS-ban/bot-prohibition signal structurally prevents Tier 2 from ever being attempted (see the findings below).

Interrupt tier: Low-Interrupt — derived from 1 finding; interrupt score 91 / 100. It alone drives the badge above; the headline Overall score blends it 50/50 with Machine-Readability.

Every tool starts at 100. Each interrupt found subtracts a penalty of base weight × timing × hardness × evidence — the multiplier values below come from the same rubric tables the score is computed with, so the arithmetic in this matrix reproduces the number exactly.

Interrupt foundBase weight× Timing× Hardness× Evidence= Penalty
Starting score100
CAPTCHA / bot-challengeBefore any account existsHomepage load triggered a recaptcha challenge page (matched signal: iframe[src*="recaptcha"]).6×1one-time setup×2.5hard×0.6Tier 0 (passive scan)−9
Total penalty9
Interrupt Score = 100 − 9 = 9191

Checked — nothing found

A check only turns green when a probe tier capable of detecting that interrupt actually ran and found nothing. Not tested ≠ clean.

Not yet tested

Less-interrupting alternatives

Other MCP Registries / Discovery tools in the same mode (integrated), ranked by Overall LLM-Friendliness — comparable to this listing because they share its usage mode.

Embed this rating

Copy this snippet to display your Interrupt Index seal on your site — the seal image and link stay in sync with your latest probe automatically. Pick the variant that matches your site’s theme.

Light (default)

<a href="https://interruptindex.com/tools/pulsemcp"><img src="https://interruptindex.com/badge/pulsemcp.svg" alt="PulseMCP — Interrupt Index agent-readiness rating" height="64"></a>

Dark

<a href="https://interruptindex.com/tools/pulsemcp"><img src="https://interruptindex.com/badge/pulsemcp.svg?theme=dark" alt="PulseMCP — Interrupt Index agent-readiness rating" height="64"></a>