BMI Kit vs EVMole

A side-by-side look at the BMI Kit and EVMole MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

B
BMI KitDeveloper Tools · Remote HTTP/SSE
Body composition for AI: BMI, body fat, FFMI, waist-to-height, plus saved measurement trends.42FairAuth: not declared
EVMole logoEVMoleDeveloper Tools · Local subprocess (stdio)Local structured analysis of deployed EVM runtime bytecode51GoodAuth: not declared

Verdict: choose BMI Kit for developer tools work over a hosted endpoint; choose EVMole for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

B
Choose BMI Kit when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a remote HTTP/SSE transport.
Explore BMI Kit

EVMole logoChoose EVMole when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
Explore EVMole

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
B
BMI Kit
EVMole logoEVMole
CategoryDeveloper ToolsDeveloper Tools
Quality signal42/100 · Fair51/100 · Good
Install commandConfirmedConfirmed
TransportRemote HTTP/SSELocal subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—472
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

BMI Kit tools

No tool names declared yet. Check the project README from the listing page.

EVMole tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

BMI Kit

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "bmi-kit-2": {
      "url": "https://bmikit.com/mcp"
    }
  }
}

EVMole

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "evmole": {
      "command": "npx",
      "args": [
        "-y",
        "evmole"
      ]
    }
  }
}

Frequently asked questions

BMI Kit is categorized under Developer Tools and uses a remote HTTP/SSE transport. EVMole belongs to Developer Tools and uses a local stdio subprocess. Pick BMI Kit for developer tools work and EVMole for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

BMI Kit has no declared pricing — check the project's own site. EVMole has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add bmi-kit-2 and evmole as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, BMI Kit has a quality signal of 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. EVMole has 51/100 (Good) with 0 views, 0 installs and 472 GitHub stars.