LoginLlama

io.github.joshghentPublished by GitHub account joshghentv1.0.0Updated Oct 26, 2026

Ask questions about your login security data: risk scores, blocked logins, Tor, VPN and bot traffic.

VerifiedStreamable HTTPWeb executableSecurity & MonitoringData & Analytics

Overview

AI-generated overview

LoginLlama's remote MCP server lets an assistant query your team's login security data: risk scores, blocked logins, and bot, Tor or VPN traffic.

What you can do
  • Summarize overall login security for your team, including total checks, average risk score, high-risk and blocked counts, with filters by browser, OS, country, device, user and time window.
  • Compute the average login risk score across matching logins.
  • Group logins by browser, OS, device, country or status with counts, average risk and high-risk totals per group.
  • List the most recent login checks with risk score, status, location and device.
  • Check account usage: remaining API credits for production and staging, and plan name.
When to use it
Useful when you want to ask plain-language questions about login risk and traffic patterns, such as which browser carries the highest risk or how many logins were blocked, without opening the LoginLlama dashboard.
Requirements
A remote MCP endpoint at loginllama.app over streamable HTTP. Requires a LoginLlama account and an API key sent in the X-API-KEY header, taken from the API page of the dashboard. Network access to the service.
Before you install
The API key is a secret sent in the X-API-KEY header; keep it out of shared logs and configs. Queries consume API credits, and the usage tool reports remaining production and staging credits. Login data returned includes user, location and device details, so answers may expose sensitive security information.

Installation

In SourceWeft

  1. Open LoginLlama in the dashboard and add it to a workspace.
  2. Connect X-API-KEY credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.joshghent%2Floginllama/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "loginllama": {
      "type": "http",
      "url": "https://loginllama.app/api/v1/mcp",
      "headers": {
        "X-API-KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

5

get_login_stats

Overall login security summary for your team: total checks, average risk score, high-risk count, blocked/failed logins, and bot/Tor/VPN counts. Supports filtering by browser, OS, country, device, user and time window.

Parametersosdaysdevicebrowsercountryidentity_key

get_average_risk_score

Average login risk score (0-10) across matching logins. Use the filters to answer questions like "what is my average login risk score for the chrome browser".

Parametersosdaysdevicebrowsercountryidentity_key

get_login_breakdown

Group logins by a dimension (browser, os, device, country, or status) and return counts, average risk score and high-risk counts per group. Good for "which browser has the highest risk".

Parametersosdaystop_ndevicebrowsercountrydimensionrequiredidentity_key

get_recent_logins

List the most recent login checks (newest first) with risk score, status, location and device. Supports the same filters.

Parametersosdayslimitdevicestatusbrowsercountryidentity_key

get_account_usage

Your LoginLlama account usage: remaining API credits for production and staging, and plan name.

Takes no parameters.

Version history

1
  1. v1.0.0LatestOct 19, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.