Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

it.elsas/security-intel

REMOTE · ELSAS.IT

Daily Ed25519-signed security intelligence for AI-agent stacks; CVEs & advisories, paid via x402.

Available components

0 this week 23 Trust /100

Last scanned (22 hours ago)

Scores higher than 6% of remote servers

Reachable. Last reached 23 Oct 2026.

Category Security

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Aug 26 0
    • Endpoint reachability: unreachable → not serving MCP ▼ security
    • HSTS header: unverified → fail ▼ security
    • TLS certificate: unverified → pass ▲ security
    • Transport: Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
  • 1 Aug 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 23 Oct 2026 · Probed https://elsas.it/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=elsas.it CN=YE2,O=Let's Encrypt,C=US 30 Sept 2026 29 Dec 2026 ECDSA 256 ECDSA-SHA384 5d7ef0337eca043a5117dc6ef350fe73473
SANs: elsas.it
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of elsas.it. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
it. present 51765 13 Verified
elsas.it. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://elsas.it/mcp HTTP error 404
http (plaintext) http://elsas.it/mcp HTTPS enforced 308 https://elsas.it/mcp
MCP tools · 11 exposed · ~2,041 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_affected ~565

Check your installed packages against recent security advisories. Pay-per-value: $0 when nothing affects your versions (status all_clear/verify is always free), otherwise priced per confirmed match via x402 — you only pay when you learn you are actually exposed. Zero-friction input: paste your dependency file straight into `lockfile` — no need to hand-extract package/version. Auto-detected formats: package-lock.json, yarn.lock, requirements.txt (== pins), poetry.lock, Pipfile.lock, go.mod, go.sum, Cargo.lock, and CycloneDX / SPDX JSON SBOMs. Or pass an explicit `components` list of {package, version, ecosystem?} (you may pass both — they are merged). Built for agents that poll on their own clock: pass `since` (a cursor) to match ONLY advisories first published after your last check, so a repeated poll is free until something NEW hits you — and you pay at most once per new exposure. The returned `cursor` is interchangeable with get_since's cursor; store it and pass it back next time. Use `min_severity` to ignore (and not pay for) matches below your threshold. Returns advisories that affect (or may affect) your versions, each with the primary-source URL so you can verify independently. Trust-safe: when a version range cannot be parsed, or an advisory is product-level (no version data), it is reported as "verify" rather than silently cleared. Pair with the signed report for an auditable trail.

NameTypeReqDescription
components––optional list of {package, version, ecosystem?}.
lockfile––optional raw lockfile or SBOM text — parsed server-side into components (exact pinned versions only). Auto-detected; combine with `components` if you like. Practical size limit ~1MB; for…
lockfile_type––optional hint/filename to force the parser (e.g. "go.mod", "requirements.txt", "cyclonedx") when auto-detect is ambiguous.
min_severity––optional floor — one of low|medium|moderate|high|critical. Matches below it are dropped (and not charged for).
previewboolean–if true, return only the shape (counts + max severity) used to quote a price — no advisory bodies. The gateway uses this; you do not need to set it.
since––optional cursor — only match advisories first published after it. Omit on the first call; pass the returned `cursor` thereafter.

Structured output declared, but exposes no named fields.

No examples provided.

check_cve ~125

Normalized, SIGNED verdict for a single CVE: CVSS (v3.1/v4.0, authoritative from NVD with OSV fallback), CISA-KEV exploitation status, and EPSS probability. PAID ($0.01 USDC via x402). Deterministic JSON; the response carries an Ed25519 SSHSIG signature (`_signature`) you can verify offline — unlike unsigned CVE APIs.

NameTypeReqDescription
cvestringyesa CVE id, e.g. "CVE-2021-44228".

Structured output declared, but exposes no named fields.

No examples provided.

check_package ~121

SIGNED vulnerability verdict for one package version (OSV.dev) with a CISA-KEV flag per matching advisory. PAID ($0.002 USDC via x402). Deterministic JSON + Ed25519 signature.

NameTypeReqDescription
ecosystem––OSV ecosystem (npm, PyPI, Go, crates.io, …). Inferred-as-given; pass it for precise matching.
namestringyespackage name (e.g. "lodash", "requests").
version––exact version to test against advisory ranges (recommended).

Structured output declared, but exposes no named fields.

No examples provided.

get_items ~206

Full bodies for items you discovered via `get_since` (PAID — pay-per-value, priced per delivered item via x402; $0 if none of the ids are found). `get_since` gives you a free index (id, title, severity, …) so you can decide what matters to you; `get_items` returns the actionable payload — affected ranges, primary sources, assessment and remediation — only for the ids you ask for. Each item carries the `report_id` of the signed report it was first published in: fetch that report via `get_sample_report(run_id=report_id)` to verify the Ed25519 signature yourself.

NameTypeReqDescription
idsarrayyesitem ids (from get_since's index) to retrieve.
previewboolean–if true, return only the shape (count + max severity) used to quote a price — no bodies. The gateway uses this; you do not need to set it.

Structured output declared, but exposes no named fields.

No examples provided.

get_sample_report ~136

FREE preview — yesterday's full report, identical in format and signing to the paid `get_today`. Call this first to see exactly what you get before paying: real curated security items, severities, recommendations, and an Ed25519 signature you can verify (https://elsas.it/docs#verify). The only difference from get_today is freshness (this is the previous day's report).

