Lob
NPM · @PIPEWORX/MCP-LOB · 2 COMPONENTS
Lob MCP — US address verification, bulk verification, and autocompletion (docs.lob.com). BYO-key…
Available components
Last scanned (7 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
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-lob). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 676 tokens (~225/item across 3 items; 3 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 Management23
- Stability observed for 7 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-lob@0.2.1
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-lob |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-lob/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649712523 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3c6741a06d37800f06f88afd8d3b584b586c2c94e84bbc3a3db0104dfec72c117980fe509b102773a400df11bc494bba7eac5bf9c98faf2454e418319 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
lob_autocomplete ~166
Autocomplete a partial US address. Given a primary-line prefix (and optional city/state/zip), returns up to 10 full address suggestions. Suggestions are candidates, not guaranteed deliverable — verify with lob_verify_address. Example: lob_autocomplete({ address_prefix: "185 B", city: "San Francisco", state: "CA", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Lob API key (sign up at https://dashboard.lob.com/). |
| address_prefix | string | yes | Partial primary line to complete, e.g. "185 B". |
| city | string | – | City filter (optional). |
| state | string | – | Two-letter state filter (optional). |
| zip_code | string | – | ZIP filter (optional). |
No output schema declared.
No examples provided.
lob_verify_address ~307
Verify a single US address for deliverability and return USPS-standardized/corrected components (ZIP+4, DPV codes, county, lat/lon). Pass structured components (primary_line, city, state, zip_code) OR a single freeform `address` string — not both. Example: lob_verify_address({ primary_line: "185 Berry St", secondary_line: "Ste 6100", city: "San Francisco", state: "CA", zip_code: "94107", _apiKey: "your-key" }) or lob_verify_address({ address: "185 Berry St Ste 6100 San Francisco CA 94107", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Lob API key (sign up at https://dashboard.lob.com/). |
| address | string | – | Full single-line address, e.g. "185 Berry St San Francisco CA 94107". Use this OR the component fields, not both. |
| city | string | – | City name, e.g. "San Francisco". |
| primary_line | string | – | Primary street address line, e.g. "185 Berry St". |
| secondary_line | string | – | Secondary line (apt/suite/unit), e.g. "Ste 6100". Optional. |
| state | string | – | Two-letter state code, e.g. "CA". |
| zip_code | string | – | ZIP or ZIP+4, e.g. "94107". |
No output schema declared.
No examples provided.
lob_verify_bulk ~152
Verify a list of US addresses in one request. Each address is an object with primary_line, city, state, zip_code (secondary_line/recipient optional). Returns per-address deliverability + corrected components. Example: lob_verify_bulk({ addresses: [{ primary_line: "210 King St", city: "San Francisco", state: "CA", zip_code: "94107" }], _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Your Lob API key (sign up at https://dashboard.lob.com/). |
| addresses | array | yes | Array of address objects, each with primary_line, city, state, zip_code (secondary_line, recipient, urbanization optional). |
No output schema declared.
No examples provided.
How do I install the Lob MCP server?
Lob runs locally as an npm package, launched with npx -y @pipeworx/mcp-lob. 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-lob
claude mcp add pipeworx-io-lob -- npx -y @pipeworx/mcp-lob
What is the Lob MCP server?
Lob is an MCP server listed in the public MCP registry as io.github.pipeworx-io/lob. Lob MCP, US address verification, bulk verification, and autocompletion (docs.lob.com). BYO-key… This page covers its npm package (@pipeworx/mcp-lob).
Is the Lob MCP server safe to use?
Lob scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Lob MCP server expose?
Lob exposes 3 tools: lob_verify_address, lob_verify_bulk, lob_autocomplete. Their descriptions and schemas cost roughly 625 tokens of context every time the server is loaded.
Is the Lob MCP server still maintained?
Lob is still listed as active in the MCP registry. We last reached this channel on 5 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 Lob MCP server under?
Lob declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.