VerifyRef

com.verifyrefPublished by verifyref.comOfficial publisherv1.0.0Updated Oct 25, 2026

AI agent recruiting: talent pool match, reference checks, credit packs via Stripe MPP

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

VerifyRef is a recruiting MCP server that lets an assistant match talent-pool candidates, run reference checks and buy credit packs.

What you can do
Search and match candidates in a talent pool. Run reference and background check workflows. Buy credit packs through Stripe. Connect to your team account with an API key.
When to use it
Use it when an assistant should help search a talent pool, run reference or background checks, or buy credit packs as part of a recruiting workflow. It is not intended for non-recruiting tasks.
Requirements
A VerifyRef API key supplied as the VERIFYREF_API_KEY environment variable, either a test or live key obtained from the team API page. Connects to a remote endpoint or runs locally from an npm package over stdio.
Before you install
Requires an API key (VERIFYREF_API_KEY) that should be kept private. It involves paid credit-pack purchases through Stripe, which can incur real charges. Check and talent-pool actions may write or change team data and send candidate and check data to a third-party service.

Installation

In SourceWeft

  1. Open VerifyRef in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.verifyref%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "verifyref": {
      "type": "http",
      "url": "https://verifyref.com/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.