MCP setup guide

1 · Get your API key

Two of the three tools need a key. It is free, takes about thirty seconds, and needs no credit card.

Step 1

Enter your email on the home page.

Step 2

Open the verification link we email you. Your key is shown once on that page — copy it somewhere safe before closing the tab.

Your key starts with ync_. Treat it like a password. If you lose it, sign up again or contact us — we cannot show it to you a second time.

2 · Add to Claude Desktop

The quickest way, if you have Claude Desktop installed:

Add to Claude Desktop

That opens Claude Desktop and adds the server in one step. Paste your API key when it asks, and you are done.

Or add it by hand

Open Claude Desktop.
Go to Settings → Developer → Edit Config. A file called claude_desktop_config.json opens.
Paste the block below into it. If the file already has an mcpServers section, add just the "yin-ai-certification" part inside it.
Replace your-ync-api-key-here with the key from step 1.
Save the file and restart Claude Desktop.

{
  "mcpServers": {
    "yin-ai-certification": {
      "type": "url",
      "url": "https://certification.yintechnologies.com/mcp",
      "headers": {
        "Authorization": "Bearer your-ync-api-key-here"
      }
    }
  }
}

3 · Add to Claude on iPhone, iPad, and Android

You do not set this up on the phone itself. Connectors belong to your Claude account, so you add ours once in a web browser and it then appears in the Claude app on every device you are signed in to.

On any computer or phone browser, go to claude.ai/settings/connectors and sign in.
Tap Add custom connector.
Name it YIN-AI CERTIFICATION and paste this address:
https://certification.yintechnologies.com/mcp
Paste your API key when it asks for authentication.
Open the Claude app on your phone. Fully close and reopen it if it was already running.
Start a chat, tap the attachments / tools control, and switch YIN-AI CERTIFICATION on.

Custom connectors are a paid-plan feature on Claude (Pro, Max, Team, or Enterprise). If you do not see Add custom connector, your plan does not include it yet — the same three tools are still available through Claude Desktop, Cursor, or any other client below.

4 · Add to Cursor

Open Cursor.
Go to Settings → MCP → Add new MCP server.
Choose the URL (or remote) server type.
Name it yin-ai-certification and use this address:
https://certification.yintechnologies.com/mcp
Add a header called Authorization with the value Bearer followed by your key.
Save, then reload Cursor.

Cursor also accepts the same JSON as Claude Desktop if you prefer editing the config file directly.

5 · Add to any other MCP client

Every MCP client asks for the same three things. Wherever your app keeps its MCP or connector settings, give it:

Type — remote server, sometimes called URL, HTTP, streamable HTTP, or custom connector. Not command or stdio: there is nothing to install.
Address — https://certification.yintechnologies.com/mcp
Authentication — a header named Authorization whose value is the word Bearer, a space, then your API key.

If your app wants a config file instead of a form, this is the block nearly all of them accept:

{
  "mcpServers": {
    "yin-ai-certification": {
      "type": "url",
      "url": "https://certification.yintechnologies.com/mcp",
      "headers": {
        "Authorization": "Bearer your-ync-api-key-here"
      }
    }
  }
}

Some tools name the same field differently — servers instead of mcpServers, or serverUrl instead of url. The address and the Authorization header never change. Restart the app afterwards; MCP settings are read at startup.

6 · The three tools

Once connected, just ask in plain language — your assistant picks the right tool. The examples show what it sends behind the scenes.

yin_cert_certify

Issues a signed certificate for a decision your AI made. Needs your API key.

Say: “Certify this loan decision.”

{
  "query": "Should we approve loan application #4471?",
  "answer": "Approve, with manual review of the collateral valuation.",
  "context": { "certification_profile": "regulated" }
}

yin_cert_verify

Checks a certificate's signatures on your own machine. No API key, no network call.

Say: “Verify this certificate.”

{
  "certificate": { "...paste the certificate JSON here..." }
}

yin_cert_get_schema

Fetches the exact field list for a module's certificate. No API key needed.

Say: “Show me the vision certificate schema.”

{
  "module": "m2_vision"
}

Where it works

Our server is a standard remote MCP server, so it works in any client that speaks MCP. These are the ones people ask about most, and how each one connects:

Claude — web, desktop, iOS, AndroidOne custom connector on your account covers all four. See steps 2 and 3 above.
Claude CodeRun claude mcp add --transport http yin-ai-certification https://certification.yintechnologies.com/mcp --header "Authorization: Bearer your-ync-api-key-here"
ChatGPT — web and appAdd as a connector in settings, where your plan enables custom connectors. Same address and header.
Gemini — web and appAdd as an extension or MCP server wherever your Gemini build exposes MCP settings. Same address and header.
Copilot and GitHub CopilotAdd an MCP server in your editor's Copilot settings, or in the repository's MCP configuration for the coding agent.
CursorSee step 4 above.
Windsurf · Cline · ContinueAll three take the JSON block from step 5 in their MCP settings.
Any MCP-compatible clientRemote server, address https://certification.yintechnologies.com/mcp, Authorization: Bearer header. Nothing to install.

Client menus move between releases, and not every plan exposes custom connectors. If the wording on your screen does not match ours, look for anything called MCP, Connectors, Integrations, or Tools — the three values in step 5 are all you ever need to enter.

What MCP is