Datris vs TRIZ
Datris is an MCP server published by datris. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). TRIZ is an MCP server published by sv. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-24. 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 |  Datris | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.53.0 Downloads/month (PyPI): 10 146 Downloads/week (PyPI): 1 062 Forks (GitHub): 1 Stars (GitHub): 13 Not marked · First seen |
Listed Version: 0.3.0 Downloads/month (npm): 1 388 Downloads/week (npm): 228 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 1.53.0 Downloads/month (PyPI): 10 146 Downloads/week (PyPI): 1 062 Forks (GitHub): 1 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 1 388 Downloads/week (npm): 228 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 | Datris | TRIZ |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 13 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | On your machine (datris-mcp-server) | On your machine (triz-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | 3, secrets among them: 0 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/datris/datris-platform-oss | github.com/sv/triz-skill |
| Changes in the last 7 days (differs) | 4 | 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
Datris
The data control plane for AI agents — acquire, validate, land, and query data over MCP.
TRIZ
Deterministic, read-only TRIZ knowledge: parameters, principles, matrix, tool routing, effects.
How to run each
Datris As a local MCP server: PyPI package
claude mcp add --env "DATRIS_API_KEY=<YOUR_DATRIS_API_KEY>" --env "DATRIS_API_URL=<YOUR_DATRIS_API_URL>" --transport stdio datris -- uvx datris-mcp-serverRequires: DATRIS_API_KEY (secret), DATRIS_API_URL
TRIZ As a local MCP server: npm package
claude mcp add --transport stdio triz -- npx -y triz-mcpCommands 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
Only Datris asks for
DATRIS_API_KEY (secret)DATRIS_API_URL
Only TRIZ asks for
TRIZ_DATA_DIRTRIZ_GRAPHTRIZ_REGISTRY
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Datris · What it can do: TRIZ · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.