Sos Entities
NPM · @PIPEWORX/MCP-SOS-ENTITIES · 2 COMPONENTS
sos-entities — state business-entity registries in one normalised shape (fleet #2867).
Available components
Last scanned (15 hours ago)
Scores higher than 72% of npm servers
Category CRM and Sales
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-sos-entities). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 709 tokens (~236/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.
- 5 Nov 26 +3
- Tool safety: pass → unverified ▼ 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
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified 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-sos-entities@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-sos-entities |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sos-entities/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692355136 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0df244f5c009cc6179c838d939a9b26cbdaf37c01ea9aa3a49b38f008c882873e5ddb285479abff3d6dde11b3069e6e35b007045cb53588d7b738a292 |
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 →
sos_entity ~181
Full registry record for one business entity by state and entity number: legal name, type, status, formation date, principal address, registered agent, and officers/directors/managers as [{name, role}] where the state publishes them (FL up to six officers, CT principals, PA parties, NY chairman/CEO, OR authorized representative; CO and TX publish none). Individuals' addresses are never included. Get entity_number from sos_search or sos_new_entities.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_number | string | yes | The state's entity number: FL document number (e.g. "L26000507120"), NY DOS ID, CO entity ID, OR registry number, CT business ALEI/account number, TX taxpayer number or SOS file number, PA filing num… |
| state | string | yes | Two-letter state: FL, NY, CO, OR, CT, TX, PA. |
No output schema declared.
No examples provided.
sos_new_entities ~230
Business entities newly formed in one state since a date — new LLCs, corporations and partnerships, newest first (formation dates from `since` through today; delayed-effective future dates are left out), with entity number, name, type, formation date, principal address and source, plus data_as_of. Optional name and entity-type filters. Deterministic order (formation date, then entity number). Florida reaches back 70 days; the other states any date. Use for new-business lead lists and formation monitoring.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_type | string | – | Only types containing this text, e.g. "limited liability" or "LLC" or "corporation". |
| limit | number | – | Max results (default 100, max 1000). |
| name_query | string | – | Only names containing this text, e.g. "dental". |
| since | string | yes | Formation date on or after, YYYY-MM-DD, e.g. "2026-10-01". |
| state | string | yes | Two-letter state: FL, NY, CO, OR, CT, TX, PA. |
No output schema declared.
No examples provided.
sos_search ~243
Search US state business-entity registries (Secretary of State) by company name — FL, NY, CO, OR, CT, PA, and TX (Comptroller franchise-tax registrations). Returns each match with entity number, legal name, entity type, status, formation date, principal address, registered agent (an agent's address only when the agent is a business), and the state source, plus data_as_of per state. Name matching is "starts with"; if nothing starts with the name it retries as "contains". Omit state to search all seven at once. Use the entity_number with sos_entity for officers. Sourced from each state's official registry publications.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results per state (default 10, max 50). |
| name | string | yes | Company name or its beginning, e.g. "Publix Super Markets" or "Coors". |
| state | string | – | Two-letter state. One of FL, NY, CO, OR, CT, TX, PA. Omit to search all. |
| status | string | – | Filter by status (default any). NY, OR and PA publish active entities only. |
No output schema declared.
No examples provided.
How do I install the Sos Entities MCP server?
Sos Entities runs locally as an npm package, launched with npx -y @pipeworx/mcp-sos-entities. 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-sos-entities
claude mcp add pipeworx-io-sos-entities -- npx -y @pipeworx/mcp-sos-entities
What is the Sos Entities MCP server?
Sos Entities is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sos-entities. sos-entities, state business-entity registries in one normalised shape (fleet #2867). This page covers its npm package (@pipeworx/mcp-sos-entities).
Is the Sos Entities MCP server safe to use?
Sos Entities 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 Sos Entities MCP server expose?
Sos Entities exposes 3 tools: sos_search, sos_entity, sos_new_entities. Their descriptions and schemas cost roughly 654 tokens of context every time the server is loaded.
Is the Sos Entities MCP server still maintained?
Sos Entities 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 Sos Entities MCP server under?
Sos Entities 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 Sos Entities MCP server?
VerifyMCP ran 16 checks on Sos Entities, 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.