Vendor: origami.chat · entry id 02-origami · source 02-engagement-outbound.md line 1491
No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-12.
mcp_status, verbatim from the file:
none-found
The mcp_url field is empty on this entry. 417 of 1252 entries are.
This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.
Install, as the source shows it:
npm install -g @weborigami/origamiquoted from https://www.npmjs.com/package/@weborigami/origami on 2026-09-27, via npm, a third party source
npm install -g origami-cliquoted from https://www.npmjs.com/package/origami-cli on 2026-09-27, via npm, a third party source
Packages seen, with the version on 2026-09-27:
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:
unknown
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 text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.
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 origami.chat with evidence on 2026-09-15.
Recorded by the harvest: not checked: gh CLI missing or not logged in.
No job tag on this entry.
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.
4 source URLs. Raw sources field, verbatim:
https://origami.chat/, https://origami.chat/docs, https://origami.chat/developers, https://yc-oss.github.io/api/industries/sales.json
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.