78trust / 100

Jid: the trust API for AI agents

by jid.com in Security & trust

MCP serverPassing, checked 6 h ago

Verify a business before an agent pays, signs or buys: registry-cited decision and signed receipt.

https://jid.com/mcp

Last 30 days

All checks passedSome failedAll failedNot checked
Uptime
100%
Response time
301 ms typical, 351 ms slowest 5%
Last check
6 h ago
Next check
in 15 min

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "jid-the-trust-api-for-ai-agents": {
      "type": "http",
      "url": "https://jid.com/mcp"
    }
  }
}

7 tools

  • 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). Returns candidate files with status and match evidence.

  • get_business_file

    The Jid file for one business. Default (compact): status with its flags, identifiers, verified websites, the top facts with source and verification date, counts and the latest changes. With detail "full": every current fact with its source, verification date, next check and confi

  • verify_business

    Verifies a business against the registry facts Jid holds. Input: a Jid id (or a name or registry number) and, optionally, an activity, jurisdiction and amount. With an activity it returns a decision (proceed, review, stop or insufficient_data) with reasons: each names the require

  • get_receipt

    Returns a stored, Ed25519-signed verification receipt by receipt_id: the inputs, decision, reasons, fact ids and value hashes, rules version and time of the check. Free; does not count as a check.

  • qualify_counterparty

    Qualifies a business that made contact (a form submission, an inquiry, an outreach reply). Input: the sender's e-mail (or the company domain), the company name if given, and the context (form type, message, stated value, stated role). Jid checks the domain (MX, SPF, DMARC, regist

  • screen

    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 context (lead, inbound_email, partnership, vendor, purchase, marketplace_seller, agent_action), an optional amount (USD) and a policy (stric

  • 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 checks and a read (headline, recommendation engage | verify_first | do_not_engage, failed checks, lookup links): DMARC/SPF/DKIM as the receiving

Security scan

  • No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTime
6 h agoPassed200229 ms
15 h agoPassed200746 ms
24 h agoPassed200265 ms
32 h agoPassed200301 ms
41 h agoPassed200351 ms
2 days agoPassed200335 ms