LoginLlama MCP

An official MCP server provided by LoginLlama that allows AI agents to query login security analytics in plain language. It enables users to retrieve risk scores, blocked logins, and traffic data related to Tor, VPNs, and bots, scoped to the user's team and read-only.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-10-26Operated by LoginLlama

MCP endpoint (Streamable HTTP)

https://loginllama.app/api/v1/mcp

Vendor documentation

What you can do with it

Query average login risk scores filtered by browser or OS
Identify the browser with the highest risk logins this month
Retrieve the 10 most recent high-risk login attempts
Count Tor or VPN logins seen in the last 7 days

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: io.github.joshghent/loginllama@1.0.0 Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Oct 31, 2026, 7:56 PM UTC · registry · passed · metadata changed · Source metadata updated
Oct 31, 2026, 7:56 PM UTC · backfill · recorded · Pre-expansion baseline; unobserved rich metadata remains unknown

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http loginllama-mcp https://loginllama.app/api/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add loginllama-mcp --url https://loginllama.app/api/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable loginllama-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "loginllama-mcp": {
      "url": "https://loginllama.app/api/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "loginllama-mcp": {
      "type": "streamableHttp",
      "url": "https://loginllama.app/api/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start loginllama-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "loginllama-mcp": {
      "type": "http",
      "url": "https://loginllama.app/api/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http loginllama-mcp https://loginllama.app/api/v1/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "loginllama-mcp": {
      "url": "https://loginllama.app/api/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "loginllama-mcp": {
      "serverUrl": "https://loginllama.app/api/v1/mcp"
    }
  }
}

Let your agent find its tools

Find servers like LoginLlama MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 2,301

Do you run LoginLlama MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing