Categories › AI & Agents › Multi-agent, orchestration & workflows
Verify a business before an agent pays, signs or buys: registry-cited decision and signed receipt.
Remote server: your requests and data go to jid.com. Claude Code: claude mcp add --transport http jid-the-trust-api-for-ai-agents https://jid.com/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
search_business — Finds Jid business files by name or by any registry number (FEI, LEI, SEC CIK, DUNS, NDC labeler code, state licence or entity number, Frencget_business_file — The Jid file for one business. Default (compact): status with its flags, identifiers, verified websites, the top facts with source and verifverify_business — Verifies a business against the registry facts Jid holds. Input: a Jid id (or a name or registry number) and, optionally, an activity, jurisget_receipt — Returns a stored, Ed25519-signed verification receipt by receipt_id: the inputs, decision, reasons, fact ids and value hashes, rules versionqualify_counterparty — Qualifies a business that made contact (a form submission, an inquiry, an outreach reply). Input: the sender's e-mail (or the company domainscreen — Screens a lead, sender, vendor or website and returns an engage-or-not answer. Input: any of domain, url, email, phone or company_name, the check_email — Checks whether an e-mail is from who it claims. Input: the raw headers of a message (as shown by Show original or View source). Returns checNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.