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

security-intel

https://security.datakoot.com

Registry code: b11a45c8db4a8e92

api record

Security Intel: vulnerability intelligence for AI agents — CVE lookups enriched with real-world exploitation signal (NVD + CISA Known-Exploited + EPSS), per-package known vulnerabilities and whole-manifest dependency audits (OSV), plus a live feed of what's actively exploited (known_exploited) and exploit-probability scoring (epss_score). Call audit_dependencies before trusting a project's dependency tree; use known_exploited + epss_score to prioritize what to patch first.

endpoint
https://security.datakoot.com/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 security-intel live?
Yes — it answered the hub's last check (checked 5m ago). It answered 100% of checks over the last 30 days.
Is security-intel free to use?
Yes — the hub reached it with no key and no payment.
What tools does security-intel have?
5 tools: package_vulnerabilities, epss_score, cve_lookup, audit_dependencies, known_exploited.
Is security-intel 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 99.4%· all time 99.4%

latency
80ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 480 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • look up a cve
  • audit a dependency manifest for vulnerabilities
  • check if a cve is actively exploited
  • get exploit probability scores
takes → gives
text, code → data
tools
5 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

_ what it can do 5 tools
1 open 4 never probed 1 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.

  • known_exploited reads open 5m ago

    Check whether a CVE is on the CISA Known Exploited Vulnerabilities (KEV) catalog — confirmed exploited in the wild — or list the most recently added exploited vulnerabilities. Pass cve_id to check one; omit it to list recent (optionally filter by vendor/product, or ransomware_only). Source: CISA KEV, updated ~daily.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "limit": {
          "type": "number",
          "description": "When listing, how many newest entries to return (default 20, max 100)."
        },
        "cve_id": {
          "type": "string",
          "description": "Optional. Check a single CVE, e.g. CVE-2021-44228."
        },
        "vendor": {
          "type": "string",
          "description": "Optional. Filter by vendor or product name substring."
        },
        "ransomware_only": {
          "type": "boolean",
          "description": "Optional. Only vulns CISA links to known ransomware campaigns."
        }
      }
    }
    arguments 22 lines
  • package_vulnerabilities reads unknown 16h ago

    List known vulnerabilities for a software package (optionally a specific version) via OSV. Ecosystems: npm, pypi, cargo, go, maven, rubygems, nuget, composer, pub, hex.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ecosystem",
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Exact package name as published in that registry, e.g. lodash for npm, requests for pypi."
        },
        "version": {
          "type": "string",
          "description": "Optional; if given, only vulns affecting that version are returned"
        },
        "ecosystem": {
          "type": "string",
          "description": "Package registry to look in. One of: npm, pypi, cargo, go, maven, rubygems, nuget, composer, pub, hex."
        }
      }
    }
    arguments 21 lines
  • epss_score reads unknown 5m ago

    Get the EPSS exploit-probability score (0-1) and percentile for one or more CVEs — the likelihood each is exploited in the next 30 days. Use it to prioritize patching. Pass cve_id for one, or cve_ids (array or comma-separated) for many. Source: FIRST.org EPSS.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "cve_id": {
          "type": "string",
          "description": "A single CVE id."
        },
        "cve_ids": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Multiple CVE ids (or pass a comma-separated string)."
        }
      }
    }
    arguments 17 lines
  • cve_lookup reads unknown 16h ago

    Look up a CVE by ID and get a compact summary: description, CVSS score & severity, vector, CWE weakness, publish date, references — plus whether it is on the CISA Known-Exploited list (actively exploited in the wild) and its EPSS exploit-probability. Sources: NVD (NIST), CISA KEV, FIRST EPSS.

    mcp-tool

    {
      "type": "object",
      "required": [
        "cve_id"
      ],
      "properties": {
        "cve_id": {
          "type": "string",
          "description": "CVE identifier, e.g. CVE-2021-44228 (case-insensitive; a bare 2021-44228 also works)."
        }
      }
    }
    arguments 12 lines
  • audit_dependencies reads unknown 5m ago

    Audit a whole dependency manifest for known vulnerabilities in one call. Paste a package.json (as 'manifest'), or pass a 'dependencies' array of {name, version} objects. Returns per-package findings and a summary. Ecosystem defaults to npm.

    mcp-tool

    {
      "type": "object",
      "required": [],
      "properties": {
        "manifest": {
          "type": "string",
          "description": "Raw package.json contents"
        },
        "ecosystem": {
          "type": "string",
          "description": "Package registry for the dependencies: npm (default), pypi, cargo, go, maven, rubygems, nuget, composer, pub, or hex."
        },
        "dependencies": {
          "type": "array",
          "items": {
            "type": "object"
          },
          "description": "[{name, version}] entries"
        }
      }
    }
    arguments 21 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 b11a45c8db4a8e92.

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

_ also on datakoot.com 10 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

2 more sit on this domain. All of them.