whereamimentioned packages
This repository is generated. It is a one-way copy of the packages/ directory of a private repository, rebuilt from scratch and force-pushed on every release tag. Nothing here is edited by hand: a commit made in this repository is destroyed by the next sync, with no warning and no merge, and a pull request opened here is opened against a copy of a file its author cannot reach and will be destroyed the same way. Please do not send pull requests to this repository. The root package.json, vitest.config.mts and pnpm-lock.yaml are generated by the same sync and exist only so that this tree installs, typechecks, tests and builds on its own.
What is here
Three npm packages, versioned and released together, for whereamimentioned, which measures whether AI assistants mention your brand.
packages/cli, published as @whereamimentioned/cli. The wam command line: the free site checks that need no account, scans and reports from a terminal or from CI, and the installer for the MCP server. Documented at whereamimentioned.com/docs/cli.
packages/mcp-stdio, published as @whereamimentioned/mcp. A small stdio bridge for MCP clients that cannot add a remote URL. It forwards each request to the hosted server at https://whereamimentioned.com/api/mcp and holds no tool definitions of its own. Documented at whereamimentioned.com/docs/mcp.
packages/api-client, published as @whereamimentioned/api-client. The typed client and response types for the REST API at https://whereamimentioned.com/api/v1, described by its OpenAPI document. The other two packages are built against it.
None of the three contains server code, database access or a secret. Every request they make goes to https://whereamimentioned.com.
Releases
Releases run from this repository so that npm provenance and GitHub artifact attestations are generated. Each release tag (cli-v*) carries a GitHub Release with the CLI tarball and a SHA256SUMS file, and the npm packages carry provenance pointing back here.
Reporting a problem
Open an issue in this repository's issue tracker. Issues are not part of the synced tree, so they survive the sync; pull requests do not. For anything involving your account or your data, use whereamimentioned.com/contact instead of a public issue.