RelPro MCP Connector

Quality leads. Actionable sales intelligence. RelPro company and people data, where you work.

Overview

The RelPro MCP Connector gives AI applications secure, read-only access to RelPro's B2B company and people intelligence — firmographics, executive and person profiles, and premium signals such as loans, UCC filings, Form 5500, and government contracts. It is intended for sales, research, and prospecting workflows inside approved AI apps (e.g., Claude).

Who can use it

Access is limited to users of existing RelPro client organizations. There is no public or self-service sign-up. Users are provisioned by RelPro and assigned to an entitled group; group membership determines which tools and data each user can access.

Capabilities

Tool	Description
company_search	Search companies by name, location, headcount, revenue, website, or industry.
company_premium_search	Company search plus premium filters (loan type, lender, filing dates, UCC, Form 5500, government contracts).
company_profile	Retrieve a full company profile.
company_premium_profile	Retrieve premium company data by section (loans, UCC, Form 5500, government contracts, investment data).
company_executives_search	Find senior executives and board members for given companies.
person_search	Search for people by name, title, employer, or location; reverse lookup by email or phone.
person_profile	Retrieve a full person profile.

The connector is read-only. It does not create, modify, or delete data in any user system, and it does not send email or take actions on a user's behalf.

Security & authentication

• OAuth 2.1 (authorization code flow). The connector is an OAuth resource server; access tokens are issued and signed by the RelPro Identity Provider (idp.relpro.com). No API keys are used.
• Token validation — every request's token is verified against the IdP's signing keys, with standard claim checks (expiry, issuer, subject, client).
• Approved apps only — the calling AI app must be registered in RelPro's allow-list; unknown clients are rejected.
• SSO (optional) — approved apps can be mapped to an enterprise SSO login. When configured for a client, the OAuth authorize flow routes the user through their organization's SSO provider before the IdP issues a token. Clients without an SSO mapping use the standard IdP login unchanged.
• Group-based authorization — per-group entitlements gate every tool, resource, and prompt. Requests outside a group's entitlements are denied (403).
• IP restrictions — certain groups require connecting from approved IP ranges (CIDR allow-lists).
• Transport — Streamable HTTP over TLS.

Data handling

• The connector returns RelPro-licensed business data to the requesting user; it does not ingest or store the user's own files or messages.
• Chargeable profile views are recorded to a billing audit log for usage accounting.
• Request activity is logged for operational and security monitoring.

Permissions requested

Read-only access to RelPro company and people data, scoped to the user's entitled group. No write, delete, or messaging permissions.

Getting access

Contact RelPro or your RelPro account representative to be provisioned. Once your organization and AI app are approved, connect through your AI app's connector settings and authenticate with your RelPro credentials.

Support

For access requests, technical questions, or issues with the connector, contact RelPro at support@relpro.com. For details on how RelPro handles data, see our privacy policy.