Back to Browse

Argorant MCP Server

Developer ToolsUse Caution4.8MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

Verified B2B contact data: size a market free, reveal or export when the segment is right.

About

Verified B2B contact data: size a market free, reveal or export when the segment is right.

Remote endpoints: streamable-http: https://mcp.argorant.com/mcp

Security Report

4.8
Use Caution4.8High Risk

Argorant MCP is a well-architected remote OAuth 2.1-protected server with proper authentication and authorization controls. The code demonstrates strong security practices including PKCE enforcement, single-use authorization codes, refresh token rotation, and scoped access to sensitive operations. Minor code quality observations exist but do not materially impact security posture given the server's architecture and intended use case. Supply chain analysis found 10 known vulnerabilities in dependencies (0 critical, 7 high severity).

4 files analyzed · 15 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

database

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

Argorant MCP

Verified B2B contact data for AI agents. Search, count, preview, reveal, export, and build saved lists across 600M+ business contacts — directly from Claude, ChatGPT, Cursor, and any MCP client.

This is a hosted remote connector — no install, no API key paste. Clients connect to the endpoint and authenticate via OAuth. A standalone CLI also exists (npx argorant) for terminal/script use.

Connect

Claude (claude.ai / Desktop): Settings → Connectors → Add custom connector → URL https://mcp.argorant.com/mcp → complete the OAuth login.

ChatGPT (Developer Mode): Settings → Apps & Connectors → Advanced → enable Developer Mode → Connectors → Create → URL https://mcp.argorant.com/mcp. The search + fetch tools make it usable as a Deep Research connector.

Cursor / other MCP clients: add the remote server from mcp.json:

{
  "mcpServers": {
    "argorant": {
      "url": "https://mcp.argorant.com/mcp"
    }
  }
}

Tools

Free (no credits, masked/aggregate only):

ToolWhat it does
search / fetchChatGPT-style coverage search + safe summary (masked previews, counts)
argorant_accountConnected account, scopes, limits
argorant_count_peopleCount matching contacts by role, seniority, dept, industry, geo
argorant_preview_peopleMasked preview rows (initials, role, company, location)

Consume credits (require OAuth scope + permission; verification is live at this step and only valid/deliverable contacts are billed):

ToolWhat it does
argorant_reveal_peopleReveal real emails, phones, profile URLs for a small set
argorant_create_export / argorant_export_listAsync CSV export (large lists)
argorant_create_list / argorant_list_statusBuild & inspect reusable saved lists
argorant_export_status / argorant_export_batch_status / argorant_download_export_previewTrack & fetch exports

Tools are annotated with read-only vs. action hints. Reveal/export/list actions only run after OAuth, scope, permission, quota, and plan checks; without credits they are blocked by design.

Data & privacy posture

  • OAuth + account-scoped. Unauthenticated requests to /mcp return 401 with WWW-Authenticate pointing at protected-resource metadata.
  • Masked by default. search/fetch/preview never return raw emails, phones, or profile URLs — only aggregate coverage and masked rows. Raw contact details require the scoped reveal/export tools and consume credits.
  • Verification is live. Emails are verified at reveal/export time; you are billed only for deliverable contacts. Raw verification status is never exposed as a queryable field.
  • Hosts are separated: argorant.com (marketing/docs), app.argorant.com (signed-in app), mcp.argorant.com (remote MCP + OAuth).

OAuth discovery

https://mcp.argorant.com/.well-known/oauth-protected-resource
https://mcp.argorant.com/.well-known/oauth-authorization-server

Dynamic Client Registration is supported at /register (grant types: authorization_code, refresh_token).

Documentation

Registry metadata

  • mcp.json — Open Plugins / Cursor remote-server declaration.
  • server.json — official MCP Registry entry (io.github.argorant/argorant-mcp, remote streamable-http).

Reviews

No reviews yet

Be the first to review this server!