Tengence Search MCP vs meshdb
Tengence Search MCP is an MCP server published by tengence.com. Marketplaces we read that list it: 1 (Official MCP Registry). meshdb is an MCP server published by meshpop. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.5 Downloads/month (npm): 1 233 Downloads/week (npm): 28 Not marked · First seen |
Listed Version: 1.0.1 No figure published 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
| Fact | Tengence Search MCP | meshdb |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@tengence/search-mcp) | Not stated |
| Transport (differs) | stdio | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 7, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/tengence-team/tengence-search-mcp | github.com/meshpop/meshdb |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Tengence Search MCP
Thin MCP wrapper for the Tengence Search SaaS: push data and search via official APIs.
meshdb
Distributed search and indexing MCP — full-text search, semantic queries, structured data
How to run each
Tengence Search MCP As a local MCP server: npm package
claude mcp add --transport stdio search -- npx -y @tengence/search-mcpmeshdb
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 meshdb publish no settings it asks for, so we do not compare settings.
What it can do: Tengence Search MCP · What it can do: meshdb · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.