io.github.outris-dev-user/outris-identity-mcp
REMOTE · MCP-SERVER.OUTRIS.COM · SCANNED SEP 21
Identity resolution MCP server for phone/email lookups across 31+ services. Global + India coverage.
Available components
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. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 2100 tokens (~105/item across 20 items; 19 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.outris-dev-user/outris-identity-mcp server?
io.github.outris-dev-user/outris-identity-mcp is a hosted endpoint at https://mcp-server.outris.com/http, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp-server.outris.com
claude mcp add --transport http outris-dev-user-outris-identity-mcp 'https://mcp-server.outris.com/http'
{
"mcpServers": {
"outris-dev-user-outris-identity-mcp": {
"url": "https://mcp-server.outris.com/http"
}
}
} {
"servers": {
"outris-dev-user-outris-identity-mcp": {
"type": "http",
"url": "https://mcp-server.outris.com/http"
}
}
} [mcp_servers.outris-dev-user-outris-identity-mcp] url = "https://mcp-server.outris.com/http"
{
"$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 mcp add outris-dev-user-outris-identity-mcp --url 'https://mcp-server.outris.com/http' --transport streamable-http
mcp_servers:
outris-dev-user-outris-identity-mcp:
url: "https://mcp-server.outris.com/http" {
"McpServers": {
"outris-dev-user-outris-identity-mcp": {
"Transport": "http",
"Url": "https://mcp-server.outris.com/http"
}
}
} assistant mcp add outris-dev-user-outris-identity-mcp -t streamable-http -u 'https://mcp-server.outris.com/http'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- Schema quality: fail → pass ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://mcp-server.outris.com/http
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp-server.outris.com | CN=YR2,O=Let's Encrypt,C=US | 24 Jul 2026 | 22 Oct 2026 | RSA 2048 | SHA256-RSA | 6ed0cfb7c58a09da6cdddc093fb19d441c8 |
| SANs: mcp-server.outris.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-server.outris.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| outris.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer
Bearer Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-server.outris.com/http | Verified | 200 | |
| http (plaintext) | http://mcp-server.outris.com/http | HTTPS enforced | 301 | https://mcp-server.outris.com/http |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
assess_fraud_risk ~115
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
| Name | Type | Req | Description |
|---|---|---|---|
| detailed | boolean | – | Include the full raw signal breakdown. Default false. |
| phone | string | yes | Indian mobile number (10-digit, with or without +91). |
No output schema declared.
No examples provided.
check_digital_commerce_activity ~138
**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
| Name | Type | Req | Description |
|---|---|---|---|
| include_demographics | boolean | – | Include age/gender estimation (default: true) |
| phone | string | yes | Phone number (with or without country code) |
No output schema declared.
No examples provided.
check_job ~64
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
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id returned by an async tool. |
No output schema declared.
No examples provided.
check_online_platforms ~107
**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
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number (with or without country code) |
No output schema declared.
No examples provided.
due_diligence_person_start ~242
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| string | – | Optional subject email. | |
| name | string | – | Optional subject full name. |
| pan | string | – | Optional PAN — strongest key for PEP/enforcement. |
| phone | string | yes | Indian mobile number (10-digit, with or without +91). |
No output schema declared.
No examples provided.
find_contacts ~140
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Indian mobile number (10-digit, with or without +91). |
No output schema declared.
No examples provided.
get_address ~82
**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
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number |
No output schema declared.
No examples provided.
get_alternate_phones ~107
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
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number |
No output schema declared.
No examples provided.
get_email ~73
**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
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number |
No output schema declared.
No examples provided.
get_identity_profile ~98
**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
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number |
No output schema declared.
No examples provided.
get_name ~83
**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
| Name | Type | Req | Description |
|---|---|---|---|
| phone | string | yes | Phone number |
No output schema declared.
No examples provided.
investigate_email ~62
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
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address to investigate. |
No output schema declared.
No examples provided.
investigate_phone ~130
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
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | basic = fast identity bundle (default); full = comprehensive investigation (slower). |
| phone | string | yes | Indian mobile number (10-digit, with or without +91). |
No output schema declared.
No examples provided.
lookup_gst ~69
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
| Name | Type | Req | Description |
|---|---|---|---|
| gstin | string | yes | 15-character GSTIN. |
No output schema declared.
No examples provided.
lookup_vehicle ~68
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
| Name | Type | Req | Description |
|---|---|---|---|
| rc_number | string | yes | Vehicle registration number (e.g. MH12AB1234). |
No output schema declared.
No examples provided.
resolve_company ~78
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
| Name | Type | Req | Description |
|---|---|---|---|
| company_name | string | yes | Company name to resolve. |
No output schema declared.
No examples provided.
smart_lookup ~252
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
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Identifiers you have, as {type: value} — e.g. {"pan": "ABCDE1234F"} or {"phone": "9876543210"}. Only include values the user provided. |
| question | string | yes | The user's question in plain language. |
No output schema declared.
No examples provided.
verify_bank_account ~91
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
| Name | Type | Req | Description |
|---|---|---|---|
| account_number | string | yes | Bank account number to validate. |
| ifsc | string | yes | IFSC code of the account's branch. |
No output schema declared.
No examples provided.
verify_pan ~72
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
| Name | Type | Req | Description |
|---|---|---|---|
| pan | string | yes | 10-character PAN (e.g. ABCDE1234F). |
No output schema declared.
No examples provided.
What is the io.github.outris-dev-user/outris-identity-mcp server?
io.github.outris-dev-user/outris-identity-mcp is listed in the public MCP registry as io.github.outris-dev-user/outris-identity-mcp. Identity resolution MCP server for phone/email lookups across 31+ services. Global + India coverage. This page covers its hosted endpoint (https://mcp-server.outris.com/http).
Is the io.github.outris-dev-user/outris-identity-mcp server safe to use?
io.github.outris-dev-user/outris-identity-mcp scores 88 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.outris-dev-user/outris-identity-mcp server expose?
io.github.outris-dev-user/outris-identity-mcp exposes 19 tools: investigate_phone, assess_fraud_risk, find_contacts, due_diligence_person_start, check_job, and 14 more. Their descriptions and schemas cost roughly 2,071 tokens of context every time the server is loaded.
Does the io.github.outris-dev-user/outris-identity-mcp server require authentication?
Yes. io.github.outris-dev-user/outris-identity-mcp asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.outris-dev-user/outris-identity-mcp server still maintained?
io.github.outris-dev-user/outris-identity-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.