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.

Cobalt

NPM · @PIPEWORX/MCP-COBALT · 2 COMPONENTS

Cobalt Intelligence MCP — US Secretary-of-State business registration, UCC liens, and TIN/EIN…

+3 this week 83 Trust /100

Last scanned (14 hours ago)

Scores higher than 76% of npm servers

Category Finance and Payments

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-cobalt). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 559 tokens (~186/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
What we tested

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 →

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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.07 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 80

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-cobalt@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-cobalt
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-cobalt/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612138465
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ccdfacad2c8f1c04215650401594242eaff8ee597b9ca6eb65ac58fa73ca1e7fe9545fb9de1082241c078eda8be3afbe6aff2f3c2f399b526c33a8301

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 · 3 exposed · ~508 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
cobalt_business_search ~208

Look up a US company's Secretary-of-State registration & status — returns entity name, standing/status, SOS entity id, entity type, filing date, officers, registered agent, and address. Live from the state SOS portal (all 50 states + DC). Example: cobalt_business_search({ searchQuery: "Cobalt Intelligence", state: "UT", _apiKey: "your-key" })

NameTypeReqDescription
_apiKeystringyesCobalt Intelligence API key (20 free lookups at cobaltintelligence.com).
liveDataboolean–Optional. Force a fresh live pull from the state portal (slower, may return a retryId) instead of allowing recent cached data.
searchQuerystringyesCompany legal name (e.g. "Apple Inc") or a Secretary-of-State entity id (sosId) to look up.
statestringyesTwo-letter US state code, e.g. "CA", "NY", "TX", "DE".

No output schema declared.

No examples provided.

cobalt_tin_verify ~150

Verify a business TIN/EIN against IRS records — confirms a 9-digit EIN matches the legal business name on file with the IRS. Returns match status, IRS code/reason and last-checked date. Synchronous (<5s). Example: cobalt_tin_verify({ tin: "123456789", businessName: "Acme Corp", _apiKey: "your-key" })

NameTypeReqDescription
_apiKeystringyesCobalt Intelligence API key.
businessNamestringyesThe legal business name exactly as filed with the IRS.
tinstringyesThe 9-digit EIN/TIN, digits only (no dashes), e.g. "123456789".

No output schema declared.

No examples provided.

cobalt_ucc ~150

UCC liens for a business — returns Uniform Commercial Code filings (secured party, filing date, filing number, status) recorded against a company. Covers 11 states. Use to detect existing liens on collateral for lending/underwriting. Example: cobalt_ucc({ searchQuery: "Acme LLC", state: "TX", _apiKey: "your-key" })

NameTypeReqDescription
_apiKeystringyesCobalt Intelligence API key.
searchQuerystringyesCompany legal name or Secretary-of-State entity id (sosId).
statestringyesTwo-letter US state code, e.g. "TX", "CA". UCC coverage is limited to 11 states.

No output schema declared.

No examples provided.

Install

How do I install the Cobalt MCP server?

Cobalt runs locally as an npm package, launched with npx -y @pipeworx/mcp-cobalt. 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-cobalt

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

What is the Cobalt MCP server?

Cobalt is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cobalt. Cobalt Intelligence MCP, US Secretary-of-State business registration, UCC liens, and TIN/EIN… This page covers its npm package (@pipeworx/mcp-cobalt).

Is the Cobalt MCP server safe to use?

Cobalt scores 83 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 Cobalt MCP server expose?

Cobalt exposes 3 tools: cobalt_business_search, cobalt_ucc, cobalt_tin_verify. Their descriptions and schemas cost roughly 508 tokens of context every time the server is loaded.

Is the Cobalt MCP server still maintained?

Cobalt 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 Cobalt MCP server under?

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

VerifyMCP ran 16 checks on Cobalt, 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.