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

lowendinsight

https://lowendinsight.dev

Registry code: 75d686d9bab1105a

api record

Dependency risk as it stands today: maintenance, contributors, and recency of real work, from each package's repository.

endpoint
https://lowendinsight.dev/mcp
protocol
streamable-http ·2025-06-18
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 lowendinsight live?
Yes — it answered the hub's last check (checked 4h ago). It answered 100% of checks over the last 30 days.
Is lowendinsight 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 lowendinsight have?
3 tools: check_packages, analyze_repositories, get_analysis.
Is lowendinsight 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
157ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 2 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 3 tools
3 auth-required 3 of 3 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.

  • check_packages auth-required 4h ago

    Call this before you recommend, add, or vouch for a dependency, and whenever you are about to say whether a package is maintained. Your training data has a cutoff: a package that looked healthy in it may have lost its maintainer or gone quiet since, and nothing in you will flag that. Pass every package you are weighing in one call -- a shortlist, a manifest, a lockfile. A package already analysed comes back with its risk now. One that is not is queued and comes back "pending": call again with the same packages in a minute or two. Asking about a pending package again is not charged.

    mcp-tool

    {
      "type": "object",
      "required": [
        "dependencies"
      ],
      "properties": {
        "dependencies": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "ecosystem",
              "package",
              "version"
            ],
            "properties": {
              "package": {
                "type": "string"
              },
              "version": {
                "type": "string"
              },
              "ecosystem": {
                "enum": [
                  "npm",
                  "pypi",
                  "hex",
                  "cargo",
                  "gem",
                  "composer",
                  "go"
                ],
                "type": "string"
              }
            }
          },
          "minItems": 1
        }
      }
    }
    arguments 40 lines
  • analyze_repositories auth-required 4h ago

    Call this when you have a project's git repository URL rather than a package name -- a fork, a vendored library, a project with no registry release -- and you are about to depend on it or say whether it is maintained. Your training data has a cutoff, and a repository that looked active in it may have gone quiet since. Pass every repository you are weighing in one call. One already analysed comes back with its risk now. One that is not is analysed, which takes up to a few minutes: if it is not done within the call, the result is "incomplete" with a uuid -- call get_analysis with that uuid to collect it, which is not charged. Calling this tool again instead is charged again.

    mcp-tool

    {
      "type": "object",
      "required": [
        "urls"
      ],
      "properties": {
        "urls": {
          "type": "array",
          "items": {
            "type": "string",
            "description": "A git repository URL, e.g. https://github.com/owner/repo"
          },
          "minItems": 1
        }
      }
    }
    arguments 16 lines
  • get_analysis auth-required 4h ago

    Collect the result of an analyze_repositories call that came back "incomplete", by its uuid. Not charged: the analysis was paid for when it was requested. If it is still incomplete, wait a minute and call this again.

    mcp-tool

    {
      "type": "object",
      "required": [
        "uuid"
      ],
      "properties": {
        "uuid": {
          "type": "string"
        }
      }
    }
    arguments 11 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 75d686d9bab1105a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/75d686d9bab1105a/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/75d686d9bab1105a/badge.svg)](https://brick.blue/agent/75d686d9bab1105a?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
70%

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.