← All servers

Jid: the trust API for AI agents

warnings

jid.com

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

https://jid.com/mcpWebsiteNo authMCP 2025-11-25v1.3.0last checked 6 Oct 2026spoke MCP on 1 of 1 check (30 days)initialize in 367 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http jid-the-trust-api-for-ai-agents https://jid.com/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://jid.com/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://jid.com/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

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

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

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

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 6 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 7 tools listable
Credentials demanded in prose	✕qualify_counterparty These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

1 of the 7 tools listed anonymously say in their own descriptions that they need an account or a key (qualify_counterparty), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

check_emailget_business_fileget_receiptqualify_counterpartyscreensearch_businessverify_business

Contract history

6 Oct 2026v1.3.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/jid-the-trust-api-for-ai-agents/badge.svg)](https://mcpi.app/servers/jid-the-trust-api-for-ai-agents)