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.

What3words

NPM · @PIPEWORX/MCP-WHAT3WORDS · 2 COMPONENTS

what3words MCP — 3-word grid geocoding

0 this week 81 Trust /100

Last scanned (6 hours ago)

Scores higher than 68% 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 & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-what3words). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 7 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 307 tokens (~76/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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.

  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 81

    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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-what3words@0.2.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-what3words
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-what3words/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3561061751
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:7e474abae7bbdef37699505d232a8a2d8961e2e0465d6ac2d4e4c463cb25cfd2031aa605593e76aa4ed7670f3d73155ae2fa470d510e8b0236265d92d

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 · 4 exposed · ~252 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
autosuggest ~112

Given a partial / mistyped 3-word input, return ranked suggestions. Optional focus point biases results toward proximity.

NameTypeReqDescription
countrystring–Restrict to ISO country code(s), comma-separated
focus_latitudenumber–Bias toward this latitude
focus_longitudenumber–Bias toward this longitude
inputstringyesPartial three-word string
languagestring–2-letter language
n_resultsnumber–1-100 (default 3)

No output schema declared.

No examples provided.

coords_to_words ~71

Convert a lat/lon to a what3words 3-word address. Defaults to English; pass a 2-letter language code for other languages.

NameTypeReqDescription
languagestring–2-letter language code (default "en")
latitudenumberyesLatitude
longitudenumberyesLongitude

No output schema declared.

No examples provided.

list_languages ~20

Supported languages for 3-word output (code + name).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

words_to_coords ~49

Convert a 3-word address ("filled.count.soap") to a lat/lon centre + 3m×3m bounding box.

NameTypeReqDescription
wordsstringyesThree-word address (dot-separated)

No output schema declared.

No examples provided.

Install

How do I install the What3words MCP server?

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

npm · @pipeworx/mcp-what3words

# add to Claude Code
claude mcp add pipeworx-io-what3words -- npx -y @pipeworx/mcp-what3words
Common questions

What is the What3words MCP server?

What3words is an MCP server listed in the public MCP registry as io.github.pipeworx-io/what3words. what3words MCP, 3-word grid geocoding. This page covers its npm package (@pipeworx/mcp-what3words).

Is the What3words MCP server safe to use?

What3words scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 What3words MCP server expose?

What3words exposes 4 tools: coords_to_words, words_to_coords, autosuggest, list_languages. Their descriptions and schemas cost roughly 252 tokens of context every time the server is loaded.

Is the What3words MCP server still maintained?

What3words is still listed as active in the MCP registry. We last reached this channel on 6 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 What3words MCP server under?

What3words 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 What3words MCP server?

VerifyMCP ran 15 checks on What3words, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about What3words: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.