_ registry / mcp streamable-http · checked 5h ago

loginllama

https://loginllama.app

Registry code: 02636844ed918cad

api record

Authenticate with the X-API-KEY header. All tools are scoped to your team. Ask questions like "what is my average login risk score for the chrome browser".

endpoint
https://loginllama.app/api/v1/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is loginllama live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is loginllama free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does loginllama have?
5 tools: get_account_usage, get_login_breakdown, get_recent_logins, get_average_risk_score, get_login_stats.
Is loginllama safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
230ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
5 auth-required 5 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_account_usage auth-required 5h ago

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

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_login_breakdown auth-required never probed

    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".

    mcp-tool

    {
  "type": "object",
  "required": [
    "dimension"
  ],
  "properties": {
    "os": {
      "type": "string",
      "description": "Filter by operating system e.g. \"windows\"."
    },
    "days": {
      "type": "number",
      "description": "Look back this many days (default 30). Omit for all time."
    },
    "top_n": {
      "type": "number",
      "description": "Max groups to return (default 20)."
    },
    "device": {
      "type": "string",
      "description": "Filter by device e.g. \"iphone\"."
    },
    "browser": {
      "type": "string",
      "description": "Filter by browser, case-insensitive partial match e.g. \"chrome\"."
    },
    "country": {
      "type": "string",
      "description": "Filter by country e.g. \"United States\"."
    },
    "dimension": {
      "enum": [
        "browser",
        "os",
        "device",
        "country",
        "status"
      ],
      "type": "string",
      "description": "The attribute to group by."
    },
    "identity_key": {
      "type": "string",
      "description": "Filter to a single user identifier (email, user id, etc)."
    }
  }
}
    arguments 47 lines
  • get_recent_logins auth-required never probed

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

    mcp-tool

    {
  "type": "object",
  "properties": {
    "os": {
      "type": "string",
      "description": "Filter by operating system e.g. \"windows\"."
    },
    "days": {
      "type": "number",
      "description": "Look back this many days (default 30). Omit for all time."
    },
    "limit": {
      "type": "number",
      "description": "How many to return (default 25, max 100)."
    },
    "device": {
      "type": "string",
      "description": "Filter by device e.g. \"iphone\"."
    },
    "status": {
      "type": "string",
      "description": "Filter by status, e.g. \"valid\" or \"invalid\"."
    },
    "browser": {
      "type": "string",
      "description": "Filter by browser, case-insensitive partial match e.g. \"chrome\"."
    },
    "country": {
      "type": "string",
      "description": "Filter by country e.g. \"United States\"."
    },
    "identity_key": {
      "type": "string",
      "description": "Filter to a single user identifier (email, user id, etc)."
    }
  }
}
    arguments 37 lines
  • get_average_risk_score auth-required 5h ago

    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".

    mcp-tool

    {
  "type": "object",
  "properties": {
    "os": {
      "type": "string",
      "description": "Filter by operating system e.g. \"windows\"."
    },
    "days": {
      "type": "number",
      "description": "Look back this many days (default 30). Omit for all time."
    },
    "device": {
      "type": "string",
      "description": "Filter by device e.g. \"iphone\"."
    },
    "browser": {
      "type": "string",
      "description": "Filter by browser, case-insensitive partial match e.g. \"chrome\"."
    },
    "country": {
      "type": "string",
      "description": "Filter by country e.g. \"United States\"."
    },
    "identity_key": {
      "type": "string",
      "description": "Filter to a single user identifier (email, user id, etc)."
    }
  }
}
    arguments 29 lines
  • get_login_stats auth-required 5h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "os": {
      "type": "string",
      "description": "Filter by operating system e.g. \"windows\"."
    },
    "days": {
      "type": "number",
      "description": "Look back this many days (default 30). Omit for all time."
    },
    "device": {
      "type": "string",
      "description": "Filter by device e.g. \"iphone\"."
    },
    "browser": {
      "type": "string",
      "description": "Filter by browser, case-insensitive partial match e.g. \"chrome\"."
    },
    "country": {
      "type": "string",
      "description": "Filter by country e.g. \"United States\"."
    },
    "identity_key": {
      "type": "string",
      "description": "Filter to a single user identifier (email, user id, etc)."
    }
  }
}
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 02636844ed918cad.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/02636844ed918cad/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/02636844ed918cad/badge.svg)](https://brick.blue/agent/02636844ed918cad?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.