The AliveMCP status badge

Live previews

All three widgets on this page render the same JS. The only difference is the attributes on the mount <div>.

1. Default — "Is your MCP alive?" CTA

No configuration. Good for landing pages and blog posts where you want a discovery prompt, not a per-server status.

<div id="alivemcp-embed"></div>
<script async src="https://alivemcp.com/embed.js"></script>

2. Server status card

Shows live state, 30-day uptime, p95 latency, and last-probe age for a specific server. Ideal for a project README or the top of your docs site. Today the status feed is pre-MVP; the widget renders a pending card that links to the server's status page. Once the collector ships, the same embed starts rendering live numbers automatically — no code change on your end.

<div id="alivemcp-embed"
     data-server="example-mcp-server"></div>
<script async src="https://alivemcp.com/embed.js"></script>

3. Inline badge (compact)

A small inline pill for footers, nav bars, or the first paragraph of a README. Roughly the size of a shields.io badge, but live.

<div id="alivemcp-embed"
     data-server="example-mcp-server"
     data-style="badge"></div>
<script async src="https://alivemcp.com/embed.js"></script>

4. Light theme

Add data-theme="light" for pages with a white background.

<div id="alivemcp-embed"
     data-server="example-mcp-server"
     data-theme="light"></div>
<script async src="https://alivemcp.com/embed.js"></script>

Note: on this preview page each demo uses class="alivemcp-embed" instead of id="alivemcp-embed" so multiple widgets can live on the same page. The script supports both — on a normal site with one widget, use the id form from the snippet.

All options

README badge (Markdown)

GitHub READMEs don't execute <script> tags in rendered Markdown. For a README badge that works in the GitHub view, use an image badge while we're building the SVG endpoint — drop in the live widget on your project's docs site (which does execute JS).

<!-- GitHub README: link-only (image SVG badge ships next week) -->
[![AliveMCP](https://img.shields.io/badge/AliveMCP-monitored-22c55e)](https://alivemcp.com/status/your-slug)

<!-- Docs site / landing page: full interactive badge -->
<div id="alivemcp-embed" data-server="your-slug" data-style="badge"></div>
<script async src="https://alivemcp.com/embed.js"></script>

What the widget costs

• $0. The widget is free for every public MCP server, forever. The deal: we keep a small "Powered by AliveMCP" link at the bottom of each card — that's how we grow. If your MCP is private, the same widget works behind the scenes on the Team plan ($49/mo) and you can hide attribution.
• Zero dependencies. No React, no web components, no polyfills, no tracking pixel. Vanilla JS, inline CSS, single fetch to alivemcp.com.
• ~10 KB uncompressed (<3 KB gzipped). Loaded async so it never blocks your page render.
• No cookies, no fingerprinting. The widget sends no headers beyond the default GET. Our collector logs the path and your server's public slug; that's it.

What about CSP?

If your site sends a Content-Security-Policy header, you'll need to allow three things:

• script-src: add https://alivemcp.com.
• connect-src: add https://alivemcp.com so the widget can fetch status.
• style-src: add 'unsafe-inline' — the widget injects a small inline stylesheet. If you don't allow 'unsafe-inline', we have a second CSP-safe build coming.

Versioning & breakage policy

embed.js is served from a single canonical URL. We version the public API of the mount <div> (the data-* attributes): existing attribute names will keep their meaning forever. New attributes are opt-in. If we ever need to break something, we'll ship embed-v2.js and leave embed.js running the old contract — so the badge on a 5-year-old README won't render as a broken box.