About Cobalt
Cobalt is an MCP server for US business-registration, UCC lien, and TIN/EIN checks through Cobalt Intelligence. It supports KYB and underwriting workflows with state registration details, lien records in covered states, and IRS name-to-EIN matching.
Key features
- 01Search Secretary-of-State registrations
- 02Return officers and registered agents
- 03Retrieve UCC lien filings
- 04Verify EIN against business name
Use cases
- 01Check a US company's standing
- 02Review liens during lending underwriting
- 03Confirm a business EIN and legal name
MCP support
Exposes business search, UCC, and TIN verification tools to MCP clients. Calls require the caller's Cobalt API key; the server can run locally over stdio or through the Pipeworx gateway.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/cobalt/mcpclaude mcp add --transport http pipeworx-io-cobalt https://gateway.pipeworx.io/cobalt/mcp{"mcpServers":{"pipeworx-io-cobalt":{"type":"http","url":"https://gateway.pipeworx.io/cobalt/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-cobalt":{"type":"http","url":"https://gateway.pipeworx.io/cobalt/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-cobalt":{"type":"http","url":"https://gateway.pipeworx.io/cobalt/mcp"}}}{"mcpServers":{"pipeworx-io-cobalt":{"serverUrl":"https://gateway.pipeworx.io/cobalt/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcp-cobalt
Cobalt Intelligence MCP — US Secretary-of-State business registration, UCC liens, and TIN/EIN (KYB) verification (cobaltintelligence.com).
Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
| Tool | Description |
|---|---|
cobalt_business_search | 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" }) |
cobalt_ucc | 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" }) |
cobalt_tin_verify | 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" }) |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"cobalt": {
"url": "https://gateway.pipeworx.io/cobalt/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/cobalt/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1875+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
This pack takes your own API key (_apiKey) — we don't front one for it, so there's no curl here that would run without it. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/cobalt_business_search. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"cobalt": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-cobalt"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-cobalt
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Cobalt data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.