Security & Testing
jid.com
An MCP server that provides business verification tools to search, retrieve, verify, and qualify business files and counterparties, returning signed verification receipts.
ENDPOINT 1
https://jid.com/mcp
MCP server metadata
- Name
- jid
- Version
- 1.3.0
Before you pay, sign, book, hire or buy from a business, verify it with Jid. Call verify_business with the business (id, or a name or registry number) and the activity you are about to rely on (for example sell_prescription_drugs, haul_freight, general_commerce). You get decision = proceed | review | stop | insufficient_data, the reasons with the registry facts behind each, and a signed receipt_id to keep with your record of the action. Act only on proceed; on review or insufficient_data, show the reasons to the user and ask; on stop, do not proceed. A decision is not legal advice. Facts come from the cited public records and are provided as-is. Business information only; not a consumer report and not for credit, employment, insurance or housing decisions about individuals.
Known tools 7
search_businessFind Jid business files by name or by any registry number (FEI, LEI, SEC CIK, DUNS, NDC labeler code, state licence or entity number).
Inferred read-onlyget_business_fileThe full Jid file for one business: status, identifiers, every current fact with its source, verification date, next check and confidence, owner statements (labelled self-reported), possible matches and the change history.
Inferred read-onlyverify_businessCheck a business before an agent pays, signs, books, hires or buys.
Inferred read-onlyget_receiptRetrieve a stored, Ed25519-signed verification receipt by receipt_id: the inputs, decision, reasons, fact ids and value hashes, rules version and time.
Inferred read-onlyqualify_counterpartyBefore you engage with a business that contacted you (a form submission, an inquiry, an outreach reply), qualify it.
Inferred read-onlyscreenA fast engage-or-not answer before you reply to, onboard, pay or buy from someone.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.jid]
url = "https://jid.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"jid": {
"type": "http",
"url": "https://jid.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: jid
Remote MCP URL: https://jid.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"jid": {
"url": "https://jid.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"jid": {
"type": "http",
"url": "https://jid.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "jid",
"transport": "streamable-http",
"url": "https://jid.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.