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

vulnerable-now

https://vulnerable.now

Registry code: 7faf23d8d1ff9267

api record

Look up CVE, GHSA, EUVD and OSV IDs with get_vulnerability, search the catalog by product or words with search, list recent or exploited entries with list_feed, rank what to patch with top_priority, and check package versions, lockfiles, SBOMs or website technologies with check_stack. Every result links to its page and its sources.

endpoint
https://vulnerable.now/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 vulnerable-now live?
Yes — it answered the hub's last check (checked 16h ago). It answered 100% of checks over the last 30 days.
Is vulnerable-now free to use?
Yes — the hub reached it with no key and no payment.
What tools does vulnerable-now have?
7 tools: get_vulnerability, get_package, get_product, top_priority, check_stack, search, list_feed.
Is vulnerable-now 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
422ms

last good check

priced tools
0

of 7 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 7 tools
1 open 6 never probed 1 of 7 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.

  • list_feed open 16h ago

    List vulnerabilities newest first (KEV listings by date added when kev is set). Filter by severity, CISA KEV, exploitation, public exploit code, fix availability, ecosystem, vendor, product, text and dates. Use modified_since to pick up changes since a previous run.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kev": {
          "type": "boolean",
          "description": "Only entries in the CISA KEV catalog."
        },
        "tech": {
          "type": "string",
          "description": "Only entries naming this vendor or vendor product, as a slug: apache, or apache/tomcat."
        },
        "limit": {
          "type": "integer",
          "default": 20,
          "maximum": 100,
          "minimum": 1
        },
        "query": {
          "type": "string",
          "description": "Words to match against IDs, titles, vendors, products and descriptions. For best-match ordering, use search."
        },
        "since": {
          "type": "string",
          "description": "Only entries published on or after this date (YYYY-MM-DD)."
        },
        "until": {
          "type": "string",
          "description": "Only entries published before this date (YYYY-MM-DD)."
        },
        "cursor": {
          "type": "string",
          "description": "next_cursor from the previous page."
        },
        "vendor": {
          "type": "string",
          "description": "Exact vendor name, such as apache or microsoft."
        },
        "package": {
          "type": "string",
          "description": "Only entries naming this package, as ecosystem:name, such as npm:lodash or pypi:django."
        },
        "product": {
          "type": "string",
          "description": "Exact product name, such as log4j or exchange server."
        },
        "severity": {
          "type": "array",
          "items": {
            "enum": [
              "critical",
              "high",
              "medium",
              "low"
            ],
            "type": "string"
          },
          "description": "Only these severities."
        },
        "ecosystem": {
          "type": "string",
          "description": "Package ecosystem, such as npm, PyPI, Maven, Go or crates.io."
        },
        "exploited": {
          "type": "boolean",
          "description": "Only entries with reported exploitation (KEV, CISA SSVC, ENISA or VulnCheck KEV)."
        },
        "fix_available": {
          "type": "boolean",
          "description": "Only entries with a fixed version."
        },
        "modified_since": {
          "type": "string",
          "description": "Only entries whose merged record changed at or after this date (YYYY-MM-DD) or time (ISO 8601). Pass the newest modified value from the previous run."
        },
        "public_exploit": {
          "type": "boolean",
          "description": "Only entries with public exploit code."
        }
      },
      "additionalProperties": false
    }
    arguments 81 lines
  • get_vulnerability unknown 16h ago

    Get the merged entry for one or more IDs: CVE, GitHub advisory (GHSA), EUVD, or an OSV ID such as PYSEC, GO or RUSTSEC. Returns the description, CVSS, CISA KEV status, EPSS, public exploits, affected packages, fixed versions, priority and source links.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "id": {
          "type": "string",
          "description": "One ID, such as CVE-2021-44228, GHSA-jfh8-c2jp-5v3q or PYSEC-2021-19."
        },
        "ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 20,
          "description": "Up to 20 IDs at once, for triaging scanner output."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • get_package unknown never probed

    Every known vulnerability in one open source package, most urgent first, with the affected ranges and fixed versions published for that package. Give a version to learn which advisories affect it and the lowest upgrade that leaves every affecting range.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ecosystem",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "The package name, such as lodash, django, org.apache.logging.log4j:log4j-core or golang.org/x/net."
        },
        "sort": {
          "enum": [
            "priority",
            "published",
            "score",
            "epss"
          ],
          "type": "string",
          "default": "priority"
        },
        "limit": {
          "type": "integer",
          "default": 40,
          "maximum": 100,
          "minimum": 1
        },
        "cursor": {
          "type": "string",
          "description": "next_cursor from the previous page."
        },
        "version": {
          "type": "string",
          "description": "Optional exact version to check, such as 4.17.20."
        },
        "ecosystem": {
          "type": "string",
          "description": "npm, PyPI, Maven, Go, crates.io, RubyGems, Packagist, NuGet, Hex or Pub."
        },
        "only_affected": {
          "type": "boolean",
          "description": "With version, list only the advisories that affect it."
        }
      },
      "additionalProperties": false
    }
    arguments 46 lines
  • get_product unknown never probed

    Every known vulnerability in one vendor product, such as an operating system, browser, server, CMS or appliance, most urgent first, with the affected versions and fixes. The vendor is optional: with only a product name, a clear match is answered directly and otherwise the candidates are listed. Give a version to learn which entries affect it and the lowest upgrade that clears them.

    mcp-tool

    {
      "type": "object",
      "required": [
        "product"
      ],
      "properties": {
        "sort": {
          "enum": [
            "priority",
            "published",
            "score",
            "epss"
          ],
          "type": "string",
          "default": "priority"
        },
        "limit": {
          "type": "integer",
          "default": 40,
          "maximum": 100,
          "minimum": 1
        },
        "cursor": {
          "type": "string",
          "description": "next_cursor from the previous page."
        },
        "vendor": {
          "type": "string",
          "description": "Optional vendor name, such as Apache or Fortinet."
        },
        "product": {
          "type": "string",
          "description": "The product name, such as WordPress, nginx, Tomcat or FortiOS."
        },
        "version": {
          "type": "string",
          "description": "Optional exact version to check, such as 6.4.2."
        },
        "only_affected": {
          "type": "boolean",
          "description": "With version, list only the entries that affect it."
        }
      },
      "additionalProperties": false
    }
    arguments 45 lines
  • top_priority unknown never probed

    What to patch first: the vulnerabilities with the highest priority score (exploitation, EPSS, CVSS, automatability) among those with activity in a time window, optionally narrowed to an ecosystem, vendor or product.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "kev": {
          "type": "boolean",
          "description": "Only entries in the CISA KEV catalog."
        },
        "limit": {
          "type": "integer",
          "default": 15,
          "maximum": 50,
          "minimum": 1
        },
        "vendor": {
          "type": "string",
          "description": "Exact vendor name, such as apache or microsoft."
        },
        "window": {
          "enum": [
            "week",
            "month",
            "year",
            "all"
          ],
          "type": "string",
          "default": "week"
        },
        "product": {
          "type": "string",
          "description": "Exact product name, such as log4j or exchange server."
        },
        "ecosystem": {
          "type": "string",
          "description": "Package ecosystem, such as npm, PyPI, Maven, Go or crates.io."
        }
      },
      "additionalProperties": false
    }
    arguments 38 lines
  • check_stack unknown 16h ago

    Find known vulnerabilities in what a project or site runs, ranked by what to fix first. Send exact package versions, the raw content of a lockfile (package-lock.json, poetry.lock, go.sum and others), a CycloneDX or SPDX SBOM, a Wappalyzer export, or detected technologies such as nginx 1.18.0. Returns each finding with severity, exploitation, priority and fixed versions.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "file": {
          "type": "object",
          "required": [
            "name",
            "content"
          ],
          "properties": {
            "name": {
              "type": "string",
              "description": "The file name, such as package-lock.json, bom.json or wappalyzer.csv."
            },
            "content": {
              "type": "string",
              "description": "The file content as text."
            }
          },
          "description": "A whole file: a lockfile (recognized by its name), a CycloneDX or SPDX SBOM, or a Wappalyzer JSON or CSV export. Up to 5 MB.",
          "additionalProperties": false
        },
        "packages": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "ecosystem",
              "name",
              "version"
            ],
            "properties": {
              "name": {
                "type": "string"
              },
              "version": {
                "type": "string",
                "description": "One exact version, not a range."
              },
              "ecosystem": {
                "type": "string",
                "description": "npm, PyPI, Maven, Go, crates.io, RubyGems, Packagist, NuGet, Hex or Pub."
              }
            },
            "additionalProperties": false
          },
          "maxItems": 1000
        },
        "technologies": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "name"
            ],
            "properties": {
              "name": {
                "type": "string",
                "description": "Such as nginx, PHP, WordPress or jQuery."
              },
              "version": {
                "type": "string"
              }
            },
            "additionalProperties": false
          },
          "maxItems": 500,
          "description": "Website technologies, as Wappalyzer or a person names them."
        }
      },
      "additionalProperties": false
    }
    arguments 72 lines
  • search unknown never probed

    Search the whole catalog by words: product, vendor, package, CVE ID, common vulnerability name, research metadata or description text. Best match first by default. Each result says which fields matched. When nothing matches, the reply suggests a broader query.

    mcp-tool

    {
      "type": "object",
      "required": [
        "q"
      ],
      "properties": {
        "q": {
          "type": "string",
          "description": "Words to search for, such as \"openssl\", \"log4j rce\" or \"exchange server\"."
        },
        "kev": {
          "type": "boolean",
          "description": "Only entries in the CISA KEV catalog."
        },
        "sort": {
          "enum": [
            "relevance",
            "published",
            "score",
            "epss",
            "priority",
            "activity",
            "modified"
          ],
          "type": "string",
          "default": "relevance"
        },
        "tech": {
          "type": "string",
          "description": "Only entries naming this vendor or vendor product, as a slug: apache, or apache/tomcat."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "since": {
          "type": "string",
          "description": "Only entries published on or after this date (YYYY-MM-DD)."
        },
        "until": {
          "type": "string",
          "description": "Only entries published before this date (YYYY-MM-DD)."
        },
        "cursor": {
          "type": "string",
          "description": "next_cursor from the previous page."
        },
        "vendor": {
          "type": "string",
          "description": "Exact vendor name, such as apache or microsoft."
        },
        "package": {
          "type": "string",
          "description": "Only entries naming this package, as ecosystem:name, such as npm:lodash or pypi:django."
        },
        "product": {
          "type": "string",
          "description": "Exact product name, such as log4j or exchange server."
        },
        "severity": {
          "type": "array",
          "items": {
            "enum": [
              "critical",
              "high",
              "medium",
              "low"
            ],
            "type": "string"
          },
          "description": "Only these severities."
        },
        "ecosystem": {
          "type": "string",
          "description": "Package ecosystem, such as npm, PyPI, Maven, Go or crates.io."
        },
        "exploited": {
          "type": "boolean",
          "description": "Only entries with reported exploitation (KEV, CISA SSVC, ENISA or VulnCheck KEV)."
        },
        "fix_available": {
          "type": "boolean",
          "description": "Only entries with a fixed version."
        },
        "modified_since": {
          "type": "string",
          "description": "Only entries whose merged record changed at or after this date (YYYY-MM-DD) or time (ISO 8601). Pass the newest modified value from the previous run."
        },
        "public_exploit": {
          "type": "boolean",
          "description": "Only entries with public exploit code."
        }
      },
      "additionalProperties": false
    }
    arguments 97 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 7faf23d8d1ff9267.

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