Outris Identity MCP Server

How to use

You connect to the Outris Identity MCP Server using an MCP client that supports HTTP streamable transport or the local STDIO transport. The server exposes tools that let you resolve identities, verify platform registrations, examine commerce activity, and check for known data breaches. Start by obtaining an API key, then choose the transport that fits your environment.

Primary usage patterns include querying identity-related data for a given phone number or email. You can request complete profiles, names, emails, addresses, and linked identifiers, as well as check where the subject has registrations across social platforms and e-commerce services. For security, always provide your API key in the Authorization header or as configured by your client, and respect the credit-based rate limits.

How to install

Prerequisites: ensure you have Python 3.8+ and pip installed on your system. If you prefer a containerized setup, Docker is also supported.

Option A: Local installation (Python)

# Clone the MCP server repository
git clone https://github.com/outris/outris-identity-mcp.git
cd outris-identity-mcp

# Install Python dependencies
pip install -r requirements.txt

# Start the server locally (HTTP transport available via /http endpoint)
python -m mcp_server --http
# Server runs on http://localhost:8000

Option B: Cloud deployment using a client config

{
  "mcpServers": {
    "outris-identity": {
      "command": "npx",
      "args": [
        "-y", 
        "mcp-remote", 
        "https://mcp-server.outris.com/http",
        "--transport", 
        "streamable-http",
        "--header", 
        "Authorization=Bearer YOUR_API_KEY"
      ]
    }
  }
}

Option C: Docker (containerized)

docker build -t outris-identity .
docker run -e OUTRIS_API_KEY="your_key" -p 8000:8000 outris-identity

Configuration and security notes

The server uses API key authentication with a credit-based rate limiter. Keep your API key secure and rotate it regularly. If you deploy in the cloud, store the key as a secure environment variable or secret and reference it in client configurations.

Key configuration options are shown in the cloud client snippet, which demonstrates how to pass the API key through the Authorization header. When running locally, start the HTTP server to expose endpoints such as /health, /tools, and the individual tools under the http transport.

Transport overview and endpoints

Streamable HTTP provides the primary cloud-friendly path for remote clients. SSE is supported for legacy clients and proxies, while STDIO enables local command-line or embedded usage without a network layer.

Common endpoints include health checks and a catalog of available tools. You can invoke a tool by sending a properly formed request to the HTTP endpoint associated with the tool name.

Troubleshooting tips

If you encounter authentication errors, verify your API key is correct and that the Authorization header is present in requests. Ensure the server has sufficient credits available for the requested operations. For local runs, confirm Python is installed and that the mcp_server module is reachable.

For docker deployments, check the container logs if the server fails to start or respond, and verify the environment variable OUTRIS_API_KEY is provided to the container.

get_identity_profile

Return a complete profile for a given identifier, including names, emails, addresses, and documents.

get_name

Retrieve names linked to a phone number.

get_email

Retrieve emails linked to a phone number.

get_address

Obtain addresses associated with a phone number for various contexts such as ecommerce or banking.

get_alternate_phones

Find additional phone numbers associated with the same person.

check_online_platforms

Check registrations across social media and apps for the identifier.

check_digital_commerce_activity

Inspect ecommerce, travel, and quick-commerce activities linked to the identifier.

check_breaches

Detect if the identifier appears in known data breaches.