Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Anwani

NPM · ANWANI-MCP · 2 COMPONENTS

Anwani: digital addressing — permanent 9-digit codes for physical locations.

+30 this week 70 Trust /100

Last scanned (14 hours ago)

Scores higher than 41% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1166 tokens (~166/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (71% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +29
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
    • Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. security
    • Capabilities: fail → unverified ▼ functional
    • Stability: unverified → 0.00 ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: 100 functional
    • First check of Tool coverage: 71 functional
    • First check of Tool coverage: 100 functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
    • Package version: 1.1.3 → 1.1.7 functional
  • 12 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 11 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/anwani-mcp@1.1.7

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,166 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_session ~91

Returns connection status for the signed-in Anwani user as {ok, connected, scopes, expiresAt}. Identity comes from the saved OAuth token (no parameters) and never includes Firebase UIDs or internal IDs. Use it when unsure the user is signed in before calling address tools; do not use it to list or change addresses (use list_addresses, get_address, create_address, patch_address instead). Read-only.

Input schema present but exposes no named parameters.

NameTypeReqDescription
connectedboolean–True when a valid OAuth token is saved.
expiresAt––Token expiry (epoch ms or ISO string), or null.
okboolean–True when the request succeeded.
scopesarray–Granted scopes, e.g. address:read.

No examples provided.

create_address ~578

Creates one new permanent 9-digit Anwani address within the account quota and returns {ok, code, created, url}. Requires a real user-provided latitude/longitude (map pin) — NEVER invent coordinates, city, or name; if the user gave no location (coords, Maps link, or clear place), ask first and do not call with sample data. Use it for new places; use patch_address to edit an existing code. Not idempotent unless the same idempotency_key is retried, which returns the original result.

NameTypeReqDescription
buildingNamestring–Building name if provided. Example: برج الملقا
categorystring–Optional category tag. Example: home, work, shop
citystring–City only if the user provided it. Example: الرياض
countrystring–Country name or ISO-ish label if provided. Example: السعودية or SA
floor––Floor / level of the unit. Example: 5 or G
houseNumberstring–House / unit number if provided. Example: 12
idempotency_keystringyesClient-generated key to safely retry the same create without duplicates. Example: create-2026-11-16-home-a1b2c3d4
instructionsstring–Delivery notes for the courier (door color, buzzer, landmark). Example: الباب الأصفر، دق الجرس
labelstring–Short friendly label for the address. Example: البيت or المكتب
latitudenumberyesUser-provided latitude only — never invent. Example: 24.7136
longitudenumberyesUser-provided longitude only — never invent. Example: 46.6753
neighborhoodstring–Neighborhood / district if provided. Example: حي الملقا
ownerNamestring–Display name for the address owner only if the user provided one. Example: أحمد
phonestring–Contact phone in international or local form if provided. Example: +9665xxxxxxx
pinstring–Optional 4-digit privacy PIN that couriers must enter to view details. Example: 4821
pinEnabledboolean–When true, details stay locked until the correct 4-digit PIN is entered. Example: true
postalCodestring–Postal / ZIP code if provided. Example: 13521
saudiNationalCodestring–Optional Saudi national short code (4 letters + 4 digits, AAAA####) when country is SA. Does not replace the Anwani 9-digit code. Example: RADC2959
streetstring–Street name if the user provided it. Example: شارع التحلية
NameTypeReqDescription
codestring–New permanent 9-digit Anwani address code.
createdboolean–True when a new address was made.
okboolean–True when the request succeeded.
urlstring–Public link https://9code.app/code/{code}.

No examples provided.

delete_address ~82

Permanently deletes an owned address and its photos (irreversible) and returns {ok, deleted}. Prefer patch_address for edits; confirm user intent before calling. Fails if the code is not owned by the connected account.

NameTypeReqDescription
codestringyesAnwani permanent 9-digit address code (digits 1–9 only). Example: 365131449

No output schema declared.

No examples provided.

get_address ~94

Returns one owned address by its permanent 9-digit code as {ok, address}. Use it when the user already provided a code; use list_addresses to discover codes. Fails clearly if the code is invalid or not owned by the connected account. Read-only; does not mutate.

NameTypeReqDescription
codestringyesAnwani permanent 9-digit address code (digits 1–9 only). Example: 365131449
NameTypeReqDescription
addressobject–One owned Anwani address (no internal user IDs).
okboolean–True when the request succeeded.

No examples provided.

list_addresses ~76

Returns all addresses owned by the connected account as {ok, addresses[]} (same quota as app/Telegram, typically up to 10), newest updates first. Use it to browse or when you do not yet know a 9-digit code; use get_address when you already have a code. Read-only; the account comes from OAuth.

Input schema present but exposes no named parameters.

NameTypeReqDescription
addressesarray–Owned addresses, newest updates first.
okboolean–True when the request succeeded.

No examples provided.

patch_address ~146

Updates only the fields present in `changes` on an owned address and returns the result; omitted fields stay unchanged. Coordinates are immutable after create. Use it to edit label, instructions, floor and similar fields; use create_address for a new pin; use delete_address only to remove an address permanently. Fails if the code is not owned by the connected account.

NameTypeReqDescription
changesobjectyesPartial address fields to update. Omit keys you do not want to change. Example: {"instructions":"الباب الأصفر","floor":5}
codestringyesAnwani permanent 9-digit address code (digits 1–9 only). Example: 365131449

No output schema declared.

No examples provided.

share_address ~99

Returns the public deep link https://9code.app/code/{code} for an owned address as {ok, code, url, shareText}. Use it when the user wants a shareable URL; it does not modify the address. Fails if the code is invalid or not owned by the connected account.

NameTypeReqDescription
codestringyesAnwani permanent 9-digit address code (digits 1–9 only). Example: 365131449
NameTypeReqDescription
codestring–The 9-digit address code.
okboolean–True when the request succeeded.
shareTextstring–Text to paste when sharing.
urlstring–Public link https://9code.app/code/{code}.

No examples provided.

Install

How do I install the Anwani MCP server?

Anwani runs locally as an npm package, launched with npx -y anwani-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · anwani-mcp

# add to Claude Code
claude mcp add anwani-app-anwani-mcp -- npx -y anwani-mcp
Common questions

What is the Anwani MCP server?

Anwani is an MCP server listed in the public MCP registry as io.github.Anwani-app/anwani-mcp. Anwani: digital addressing, permanent 9-digit codes for physical locations. This page covers its npm package (anwani-mcp).

Is the Anwani MCP server safe to use?

Anwani scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Anwani MCP server expose?

Anwani exposes 7 tools: check_session, list_addresses, get_address, create_address, patch_address, and 2 more. Their descriptions and schemas cost roughly 1,166 tokens of context every time the server is loaded.

Is the Anwani MCP server still maintained?

Anwani is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Anwani MCP server under?

Anwani declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Anwani MCP server?

VerifyMCP ran 16 checks on Anwani, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.