Spark
Sign In
MCP Connector

Generate Project Status Badges

Generate eye-catching MCP badges for README files - default, server, client, and dev types with status and feature indicators.

Connect
Works with github
MCPX
Own this? Claim it

Maintainer of this project? Claim this page to edit the listing.

84
Spark score
out of 100
Updated Jan 2025
Fresher alternatives ↓
Version 1.0.0
Models
universal
Add to Favorites

Why it matters

Create visually appealing badges that represent the status and capabilities of your MCP projects. These badges can be easily integrated into documentation or project pages to provide at-a-glance information.

Outcomes

What it gets done

01

Generate standard, server, client, and development badges.

02

Include status and capability parameters in badge generation.

03

Support Markdown and HTML img tag formats for badges.

04

Provide special badges for MCP development projects.

Install

Add it to your toolbox

Run in your project directory:

curl -fsSL https://spark.entire.vc/get/vb-mcp-badges | bash

Overview

MCP Badges MCP Server

MCP Badges is a hosted image service that generates README badges for Model Context Protocol projects, with default, server, client, and dev badge types. Server and client badges can advertise specific supported features like resources, tools, prompts, or sampling. Use it to add a recognizable MCP badge to your server, client, or dev-tooling repository's README. Not applicable if you need an actual functional MCP server rather than a static badge image.

What it does

MCP Badges is a hosted badge-generation service (badge.mcpx.dev) that produces clear, eye-catching status badges for Model Context Protocol projects. Instead of an installable server, it is a URL-based image endpoint you embed directly in a README or HTML page to visually mark a repository as MCP-related.

When to use - and when NOT to

Use it when you maintain an MCP server, client, or dev-tooling repository and want a recognizable badge in the README that signals MCP compatibility, shows enabled/disabled status, or lists supported protocol features at a glance. Do not use it if you need a functional MCP server that exposes tools, resources, or prompts to an AI agent - this project only renders static badge images and has no runtime MCP capabilities of its own.

Capabilities

  • Default badges: a plain MCP badge, with an optional status parameter (status=on for "MCP Enabled", status=off for "MCP Disabled").
  • Server badges: type=server marks a repository as an MCP server; combine with features=resources,tools (or any of resources, prompts, tools, sampling) to advertise which server capabilities are supported.
  • Client badges: type=client marks a repository as an MCP client; combine with features=prompts,tools (or any of resources, prompts, tools, sampling, roots) to advertise client capabilities.
  • Dev badges: type=dev is recommended for MCP development tools, frameworks, and related tooling repositories.

How to install

No installation is required - embed the badge directly as a Markdown image or HTML tag:

Swap in ?status=on/?status=off, ?type=server, ?type=client, or ?type=dev with the relevant features query parameter to match your project.

Who it's for

Maintainers of MCP servers, clients, and developer tooling who want a quick, standardized visual badge in their README to communicate MCP support, connection status, and supported protocol features.

Source README

🔰 Model Context Protocol Badges

Quickly highlight your MCP project with clear, eye-catching badges

How to？

There are four types of badges: default, server, client, and dev. The default type supports the status parameter, while both server and client types support the features parameter.

Default Badges

  • ![](https://badge.mcpx.dev 'MCP')
  • <img src="https://badge.mcpx.dev" title="MCP"/>
Default Badges With Status

  • ![](https://badge.mcpx.dev?status=on 'MCP Enabled')
  • <img src="https://badge.mcpx.dev?status=on" title="MCP Enabled"/>

  • ![](https://badge.mcpx.dev?status=off 'MCP Disabled')
  • <img src="https://badge.mcpx.dev?status=off" title="MCP Disabled"/>

Server Badges

  • ![](https://badge.mcpx.dev?type=server 'MCP Server')
  • <img src="https://badge.mcpx.dev?type=server" title="MCP Server"/>

  • ![](https://badge.mcpx.dev?type=server&features=resources,tools 'MCP server with features')
  • <img src="https://badge.mcpx.dev?type=server&features=resources,tools" title="MCP server with features/>
  • Features supported by the MCP server
    • resources
    • prompts
    • tools
    • sampling

Client Badges

  • ![](https://badge.mcpx.dev?type=client 'MCP Client')
  • <img src="https://badge.mcpx.dev?type=client" title="MCP Client"/>

  • ![](https://badge.mcpx.dev?type=client&features=prompts,tools 'MCP client with features')
  • <img src="https://badge.mcpx.dev?type=client&features=prompts,tools" title="MCP client with features"/>
  • Features supported by the MCP client
    • resources
    • prompts
    • tools
    • sampling
    • roots

Dev Badges

Recommended for all MCP development-related projects, including tools, frameworks, etc.

  • ![](https://badge.mcpx.dev?type=dev 'MCP Dev')
  • <img src="https://badge.mcpx.dev?type=dev" title="MCP Dev"/>




❤️ Seamless Connectivity, Limitless Potential！

FAQ

Common questions

Discussion

Questions & comments · 0

Sign In Sign in to leave a comment.