# io.github.outris-dev-user/outris-identity-mcp (remote · mcp-server.outris.com)

Identity resolution MCP server for phone/email lookups across 31+ services. Global + India coverage.

- Trust score: 75/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp-server.outris.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/outris-dev-user-outris-identity-mcp/mcp-server.md), [page](https://verifymcp.io/servers/outris-dev-user-outris-identity-mcp/mcp-server)

## Channel facts

- Endpoint: `https://mcp-server.outris.com/http`
- Transports: `streamable-http`
- Auth: `required`
- Version: `2.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1412 tokens (~108/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http outris-dev-user-outris-identity-mcp https://mcp-server.outris.com/http
```

### Codex

```toml
[mcp_servers.outris-dev-user-outris-identity-mcp]
url = "https://mcp-server.outris.com/http"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "outris-dev-user-outris-identity-mcp": {
      "type": "remote",
      "url": "https://mcp-server.outris.com/http",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add outris-dev-user-outris-identity-mcp --url https://mcp-server.outris.com/http --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  outris-dev-user-outris-identity-mcp:
    url: "https://mcp-server.outris.com/http"
```

### Other

```json
{
  "mcpServers": {
    "outris-dev-user-outris-identity-mcp": {
      "type": "http",
      "url": "https://mcp-server.outris.com/http"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 74, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 71, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 68)

First indexed and scored.

## MCP tools (12)

### `investigate_phone` (~130 tokens)

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

Input parameters:

- `depth` (string): basic = fast identity bundle (default); full = comprehensive investigation (slower).
- `phone` (string, required): Indian mobile number (10-digit, with or without +91).

### `assess_fraud_risk` (~115 tokens)

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

Input parameters:

- `detailed` (boolean): Include the full raw signal breakdown. Default false.
- `phone` (string, required): Indian mobile number (10-digit, with or without +91).

### `find_contacts` (~140 tokens)

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

Input parameters:

- `consent` (string): Deprecated legacy consent flag ('Y'); accepted only during migration.
- `consent_token` (string): Server-issued consent token from portal.outris.com/mcp (preferred).
- `phone` (string, required): Indian mobile number (10-digit, with or without +91).

### `due_diligence_person_start` (~242 tokens)

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

Input parameters:

- `city` (string): Optional city (adverse-media disambiguation).
- `consent` (string): Deprecated legacy consent flag ('Y'); migration only.
- `consent_token` (string): Server-issued consent token (preferred).
- `dob` (string): Optional date of birth (disambiguates common names).
- `email` (string): Optional subject email.
- `name` (string): Optional subject full name.
- `pan` (string): Optional PAN — strongest key for PEP/enforcement.
- `phone` (string, required): Indian mobile number (10-digit, with or without +91).

### `check_job` (~64 tokens)

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

Input parameters:

- `job_id` (string, required): The job_id returned by an async tool.

### `investigate_email` (~62 tokens)

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

Input parameters:

- `email` (string, required): Email address to investigate.

### `resolve_company` (~78 tokens)

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

Input parameters:

- `company_name` (string, required): Company name to resolve.

### `lookup_gst` (~69 tokens)

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

Input parameters:

- `gstin` (string, required): 15-character GSTIN.

### `verify_pan` (~72 tokens)

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

Input parameters:

- `pan` (string, required): 10-character PAN (e.g. ABCDE1234F).

### `lookup_vehicle` (~68 tokens)

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

Input parameters:

- `rc_number` (string, required): Vehicle registration number (e.g. MH12AB1234).

### `verify_bank_account` (~91 tokens)

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

Input parameters:

- `account_number` (string, required): Bank account number to validate.
- `ifsc` (string, required): IFSC code of the account's branch.

### `smart_lookup` (~252 tokens)

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

Input parameters:

- `consent` (string): Deprecated legacy consent flag ('Y'); accepted only during migration. Prefer consent_token.
- `consent_token` (string): Server-issued consent token from portal.outris.com/mcp (preferred for consent-required lookups).
- `identifiers` (object, required): Identifiers you have, as {type: value} — e.g. {"pan": "ABCDE1234F"} or {"phone": "9876543210"}. Only include values the user provided.
- `question` (string, required): The user's question in plain language.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/outris-dev-user-outris-identity-mcp/mcp-server#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 75
- 2026-08-01: 74
- 2026-07-31: 74
- 2026-07-30: 71
- 2026-07-29: 70
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 68

## Links

- Remote endpoint: https://mcp-server.outris.com/http
- Authorisation metadata: https://mcp-server.outris.com/.well-known/oauth-protected-resource/http
- Repository: https://github.com/outris-dev-user/outris-identity-mcp
- Changelog RSS feed: https://verifymcp.io/servers/outris-dev-user-outris-identity-mcp/mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/outris-dev-user-outris-identity-mcp/mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/outris-dev-user-outris-identity-mcp/mcp-server