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

REMOTE · US-CENTRAL1-NINE-CODE-ANWANI.CLOUDFUNCTIONS.NET · 2 COMPONENTS

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

+5 this week 77 Trust /100

Last scanned (21 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 790 tokens (~131/item across 6 items; 6 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
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 (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: this server exposes a tool marked destructive (delete_address) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

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.

  • 17 Nov 26 +5
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 22% → 100% ▲ functional
    • Schema quality: good → excellent functional
    • MCP protocol version: 2024-11-05 → 2025-06-18 functional
    • “create_address” reworded the description of “houseNumber” cosmetic
    • “create_address” reworded the description of “buildingName” cosmetic
    • “create_address” reworded the description of “category” cosmetic
    • “create_address” reworded the description of “city” cosmetic
    • “create_address” reworded the description of “country” cosmetic
    • “create_address” reworded the description of “floor” cosmetic
    • “create_address” reworded the description of “idempotency_key” cosmetic
    • “create_address” reworded the description of “instructions” cosmetic
    • “create_address” reworded the description of “label” cosmetic
    • “create_address” reworded the description of “latitude” cosmetic
    • “create_address” reworded the description of “longitude” cosmetic
    • “create_address” reworded the description of “neighborhood” cosmetic
    • “create_address” reworded the description of “ownerName” cosmetic
    • “create_address” reworded the description of “phone” cosmetic
    • “create_address” reworded the description of “pin” cosmetic
    • “create_address” reworded the description of “pinEnabled” cosmetic
    • “create_address” reworded the description of “postalCode” cosmetic
    • “create_address” reworded the description of “saudiNationalCode” cosmetic
    • “create_address” reworded the description of “street” cosmetic
    • “delete_address” reworded the description of “code” cosmetic
    • “patch_address” reworded the description of “changes” cosmetic
    • “patch_address” reworded the description of “code” cosmetic
    • “share_address” reworded the description of “code” cosmetic
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
    • “create_address” added an optional parameter “saudiNationalCode” cosmetic
  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

  • 31 Oct 26 +1

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

  • 29 Oct 26 +1

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

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 · Probed https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=misc.google.com CN=WR2,O=Google Trust Services,C=US 3 Nov 2026 26 Jan 2027 ECDSA 256 SHA256-RSA f84e107100dec36a1091621dedbe1c17
SANs: misc.google.com, *.actions.google.com, *.baseline.google.com, *.developer.google.com, *.developers.google.com, *.ewoq.google.com, *.arvr.google.com, *.eu.aiapp.cloud.goog, *.eu.aiapp.cloud-staging.goog, *.eu.aiapp.cloud-test.goog, *.firebase.google.com, *.ggp.google.com and 392 more
CN=WR2,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a07c4cded100ad9d66a5107b98
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of us-central1-nine-code-anwani.cloudfunctions.net. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
net. DS published 37331 13 Verified
cloudfunctions.net. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote Verified 200
http (plaintext) http://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote HTTPS enforced 302 https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote
MCP tools · 6 exposed · ~769 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
create_address ~531

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.

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: شارع التحلية

No output schema declared.

No examples provided.

delete_address ~48

Permanently delete an address 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.

list_addresses ~25

List addresses owned by the connected Anwani account (same quota as app/Telegram).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

patch_address ~94

Patch only provided fields (e.g. instructions). Does not clear omitted fields. Coordinates cannot be changed.

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.

session ~23

Check that Anwani is connected for this user. Does not return internal IDs.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

share_address ~48

Return the public deep link for an owned address code.

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

No output schema declared.

No examples provided.

Install

How do I install the Anwani MCP server?

Anwani is a hosted endpoint at https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · us-central1-nine-code-anwani.cloudfunctions.net

# add to Claude Code
claude mcp add --transport http anwani-app-anwani-mcp 'https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote'
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 hosted endpoint (https://us-central1-nine-code-anwani.cloudfunctions.net/mcpRemote).

Is the Anwani MCP server safe to use?

Anwani scores 77 out of 100 on VerifyMCP. 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 6 tools: session, list_addresses, create_address, patch_address, share_address, delete_address. Their descriptions and schemas cost roughly 769 tokens of context every time the server is loaded.

Does the Anwani MCP server require authentication?

No. We connected to Anwani without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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 did VerifyMCP test on the Anwani MCP server?

VerifyMCP ran 12 checks on Anwani, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Anwani: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.