Nlrb
NPM · @PIPEWORX/MCP-NLRB · 2 COMPONENTS
NLRB MCP — US National Labor Relations Board case search: unfair labor practice (C) charges and…
Available components
Last scanned (7 hours ago)
Scores higher than 69% of npm servers
Category Education and Research
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-nlrb). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 906 tokens (~302/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
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 →
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 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
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-nlrb@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-nlrb |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-nlrb/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679355867 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3c6ddd2a384737e58b7010dad294e5abe8c92a8ad2dc91ce7ea4bf3bb8fa9fc0296e525c783e0de0a44b20ec604703bb8e6f4de7626740444b28a0c16 |
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 →
nlrb_case ~210
Full docket for one US National Labor Relations Board case by case number (e.g. "10-CB-393760", "31-RC-357638"): the allegations charged under the National Labor Relations Act (such as "8(a)(3) Discharge" or "8(b)(1)(A) Duty of Fair Representation"), status, date filed, location, assigned region, the participants (charged party, charging party, employer, union and their legal representatives), the docket activity log, and for representation cases the election tally — eligible voters, ballots counted, votes for and against the union. Answers "what is Starbucks charged with in this NLRB case", "how did the union election in case 31-RC-357638 turn out".
| Name | Type | Req | Description |
|---|---|---|---|
| case_number | string | yes | NLRB case number in region-type-serial form, e.g. "10-CB-393760" or "31-rc-357638" (case-insensitive; surrounding whitespace ignored). |
No output schema declared.
No examples provided.
nlrb_recent_filings ~256
Newest US National Labor Relations Board case filings across the country over a recent window — the labor-dispute equivalent of a new-filings feed. Returns case number, name, date filed, status, city and region, newest first, with the total filed in the window. Answers "what NLRB charges were filed this week", "recent union election petitions", "how much labor board activity was there in the last 30 days". Filter by case type (C for unfair labor practice charges, R for election petitions) and NLRB region.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | – | Restrict to "C" (unfair labor practice charges) or "R" (representation/election petitions). Omit for both. "ULP" is accepted as a synonym for C. |
| days | number|string | – | How many days back from today to include (1-365, default 7). |
| limit | number|string | – | Max cases to return (1-50, default 25). |
| region | string | – | NLRB region number, e.g. "10", "29". |
| status | string | – | Restrict to "Open", "Closed", or "Open - Blocked". |
No output schema declared.
No examples provided.
nlrb_search ~387
Search US National Labor Relations Board cases by employer, union, or case number — unfair labor practice charges (C cases: CA against an employer, CB against a union) and union representation/election petitions (R cases: RC, RD, RM). Returns case number, case name, date filed, open/closed status, city and NLRB region for each match, plus the total number of matching cases. Answers "is Starbucks facing an NLRB charge", "labor board complaints against Amazon", "union election petitions at Trader Joe's", "what NLRB cases involve Teamsters Local 705". Filter by case type, status, date filed, and NLRB region.
| Name | Type | Req | Description |
|---|---|---|---|
| case_type | string | – | Restrict to "C" (unfair labor practice charges) or "R" (representation/election petitions). Omit for both. |
| filed_before | string | – | Only cases filed on or before this date (YYYY-MM-DD). |
| filed_since | string | – | Only cases filed on or after this date (YYYY-MM-DD). |
| limit | number|string | – | Max cases to return (1-50, default 10). |
| page | number|string | – | Zero-based page of results, for paging past the first `limit` cases. |
| query | string | yes | Employer name, union name, or a full case number such as "10-CB-393760". Matched full-text against case names; case-insensitive. |
| region | string | – | NLRB region number, e.g. "10" (Atlanta), "29" (Brooklyn). Two digits; single digits are zero-padded. |
| sort | string | – | "newest" (default), "oldest", or "relevance". |
| status | string | – | Restrict to "Open", "Closed", or "Open - Blocked". |
No output schema declared.
No examples provided.
How do I install the Nlrb MCP server?
Nlrb runs locally as an npm package, launched with npx -y @pipeworx/mcp-nlrb. 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-nlrb
claude mcp add pipeworx-io-nlrb -- npx -y @pipeworx/mcp-nlrb
What is the Nlrb MCP server?
Nlrb is an MCP server listed in the public MCP registry as io.github.pipeworx-io/nlrb. NLRB MCP, US National Labor Relations Board case search: unfair labor practice (C) charges and… This page covers its npm package (@pipeworx/mcp-nlrb).
Is the Nlrb MCP server safe to use?
Nlrb scores 81 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 Nlrb MCP server expose?
Nlrb exposes 3 tools: nlrb_search, nlrb_case, nlrb_recent_filings. Their descriptions and schemas cost roughly 853 tokens of context every time the server is loaded.
Is the Nlrb MCP server still maintained?
Nlrb 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 Nlrb MCP server under?
Nlrb 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 Nlrb MCP server?
VerifyMCP ran 16 checks on Nlrb, 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.