# SpringVerify US MCP connector Connect SpringVerify US to Claude, ChatGPT, Cursor, or any MCP client through Elaichi so recruiters and HR can start background checks, look up candidates, and pull check reports, each signed in as themselves with every action logged. Source: https://elaichi.ai/connectors/springverifyus/ ## Facts | | | | --- | --- | | Application | SpringVerify US | | Category | BG Verification | | AI tools | 18 | | Authentication | Connects with an API key | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once SpringVerify US is connected - Show candidates added to SpringVerify US this week. - Pull the SpringVerify US candidates report for October. - Which SpringVerify US webhooks are failing to deliver? ## Connect SpringVerify US in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick SpringVerify US. 2. Optionally set Share with, then press Connect. 3. Paste a SpringVerify US API key. One person generates a token in SpringVerify US and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which SpringVerify US tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect SpringVerify US to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect SpringVerify US to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect SpringVerify US to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect SpringVerify US to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a SpringVerify US tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with SpringVerify US through Elaichi ### Start a background check from the offer call Recruiting. Give the agent the candidate's name, email, and package details and it creates the SpringVerify US candidate for you, so the check is under way before you hang up. ### Check where a candidate's screening stands HR. Ask what is happening with a specific candidate and get their current SpringVerify US record back in plain language, without opening another tab. ### Pull the candidates report before an audit Compliance. Request the SpringVerify US candidates report for a period and have the agent summarize who was screened and where each check landed. ### Keep company payment details current Finance. Update the card and payment information on your SpringVerify US company account, and confirm that an invite has been paid for, from the same chat you use for everything else. ### Set up a new hiring entity People operations. When a subsidiary starts hiring, create its SpringVerify US company, review the company profile, and list the companies already on the account. ### Get told the moment a check finishes HR operations. Set up a SpringVerify US webhook so completed checks reach your team automatically, then list webhooks and read their logs when something looks missed. ## Frequently asked questions ### How do I connect SpringVerify US to Claude? First, connect SpringVerify US in Elaichi by pasting in the API key from your SpringVerify US account. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate, and the whole thing takes a few minutes. ### Does SpringVerify US work with ChatGPT and Cursor as well as Claude? Yes. Once SpringVerify US is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect SpringVerify US once and every client uses it. ### What can an AI agent actually do with my SpringVerify US data? An agent connected to SpringVerify US through Elaichi can create a new candidate to start a background check, look up a single candidate's record, and pull the candidates report. It can also manage the company side, such as creating a company, reading the company profile, updating card and payment details, and paying for an invite. And it can set up, list, and remove webhooks and read their logs so your team hears when a check completes. ### Does connecting SpringVerify US give the AI access to every candidate on the account? No. Every call to SpringVerify US runs inside the access of the person who signed in, so the agent sees the candidates and companies that person can already see in SpringVerify US. Elaichi can narrow that access further, for example to read-only, but it can never widen it beyond what the person already has. ### Can my team share one SpringVerify US connection? Yes. One person connects SpringVerify US in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who created a candidate or pulled a report. ### Can I stop an agent from deleting or changing things in SpringVerify US? Yes. Restrictions in Elaichi work per action, so you can allow looking up candidates and pulling reports while blocking creating candidates, changing payment details, or deleting webhooks in SpringVerify US. A blocked action is never advertised to Claude, ChatGPT, or any other client, so no prompt can reach it. ### What happens to a SpringVerify US connection when someone leaves? Offboarding a person in Elaichi ends their access to SpringVerify US through every client at once. A shared SpringVerify US connection keeps working for everyone else on the team. If you want to remove SpringVerify US entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client at the same time. ## All 18 SpringVerify US tools Every tool below is callable through https://api.elaichi.ai/mcp once SpringVerify US is connected, subject to the toolbox it is in and the restrictions on the caller. - **Get single SpringVerify US candidate by ID** (Get). Get a SpringVerify US background verification case by employee/candidate ID. - **Create a SpringVerify US candidate** (Create). Create or invite a candidate for a SpringVerify US background verification case. - **SpringVerify US candidates report** (Action). Download the SpringVerify US PDF report for a background verification case through the proxy API. - **SpringVerify US auth login** (Action). SpringVerify US auth login endpoint. - **SpringVerify US auth signup** (Action). SpringVerify US auth signup endpoint. - **SpringVerify US auth verify** (Verify). Verify a SpringVerify US auth token/session. - **SpringVerify US auth forgot password** (Action). SpringVerify US auth forgot-password endpoint. - **SpringVerify US auth reset password** (Action). SpringVerify US auth reset-password endpoint. - **List all SpringVerify US webhooks** (List). List SpringVerify US webhook endpoints configured for the company. - **Create a SpringVerify US webhook** (Create). Create a SpringVerify US webhook endpoint. - **Delete a SpringVerify US webhook by ID** (Delete). Delete a SpringVerify US webhook endpoint. - **List all SpringVerify US webhook logs** (List). List SpringVerify US webhook delivery logs. - **Create a SpringVerify US company** (Create). Create a SpringVerify US company account. - **SpringVerify US company save cc** (Action). Create a Stripe card token used by SpringVerify US billing flows. - **SpringVerify US company save payment info** (Action). Save SpringVerify US payment information for the company. - **SpringVerify US company payment for invite** (Invite). Charge the company for a candidate invite/payment flow. - **List all SpringVerify US company** (List). List SpringVerify US company records visible to the authenticated user. - **SpringVerify US company profile** (Action). Get the SpringVerify US company/user profile.