Vendor: chatbase.co · entry id 14-chatbase · source 14-inbound-plg-chat.md line 84
A working server exists but somebody other than the vendor built it. It can be abandoned without the vendor noticing. 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:
community
mcp_url, verbatim from the file:
https://zapier.com/mcp/chatbase (Zapier-hosted; viaSocket, Activepieces and Pipedream host equivalents)
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.
Install, as the source shows it:
npm install -g chatbasequoted from https://www.chatbase.co/docs/cli/overview on 2026-09-27, via npm
npx chatbasequoted from https://www.chatbase.co/docs/cli/overview on 2026-09-27, via npx
Login or key hint seen on the page:
chatbase auth
Subcommands seen with the binary:
agents, auth, chat, config
Packages seen, with the version on 2026-09-27:
Where it was documented:
A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.
api_gate, verbatim from the file:
paid (limited free tier). Free plan: $0/mo, 50 message credits, inactive agents deleted after 14 days, no API access. API access starts at the Standard tier ($150/mo); Hobby ($40/mo) does not include it.
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.
No GitHub organisation could be tied to chatbase.co with evidence on 2026-09-08.
Recorded by the harvest: github candidates were seen but none passed the evidence rules.
5 candidate accounts seen and rejected by the evidence rules: Chatbase-co, ChatBaseSDK, chatbasedapk, ChatBase-official, ChatbaseLabs. A name match alone is never accepted; the account has to point at the vendor domain.
A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.
Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.
4 source URLs. Raw sources field, verbatim:
https://www.chatbase.co, https://www.chatbase.co/pricing, https://www.chatbase.co/docs, https://zapier.com/mcp/chatbase
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.