LoginLlama
REMOTE · LOGINLLAMA.APP
Ask questions about your login security data: risk scores, blocked logins, Tor, VPN and bot traffic.
Available components
Last scanned (9 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 26 Oct 2026.
Category Security
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 767 tokens (~153/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 +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.
- 20 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 19 Oct 26 62
First indexed and scored.
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 26 Oct 2026 · Probed https://loginllama.app/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=loginllama.app | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | d3a287097656151313e8d9378f20c0a5 |
| SANs: loginllama.app, *.loginllama.app | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of loginllama.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| loginllama.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-eval' 'unsafe-inline' *.sentry.io *.stripe.com *.googletagmanager.com *.google-analytics.com analytics.ahrefs.com client.crisp.chat; style-src 'self' 'unsafe-inline' fonts.googleapis.com; font-src 'self' fonts.gstatic.com; img-src 'self' data: https: blob:; worker-src 'self' blob:; connect-src 'self' *.sentry.io *.stripe.com api.mapbox.com basemaps.cartocdn.com *.basemaps.cartocdn.com *.google-analytics.com *.analytics.google.com analytics.ahrefs.com wss://client.crisp.chat; frame-src 'self' *.stripe.com; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://loginllama.app/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://loginllama.app/api/v1/mcp | HTTPS enforced | 301 | https://loginllama.app/api/v1/mcp |
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 →
get_account_usage ~28
Your LoginLlama account usage: remaining API credits for production and staging, and plan name.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_average_risk_score ~156
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".
| Name | Type | Req | Description |
|---|---|---|---|
| browser | string | – | Filter by browser, case-insensitive partial match e.g. "chrome". |
| country | string | – | Filter by country e.g. "United States". |
| days | number | – | Look back this many days (default 30). Omit for all time. |
| device | string | – | Filter by device e.g. "iphone". |
| identity_key | string | – | Filter to a single user identifier (email, user id, etc). |
| os | string | – | Filter by operating system e.g. "windows". |
No output schema declared.
No examples provided.
get_login_breakdown ~191
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".
| Name | Type | Req | Description |
|---|---|---|---|
| browser | string | – | Filter by browser, case-insensitive partial match e.g. "chrome". |
| country | string | – | Filter by country e.g. "United States". |
| days | number | – | Look back this many days (default 30). Omit for all time. |
| device | string | – | Filter by device e.g. "iphone". |
| dimension | string | yes | The attribute to group by. |
| identity_key | string | – | Filter to a single user identifier (email, user id, etc). |
| os | string | – | Filter by operating system e.g. "windows". |
| top_n | number | – | Max groups to return (default 20). |
No output schema declared.
No examples provided.
get_login_stats ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| browser | string | – | Filter by browser, case-insensitive partial match e.g. "chrome". |
| country | string | – | Filter by country e.g. "United States". |
| days | number | – | Look back this many days (default 30). Omit for all time. |
| device | string | – | Filter by device e.g. "iphone". |
| identity_key | string | – | Filter to a single user identifier (email, user id, etc). |
| os | string | – | Filter by operating system e.g. "windows". |
No output schema declared.
No examples provided.
get_recent_logins ~186
List the most recent login checks (newest first) with risk score, status, location and device. Supports the same filters.
| Name | Type | Req | Description |
|---|---|---|---|
| browser | string | – | Filter by browser, case-insensitive partial match e.g. "chrome". |
| country | string | – | Filter by country e.g. "United States". |
| days | number | – | Look back this many days (default 30). Omit for all time. |
| device | string | – | Filter by device e.g. "iphone". |
| identity_key | string | – | Filter to a single user identifier (email, user id, etc). |
| limit | number | – | How many to return (default 25, max 100). |
| os | string | – | Filter by operating system e.g. "windows". |
| status | string | – | Filter by status, e.g. "valid" or "invalid". |
No output schema declared.
No examples provided.
How do I install the LoginLlama MCP server?
LoginLlama is a hosted endpoint at https://loginllama.app/api/v1/mcp, 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 · loginllama.app
claude mcp add --transport http joshghent-loginllama 'https://loginllama.app/api/v1/mcp'
What is the LoginLlama MCP server?
LoginLlama is an MCP server listed in the public MCP registry as io.github.joshghent/loginllama. Ask questions about your login security data: risk scores, blocked logins, Tor, VPN and bot traffic. This page covers its hosted endpoint (https://loginllama.app/api/v1/mcp).
Is the LoginLlama MCP server safe to use?
LoginLlama scores 65 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 LoginLlama MCP server expose?
LoginLlama exposes 5 tools: get_login_stats, get_average_risk_score, get_login_breakdown, get_recent_logins, get_account_usage. Their descriptions and schemas cost roughly 730 tokens of context every time the server is loaded.
Does the LoginLlama MCP server require authentication?
No. We connected to LoginLlama without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the LoginLlama MCP server still maintained?
LoginLlama is still listed as active in the MCP registry. We last reached this channel on 26 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.