Identity resolution MCP server for phone/email lookups across 31+ services. Global + India coverage.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Bearer token for authentication. Get your API key at https://portal.outris.com
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Assess the fraud risk of an Indian mobile number. Returns a composite risk profile: SIM age / age-on-network, number revocation status, SIM-swap / port signals, and digital & financial exposure. Set detailed=true for the full signal breakdown. Best for: onboarding risk checks, is-this-number-risky. Cost: 3 credits
Indian mobile number (10-digit, with or without +91).
Include the full raw signal breakdown. Default false.
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Assess the fraud risk of an Indian mobile number. Returns a composite risk profile: SIM age / age-on-network, number revocation status, SIM-swap / port signals, and digital & financial exposure. Set detailed=true for the full signal breakdown. Best for: onboarding risk checks, is-this-number-risky. Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Indian mobile number (10-digit, with or without +91). |
| detailed | boolean | Include the full raw signal breakdown. Default false. |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
},
"detailed": {
"type": "boolean",
"description": "Include the full raw signal breakdown. Default false."
}
}
}Aggregate a phone number's caller-identity across multiple consumer caller-ID apps. Returns saved-as names, associated emails, and social handles. Requires DPDPA consent.
| Argument | Type | Description |
|---|---|---|
| phone* | string | Indian mobile number (10-digit, with or without +91). |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
}
}
}**What it does:** Checks if a phone number has been used for any digital commerce activity (ecommerce, travel, quick-commerce). **Input:** Phone number (Indian numbers only, add ISD code infront). **Returns:** Boolean flags for overall commerce types, activity timeline, and demographics if available. **Best for:** Assessing if a phone number belongs to a real, active consumer vs. a throwaway number. Cost: 1 credit
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number (with or without country code) |
| include_demographics | boolean | Include age/gender estimation (default: true) |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number (with or without country code)"
},
"include_demographics": {
"type": "boolean",
"description": "Include age/gender estimation (default: true)"
}
}
}Check the status/result of an async job by job_id (e.g. from due_diligence_person_start). Free to poll — wait ~10s between polls. Cost: 0 credits
| Argument | Type | Description |
|---|---|---|
| job_id* | string | The job_id returned by an async tool. |
{
"type": "object",
"required": [
"job_id"
],
"properties": {
"job_id": {
"type": "string",
"description": "The job_id returned by an async tool."
}
}
}**What it does:** Checks if a phone number is registered on major global platforms (Amazon, Instagram, Snapchat). **Input:** Phone number (with or without country code). **Returns:** Registration status (true/false) for each specific platform. **Best for:** Digital footprint analysis, verifying if a number is "real" and active on social/shopping apps. Cost: 1 credit
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number (with or without country code) |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number (with or without country code)"
}
}
}Start a full due-diligence / background check on a PERSON, anchored on their mobile number (optionally add name, PAN, DOB, email, city). Covers PEP, sanctions, enforcement, cybercrime, breaches, directorships, and adverse media. PREMIUM and ASYNC (~40-70s): it returns a job_id — poll check_job until status is 'complete'. Requires consent: ask the user to open the consent link in portal.outris.com/mcp and pass the consent_token. Cost: 5 credits
| Argument | Type | Description |
|---|---|---|
| dob | string | Optional date of birth (disambiguates common names). |
| pan | string | Optional PAN — strongest key for PEP/enforcement. |
| city | string | Optional city (adverse-media disambiguation). |
| name | string | Optional subject full name. |
| string | Optional subject email. | |
| phone* | string | Indian mobile number (10-digit, with or without +91). |
| consent | string | Deprecated legacy consent flag ('Y'); migration only. |
| consent_token | string | Server-issued consent token (preferred). |
Request the official MCA View-Public-Documents (VPD) pack for an unlisted or private Indian company. Delivers official balance sheets (AOC-4), annual returns (MGT-7), P&L, charges, and incorporation filings. Fulfilment is asynchronous and operator-assisted. You can optionally pass a callback_url to be notified via webhook when filings are ready. Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| cin* | string | 21-character Corporate Identification Number (CIN), LLPIN, or FCRN. |
| callback_url | string | Optional HTTPS URL to receive webhook push when documents are ready. |
{
"type": "object",
"required": [
"cin"
],
"properties": {
"cin": {
"type": "string",
"description": "21-character Corporate Identification Number (CIN), LLPIN, or FCRN."
},
"callback_url": {
"type": "string",
"description": "Optional HTTPS URL to receive webhook push when documents are ready."
}
}
}Skip-trace an Indian mobile number for the person's ALTERNATE phone numbers and current, geocoded addresses. Requires the end user's consent: ask the user to open the consent link in portal.outris.com/mcp and pass the consent_token they receive. Best for: debt collection, locating a person. Never fabricate consent. Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Indian mobile number (10-digit, with or without +91). |
| consent | string | Deprecated legacy consent flag ('Y'); accepted only during migration. |
| consent_token | string | Server-issued consent token from portal.outris.com/mcp (preferred). |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
},
"consent": {
"type": "string",
"description": "Deprecated legacy consent flag ('Y'); accepted only during migration."
},
"consent_token": {
"type": "string",
"description": "Server-issued consent token from portal.outris.com/mcp (preferred)."
}
}
}**What it does:** Finds physical addresses associated with a phone number. **Input:** Phone number. **Returns:** List of addresses with metadata (e.g., "shipping", "billing", "home") and dates. **Best for:** Fraud investigation, delivery verification, and location analysis. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number"
}
}
}Get other phone numbers belonging to the same person. Returns: List of alternate phone numbers linked through shared identities (same name, email, or address). Use when: User wants to find all phones associated with a person. Example queries: - "What other phones does this person have?" - "Find alternate numbers for 9876543210" - "Are there other phones linked to this one?" Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number"
}
}
}**What it does:** Finds email addresses linked to a phone number. **Input:** Phone number. **Returns:** List of email addresses with confidence scores. **Best for:** Digital footprint analysis, finding contact details, or cross-referencing identities. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number"
}
}
}**What it does:** Comprehensive identity report. Fetches names, emails, addresses, metadata, and risk scores in one go . **Input:** Phone number. **Returns:** Complete JSON profile containing all linked entities. **Best for:** Deep investigations where you need the "full picture" immediately. Understand if similar names, addresses appear, then that gives more confidence Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number"
}
}
}**What it does:** identifying the owner name of a phone number. **Input:** Phone number (with or without country code). **Returns:** List of full names linked to this phone with confidence scores. **Best for:** KYC verification, caller ID, finding out "who called me". Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| phone* | string | Phone number |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Phone number"
}
}
}Trace the person behind an email address — linked names, phone numbers, addresses, and known data breaches. Best for: reverse email lookup, digital footprint, cross-referencing an identity. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| email* | string | Email address to investigate. |
{
"type": "object",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"description": "Email address to investigate."
}
}
}Investigate an Indian mobile number and return who is behind it — name(s), addresses, alternate phone numbers, and social/digital footprint. Use depth='basic' for a fast identity bundle (default) or depth='full' for a comprehensive multi-source investigation (slower). Best for: 'who owns this number', caller ID, KYC, skip-tracing. Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| depth | string | basic = fast identity bundle (default); full = comprehensive investigation (slower). |
| phone* | string | Indian mobile number (10-digit, with or without +91). |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"depth": {
"enum": [
"basic",
"full"
],
"type": "string",
"description": "basic = fast identity bundle (default); full = comprehensive investigation (slower)."
},
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
}
}
}Ultimate Beneficial Ownership (UBO) screen. Unravels multi-tier holding company trees to identify natural persons holding >=10% economic interest or ultimate managerial control under RBI/PMLA guidelines. Returns ownership paths, percentages, and control tiers. Cost: 5 credits
| Argument | Type | Description |
|---|---|---|
| identifier* | string | CIN, PAN, or registered Company Name. |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string",
"description": "CIN, PAN, or registered Company Name."
}
}
}Look up GST registration details for a business by its GSTIN (15-character GST number). Returns legal/trade name, status, registration type, and address. Best for: GST verification, vendor onboarding. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| gstin* | string | 15-character GSTIN. |
{
"type": "object",
"required": [
"gstin"
],
"properties": {
"gstin": {
"type": "string",
"description": "15-character GSTIN."
}
}
}Look up an Indian vehicle by its RC (registration) number — returns make/model, registration details, and the registered owner. Best for: vehicle verification, RC checks. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| rc_number* | string | Vehicle registration number (e.g. MH12AB1234). |
{
"type": "object",
"required": [
"rc_number"
],
"properties": {
"rc_number": {
"type": "string",
"description": "Vehicle registration number (e.g. MH12AB1234)."
}
}
}Resolve an Indian company from its NAME and return its CIN (Corporate Identification Number) plus any GSTIN / MSME registrations discovered along the way. Best for: 'is this a real company', KYB entry point, finding a CIN from a company name. Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| company_name* | string | Company name to resolve. |
{
"type": "object",
"required": [
"company_name"
],
"properties": {
"company_name": {
"type": "string",
"description": "Company name to resolve."
}
}
}Comprehensive phone intelligence bundle tailored for debt-collection and skip-trace operations. Amalgamates multiple sources to provide a unified asset, contact, and lifestyle profile.
| Argument | Type | Description |
|---|---|---|
| phone* | string | Indian mobile number (10-digit, with or without +91). |
{
"type": "object",
"required": [
"phone"
],
"properties": {
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
}
}
}Deep digital footprint analysis mapping an entity's online presence, associated web links, breaches, and public risk indicators.
| Argument | Type | Description |
|---|---|---|
| query* | string | Email, phone, or name to analyze |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Email, phone, or name to analyze"
}
}
}Law Enforcement Intelligence (LEI) endpoint. Highly-privileged macro-orchestrator combining collections data, prefill identity, and caller ID aggregation for a comprehensive subject profile.
| Argument | Type | Description |
|---|---|---|
| phone* | string | Indian mobile number (10-digit, with or without +91). |
| reason* | string | Justification or case ID for the LEI inquiry |
{
"type": "object",
"required": [
"phone",
"reason"
],
"properties": {
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
},
"reason": {
"type": "string",
"description": "Justification or case ID for the LEI inquiry"
}
}
}Query the unified enforcement corpus (58 regulatory sources, 1.3M+ records) by identifier. Searches for legal actions, severe compliance failures, or negative regulatory actions against an entity.
| Argument | Type | Description |
|---|---|---|
| identifier* | string | Any valid business identifier: CIN, PAN, DIN, GSTIN, IEC, or full Company Name. |
{
"type": "object",
"required": [
"identifier"
],
"properties": {
"identifier": {
"type": "string",
"description": "Any valid business identifier: CIN, PAN, DIN, GSTIN, IEC, or full Company Name."
}
}
}Answer any other identity / KYC / business question when no specific tool fits. Provide a natural-language `question` plus the `identifiers` you already have (phone, email, PAN, GSTIN, CIN, DIN, UAN, IFSC, vehicle RC, UPI VPA, UDIN, or a company name). It figures out the right lookup — or a short sequence — and returns the answer. Only pass identifiers the user actually gave you; never invent one. For consent-required lookups, ask the user to open the consent link in portal.outris.com/mcp and pass the consent_token they receive. Cost: 3 credits
| Argument | Type | Description |
|---|---|---|
| consent | string | Deprecated legacy consent flag ('Y'); accepted only during migration. Prefer consent_token. |
| question* | string | The user's question in plain language. |
| identifiers* | object | Identifiers you have, as {type: value} — e.g. {"pan": "ABCDE1234F"} or {"phone": "9876543210"}. Only include values the user provided. |
| consent_token | string | Server-issued consent token from portal.outris.com/mcp (preferred for consent-required lookups). |
{
"type": "object",
"required": [
"question",
"identifiers"
],
"properties": {
"consent": {
"type": "string",
"description": "Deprecated legacy consent flag ('Y'); accepted only during migration. Prefer consent_token."
},
"question": {
"type": "string",
"description": "The user's question in plain language."
},
"identifiers": {
"type": "object",
"description": "Identifiers you have, as {type: value} — e.g. {\"pan\": \"ABCDE1234F\"} or {\"phone\": \"9876543210\"}. Only include values the user provided."
},
"consent_token": {
"type": "string",
"description": "Server-issued consent token from portal.outris.com/mcp (preferred for consent-required lookups)."
}
}
}Validate an Indian bank account WITHOUT moving any money (no-debit NPCI validation) and return whether it is valid plus the account holder's name for matching. Best for: payout/beneficiary verification. This does NOT transfer funds. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| ifsc* | string | IFSC code of the account's branch. |
| account_number* | string | Bank account number to validate. |
{
"type": "object",
"required": [
"account_number",
"ifsc"
],
"properties": {
"ifsc": {
"type": "string",
"description": "IFSC code of the account's branch."
},
"account_number": {
"type": "string",
"description": "Bank account number to validate."
}
}
}Verify an Indian PAN (Permanent Account Number) and return the holder's name, status, and PAN type (individual / company / etc.). Best for: KYC, PAN validity checks. Cost: 2 credits
| Argument | Type | Description |
|---|---|---|
| pan* | string | 10-character PAN (e.g. ABCDE1234F). |
{
"type": "object",
"required": [
"pan"
],
"properties": {
"pan": {
"type": "string",
"description": "10-character PAN (e.g. ABCDE1234F)."
}
}
}{
"type": "object",
"required": [
"phone"
],
"properties": {
"dob": {
"type": "string",
"description": "Optional date of birth (disambiguates common names)."
},
"pan": {
"type": "string",
"description": "Optional PAN — strongest key for PEP/enforcement."
},
"city": {
"type": "string",
"description": "Optional city (adverse-media disambiguation)."
},
"name": {
"type": "string",
"description": "Optional subject full name."
},
"email": {
"type": "string",
"description": "Optional subject email."
},
"phone": {
"type": "string",
"description": "Indian mobile number (10-digit, with or without +91)."
},
"consent": {
"type": "string",
"description": "Deprecated legacy consent flag ('Y'); migration only."
},
"consent_token": {
"type": "string",
"description": "Server-issued consent token (preferred)."
}
}
}