_ registry / mcp http-sse · checked 3h ago

devstack

https://devstack-mcp.vercel.app

Registry code: 135c92299fda5b2a

api record

Dev-registry data: npm/PyPI/Docker/VS Code packages, dep graphs, vulns, 50+ ecosystems.

from a public catalogue that lists it, not from the operator

endpoint
https://devstack-mcp.vercel.app/mcp
protocol
http-sse ·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 devstack live?
Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
Is devstack free to use?
Yes — the hub reached it with no key and no payment.
What tools does devstack have?
10 tools: get_downloads, get_ecosystems_package, get_insights, scan_vulnerabilities_batch, get_package, get_versions, get_vulnerabilities, search_packages, ….
Is devstack 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
99.3%

90 days 99.6%· all time 99.6%

latency
225ms

last good check

priced tools
0

of 10 tools

_ answered our checks, 90 days 277 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • look up package details across registries
  • get a package's dependency graph
  • check a package for vulnerabilities
  • get package download stats
  • scan a lockfile for vulnerabilities
takes → gives
text, data → data
tools
10 reads
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 10 tools
10 never probed 0 of 10 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_downloads reads unknown 3h ago

    Download statistics for a package. Only npm (via api.npmjs.org) and PyPI (via pypistats.org) support this; any other registry returns 400 not_supported. npm returns a period window with downloads, start, and end; PyPI returns last_day, last_week, and last_month totals.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "registry",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name."
        },
        "registry": {
          "enum": [
            "npm",
            "pypi"
          ],
          "type": "string",
          "description": "Target registry. Only npm and pypi expose download stats."
        }
      }
    }
    arguments 22 lines
  • get_ecosystems_package reads unknown 16h ago

    Full normalized metadata for one package on one of 50+ registries, via ecosyste.ms — including the fields v1 registries can't give you: dependentReposCount and dependentPackagesCount (reverse dependencies), ecosystem, and vulnerabilityCount. Scoped/namespaced names are handled automatically. Returns 404 if the package does not exist on that ecosystem.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ecosystem",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name / id."
        },
        "ecosystem": {
          "type": "string",
          "description": "Target ecosyste.ms ecosystem slug (e.g. npm, pypi, cargo, rubygems)."
        }
      }
    }
    arguments 18 lines
  • get_insights reads unknown 16h ago

    Health and security insights for a package's source project, via deps.dev. Returns the linked source repository, GitHub stars/forks/openIssues, licenses, resolved dependencyCount, security advisories, and the full OSSF Scorecard (ossfScore 0..10 plus the per-check breakdown). Omit version to use the registry default version — note deps.dev's default is a MOVING target and an unverified default mirror may have no computed scorecard (ossfScore: null); pin version for a stable, scorecard-backed result. system is lowercased (npm, pypi, cargo, go, maven, …).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "system",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name / id."
        },
        "system": {
          "enum": [
            "npm",
            "pypi",
            "cargo",
            "go",
            "maven",
            "nuget"
          ],
          "type": "string",
          "description": "Package system / ecosystem for deps.dev. Case-insensitive, lowercased server-side."
        },
        "version": {
          "type": "string",
          "description": "Exact version. Omit for the (moving) registry default version."
        }
      }
    }
    arguments 30 lines
  • scan_vulnerabilities_batch reads unknown 3h ago

    Scan many packages in one call — ideal for a whole lockfile. Pass a queries[] array (max 100) of { ecosystem, name, version? }; results are returned positionally aligned, one row per query, each with a count and a hydrated vulns[] array. Advisories are de-duplicated and hydrated across the batch. ecosystem is CASE-SENSITIVE (OSV spelling).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "queries"
      ],
      "properties": {
        "queries": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Package name (required)."
              },
              "version": {
                "type": "string",
                "description": "Exact version. Omit for full history."
              },
              "ecosystem": {
                "type": "string",
                "description": "OSV ecosystem (case-sensitive). e.g. npm, PyPI, Go."
              }
            }
          },
          "maxItems": 100,
          "minItems": 1,
          "description": "Up to 100 { ecosystem, name, version? } queries, ideal for a whole lockfile."
        }
      }
    }
    arguments 35 lines
  • get_package reads unknown 12h ago

    Full normalized details for one package by registry + name, in a single unified Package shape across npm, PyPI, Docker Hub, and the VS Code Marketplace. name handles scoped npm ids (e.g. @types/node), Docker namespaces (e.g. library/nginx or a bare nginx for official images), and VS Code publisher.extension ids. With registry=all the request fans out to every registry in parallel and returns a packages array (missing registries are silently dropped); otherwise a single package is returned.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "registry",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name / id. Supports scoped npm ids (@scope/pkg), Docker namespaces (ns/name or a bare name for official images), and VS Code publisher.extension ids."
        },
        "registry": {
          "enum": [
            "npm",
            "pypi",
            "docker",
            "vscode",
            "all"
          ],
          "type": "string",
          "description": "Target registry. \"all\" fans out to every registry and merges results."
        }
      }
    }
    arguments 25 lines
  • get_versions reads unknown 12h ago

    List published versions (npm/PyPI), image tags (Docker Hub, most recent 25), or extension versions (VS Code) for a package. registry=all is NOT supported here — pick a single registry. Each item carries version and released, plus registry-specific extras (files for PyPI, size for Docker tags).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "registry",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name / id (scoped npm ids, Docker namespaces, and VS Code publisher.extension ids supported)."
        },
        "registry": {
          "enum": [
            "npm",
            "pypi",
            "docker",
            "vscode"
          ],
          "type": "string",
          "description": "Target registry. \"all\" is not supported here — pick one."
        }
      }
    }
    arguments 24 lines
  • get_vulnerabilities reads unknown 12h ago

    Known vulnerabilities (CVE / GHSA / PYSEC / GO advisories) for a package, via OSV.dev. Pass version to filter to advisories affecting that exact version, or omit it for the package's full advisory history. Each result carries the OSV id, cross-id aliases, a severity word grade (LOW|MODERATE|HIGH|CRITICAL), the cvss vector string, affectedRanges with fixed-version events, references, and cwes. A clean package returns count: 0 with an empty list (not an error). ecosystem is CASE-SENSITIVE — use OSV's spelling (npm, PyPI, Go, crates.io, Maven, NuGet, RubyGems, …). Use scan_vulnerabilities_batch for lockfile batch scans.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "ecosystem",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name."
        },
        "version": {
          "type": "string",
          "description": "Exact version to filter advisories to. Omit for full history."
        },
        "ecosystem": {
          "type": "string",
          "description": "OSV ecosystem, CASE-SENSITIVE (e.g. npm, PyPI, Go, crates.io, Maven, NuGet, RubyGems)."
        }
      }
    }
    arguments 22 lines
  • search_packages reads unknown 16h ago

    Search a registry for packages matching q. registry=all fans out to npm, Docker Hub, and the VS Code Marketplace and merges the results. PyPI has no public search API, so registry=pypi returns 400 not_supported — look a PyPI package up by name via get_package instead. Results are normalized PackageSummary items (npm adds a relevance score; Docker adds isOfficial).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "registry",
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Search query."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results per registry. Clamped to 1-50. Default 20."
        },
        "registry": {
          "enum": [
            "npm",
            "pypi",
            "docker",
            "vscode",
            "all"
          ],
          "type": "string",
          "description": "Target registry. \"all\" fans out to npm, Docker, and VS Code and merges results. pypi returns not_supported."
        }
      }
    }
    arguments 31 lines
  • get_dependency_graph reads unknown 3h ago

    The fully resolved dependency graph for one exact package version, via deps.dev. Returns a flat nodes[] array plus integer-index edges[] (walk from/to to rebuild the tree). Each node carries relation (self | direct | indirect) and a direct boolean; node[0] is always the queried root (relation: self). Node order is NOT stable — look nodes up by name/relation, never by positional index. system is case-insensitive and lowercased (npm, pypi, cargo, go, maven, nuget). version is REQUIRED (a graph is resolved for one exact version).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "system",
        "name",
        "version"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Package name / id."
        },
        "system": {
          "enum": [
            "npm",
            "pypi",
            "cargo",
            "go",
            "maven",
            "nuget"
          ],
          "type": "string",
          "description": "Package system / ecosystem for deps.dev. Case-insensitive, lowercased server-side."
        },
        "version": {
          "type": "string",
          "description": "Exact version to resolve (e.g. 18.2.0). Required."
        }
      }
    }
    arguments 31 lines
  • search_ecosystems reads unknown 35h ago

    Look a package name up across 50+ registries at once, via ecosyste.ms. This is an EXACT-name lookup (not fuzzy full-text): q=react returns the react package everywhere it exists (npm, cargo, nuget, pub, bower, …), each as a normalized ecosystemsPackage with reverse-dependency counts. Pass ecosystem to narrow to one registry. Results carry dependentReposCount, dependentPackagesCount, and vulnerabilityCount.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Exact package name to look up across registries."
        },
        "limit": {
          "type": "integer",
          "maximum": 50,
          "minimum": 1,
          "description": "Max results. Clamped to 1-50. Default 20."
        },
        "ecosystem": {
          "type": "string",
          "description": "Narrow to one ecosystem (e.g. pypi, npm, cargo). Omit to search all."
        }
      }
    }
    arguments 23 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 135c92299fda5b2a.

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

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.