Vendor: klavis.ai · entry id 07-klavis-ai · source 07-mcp-infrastructure.md line 225
The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-09-02. On 2026-09-04 the recorded URL served a documentation page, not an MCP endpoint. That is where to read about the server, not where to connect to it. An agent needs the second.
mcp_status, verbatim from the file:
official
mcp_url, verbatim from the file:
https://www.klavis.ai/docs/concepts/strata.md (first-party docs for the hosted Strata server; endpoint https://strata.klavis.ai/mcp/ per the official registry entry ai.klavis/strata; source at https://github.com/Klavis-AI/klavis, Apache-2.0)
A tool below is one the server NAMES. Nobody has called it. That is the same two tier honesty rule the rest of the directory runs on: a named tool is research, and BENCH-TESTED stays the only claim that anybody ran anything.
141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. Every name across every server is on the tools index.
No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence.
api_gate, verbatim from the file:
unknown - pricing page referenced but not disclosed in the fetched content
949 of 1252 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess.
No documentation URL recorded.
727 of 1252 entries are in the same position. Blank is legal and it is published as blank.
Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.
The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.
A github.com URL already appears somewhere in this entry, which is a seed for that rail and not a measurement of repo health:
github.com/Klavis-AI tied to the vendor by rule 1, account website www.klavis.ai has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| deep-swe | other | 0 | 2026-08-04 | ||
| Toolathlon-mvp | other | 0 | 2026-06-02 | ||
| klavis | MCP server | Klavis AI: MCP integration platforms that let AI agents use tools reliably at any scale | 5,801 | 2026-06-01 | ts-v2.20.0 |
| python-sdk | SDK | 4 | 2026-01-29 | 2.20.0 | |
| typescript-sdk | SDK | 0 | 2026-01-29 | 2.20.0 |
Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.
No job tag on this entry.
Reason recorded by the tagging pass: unclear. The entry states the product is agent-training-data infrastructure and explicitly flags the mismatch with Composio/Pipedream. proxy-tool-calls-to-saas is plausible from the "600+ real tools" line and unsupported by everything else on the page.
981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag.
7 source URLs. Raw sources field, verbatim:
https://www.klavis.ai, https://klavis.ai/pricing (fetched; no pricing figures returned), https://www.klavis.ai/docs/quickstart.md, https://www.klavis.ai/docs/concepts/strata.md, https://www.klavis.ai/docs/api-reference/strata/create.md, https://github.com/Klavis-AI/klavis, https://registry.modelcontextprotocol.io/v0/servers?search=klavis
Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the methodology page.