Ext Ops Panel
Open dashboard
Comparison

com.jojapi/eyecon vs io.github.Leximo-AI/leximo-ai-call-assistant-mcp-server

com.jojapi/eyecon is an MCP server published by jojapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Leximo-AI/leximo-ai-call-assistant-mcp-server is an MCP server published by Leximo-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecom.jojapi/eyeconio.github.Leximo-AI/leximo-ai-call-assistant-mcp-server
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (npm): 136
Downloads/week (npm): 14
Forks (GitHub): 2
Stars (GitHub): 2
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

com.jojapi/eyecon vs io.github.Leximo-AI/leximo-ai-call-assistant-mcp-server
Factcom.jojapi/eyeconio.github.Leximo-AI/leximo-ai-call-assistant-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub2
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.jojapi.com/eyecon)On your machine (leximo-ai-call-assistant-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/leximo-ai/leximo-ai-call-assistant-mcp-server
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-24no remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

com.jojapi/eyecon

In its own words, on Official MCP Registry:

Eyecon: Use the no.1 API for a true caller ID to identify name and see photos. 100% success rate.

io.github.Leximo-AI/leximo-ai-call-assistant-mcp-server

In its own words, on Official MCP Registry:

Schedule AI phone calls, manage assignments, and check credits from Claude.

How to run each

com.jojapi/eyecon As a remote MCP server

Claude Code
claude mcp add --transport http eyecon https://mcp.jojapi.com/eyecon

io.github.Leximo-AI/leximo-ai-call-assistant-mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --env "LEXIMO_API_TOKEN=<YOUR_LEXIMO_API_TOKEN>" --transport stdio leximo-ai-call-assistant-mcp-server -- npx -y leximo-ai-call-assistant-mcp-server

Requires: LEXIMO_API_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only com.jojapi/eyecon has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of com.jojapi/eyecon publish no settings it asks for, so we do not compare settings.

What it can do: com.jojapi/eyecon · What it can do: io.github.Leximo-AI/leximo-ai-call-assistant-mcp-server · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built