NameTypeReqDescription
run_id––Optional specific report id (from `list_available`). Defaults to the most recent report that is not today's paid one.
stack––Optional comma-separated filter (same stacks as get_today).

Structured output declared, but exposes no named fields.

No examples provided.

get_since ~180

Delta feed for agents that poll on their own clock: what's new since you last checked. Free. Pass the `cursor` from your previous call (omit on first call); poll as often as you like. Returns a lightweight index of new items — id, title, item_type, CVE id, severity, the signed report_id each was published in, and published_at — plus a new `cursor` and `count`. count == 0 means nothing new since you last looked. To get the full bodies (affected ranges, sources, assessment, remediation) for what's new, call the paid get_today (or check_affected to test your own deps). Optional `stack` filters by relevant_for tags (same as get_today). Returns: {cursor, count, index}.

NameTypeReqDescription
cursor–––
stack–––

Structured output declared, but exposes no named fields.

No examples provided.

get_today ~198

Today's full curated security report for the MCP / AI-agent ecosystem (PAID — $0.10 USDC, charged automatically via x402 on Base; no account needed). Returns the latest signed, independently cross-validated digest of security incidents, advisories (CVE/GHSA/OSV/KEV) and notable changes affecting MCP servers, agents and their dependencies — each item with severity, why it matters, and a recommended action. Every report is Ed25519-signed; verify it yourself (see https://elsas.it/docs#verify). Try it free first with `get_sample_report` (yesterday's report, identical format).

NameTypeReqDescription
stack––Optional comma-separated filter, e.g. "devops,security", to return only relevant items. Stacks: devops, coding, qa, finance, healthcare, legal, content, security, knowledge.

Structured output declared, but exposes no named fields.

No examples provided.

is_exploited ~137

Fast boolean: is this CVE known-exploited? SIGNED. `exploited` is driven by CISA-KEV (authoritative evidence of in-the-wild exploitation). EPSS (predictive probability) is included as a secondary signal but does NOT set the boolean — we report observed exploitation, not a forecast. PAID ($0.001 USDC via x402). Args: cve — e.g. "CVE-2024-3094". Returns: signed {exploited, kev, epss, basis, _signature}.

NameTypeReqDescription
cvestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_available ~57

List available validated reports. Cheap to call, returns no full bodies. Only shows reports that passed validation (signed, TL;DR, no AUTO-CORRECTED). The current (newest) report is excluded — it's the paid product.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

scan_dependencies ~197

Bulk OSV scan of a whole lockfile/SBOM — every dependency checked against OSV.dev, KEV-flagged. SIGNED. PAID pay-per-value: billed per vulnerability HIT (dynamic x402, $0 when the whole tree is clean, capped at $0.10). Unlike `check_affected` (matches your deps against elsas's curated CURRENT advisory set), this runs a FULL OSV scan of the entire dependency graph.

NameTypeReqDescription
lockfilestringyesraw lockfile/SBOM text — package-lock.json, yarn.lock, requirements.txt, poetry.lock, Pipfile.lock, go.mod/go.sum, Cargo.lock, CycloneDX/SPDX JSON (auto-detected, ~1MB cap).
lockfile_type––optional parser hint/filename.
previewboolean–gateway-internal — returns only {affected, max_severity} for pricing.

Structured output declared, but exposes no named fields.

No examples provided.

search_cves ~119

SIGNED keyword search over the NVD CVE corpus, each result enriched with a CISA-KEV flag. PAID ($0.01 USDC via x402). Deterministic JSON + Ed25519 signature.

NameTypeReqDescription
keywordstringyesfree-text (matched by NVD keywordSearch), e.g. "langchain rce".
limitinteger–max results (1–50, default 20).
since––optional ISO date (YYYY-MM-DD); only CVEs published on/after it.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the it.elsas/security-intel MCP server?

it.elsas/security-intel is a hosted endpoint at https://elsas.it/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · elsas.it

# add to Claude Code
claude mcp add --transport http it-elsas-security-intel 'https://elsas.it/mcp'
Common questions

What is the it.elsas/security-intel MCP server?

it.elsas/security-intel is an MCP server listed in the public MCP registry as it.elsas/security-intel. Daily Ed25519-signed security intelligence for AI-agent stacks; CVEs & advisories, paid via x402. This page covers its hosted endpoint (https://elsas.it/mcp).

Is the it.elsas/security-intel MCP server safe to use?

it.elsas/security-intel scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the it.elsas/security-intel MCP server expose?

it.elsas/security-intel exposes 11 tools: get_today, get_sample_report, list_available, check_affected, get_since, and 6 more. Their descriptions and schemas cost roughly 2,041 tokens of context every time the server is loaded.

Does the it.elsas/security-intel MCP server require authentication?

Its publisher declares no required credentials for it.elsas/security-intel. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the it.elsas/security-intel MCP server still maintained?

it.elsas/security-intel is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.