An agent can connect on its own if it already holds ANWANI_MCP_TOKEN.Remote endpoint behind a static API key or header. The registry never sees the value; the agent fills the placeholder.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Dependencies
[email protected]npmthis version is not known to the dependency resolver
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
Create one address within the user quota. Requires a real map pin from the user (latitude/longitude). NEVER invent coordinates, city, or display name. If the user did not provide a location (coords, Maps link, or clear place), ask them first — do not call this tool with sample/demo data.
delete_addressdestructive
Permanently delete an address owned by the connected account.
list_addressesread-only
List addresses owned by the connected Anwani account (same quota as app/Telegram).
patch_address
Patch only provided fields (e.g. instructions). Does not clear omitted fields. Coordinates cannot be changed.
sessionread-only
Check that Anwani is connected for this user. Does not return internal IDs.
share_addressread-only
Return the public deep link for an owned address code.