Security Intel

it.elsasPublished by elsas.itOfficial publisherv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote MCP server serving daily Ed25519-signed security intelligence for AI-agent stacks: CVE and advisory lookups, package vulnerability checks, and a paid-0

What you can do
Look up whether a CVE is known-exploited, and get CVSS, KEV and EPSS data for a CVE or a package version, or search CVEs by keyword. Scan a whole lockfile for known vulnerabilities, with pay-per-vulnerability pricing and no charge when clean. Retrieve the daily curated, cross-validated security digest. Every response carries an embedded Ed25519 signature block so the assistant or user can verify authenticity offline against a pinned public key.
When to use it
Useful when an assistant needs current vulnerability intelligence while reviewing dependencies, triaging CVEs, or checking whether a package version is affected, and when tamper-evident, independently verifiable answers matter more than a free unsigned feed.
Requirements
A remote MCP endpoint at elsas.it over streamable HTTP; no local package, environment variables or headers are declared. Calls are paid per request with x402 in USDC on Base, so a funded crypto wallet is needed; no account is required. Offline verification of signatures needs openssh-client and python3, or the provider's Node or Python verifier library.
Before you install
Each tool call costs money in USDC on Base, from sub-cent lookups up to a higher-priced daily digest, and lockfile scans are billed per vulnerability found. Payment is accountless, so the wallet is the identity and spending should be capped. The server returns signed security data, but the curation pipeline and scoring are not published, so treat verdicts as one input and verify signatures before relying on them.

Installation

In SourceWeft

  1. Open Security Intel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/it.elsas%2Fsecurity-intel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "security-intel": {
      "type": "http",
      "url": "https://elsas.it/mcp"
    }
  }
}

README

elsas-verify

Independently verify the daily security-intelligence reports published by elsas.it — offline, with no trust in our servers and no access to our keys.

elsas.it is signed security intelligence for AI agents, served over MCP and paid per call with x402 (USDC on Base — accountless, your wallet is your identity). Two shapes:

  • Atomic primitives (high-frequency, sub-cent): is_exploited (is this CVE in CISA-KEV? $0.001), check_cve (CVSS + KEV + EPSS, $0.01), check_package (OSV verdict for one package@version, $0.002), search_cves ($0.01), scan_dependencies (whole-lockfile OSV scan, pay-per-vuln, free when clean).
  • Premium digest: get_today — the daily curated, cross-validated report ($0.10).

Every response is Ed25519-signed (SSHSIG, namespace elsas-report) — so you can prove it's authentic and untampered without trusting our servers and without our keys. That's the differentiator: unsigned CVE APIs ask you to trust them; we let you verify. This repo is everything you need to do that offline.

Don't trust us — verify.

Verify in 30 seconds

Requirements: openssh-client (ssh-keygen) and python3 — present on any Linux/macOS. No install, no network needed for the verification itself.

bash
git clone https://github.com/romans-repos/elsas-verify.gitcd elsas-verify./verify-report.sh examples/sample-report.json allowed_signers

Expected output:

VALID: authentic & untampered  Signer:  [email protected]  Hash:    sha256:…Good "elsas-report" signature for [email protected] with ED25519 key SHA256:gLVNll72kb8Iyni2vNMR6oHGqVh0Ynz+lBMhbS+cSa4

Verify a live report

bash
# Fetch the current public sample + its detached signaturecurl -s https://elsas.it/sample                          > report.jsoncurl -s https://elsas.it/.well-known/report.json.sig     > report.json.sig# Verify against the pinned key in this repo./verify-report.sh report.json allowed_signers

You can also verify by hand with stock OpenSSH:

bash
ssh-keygen -Y verify \  -f allowed_signers \  -I [email protected] \  -n elsas-report \  -s report.json.sig < report.json

Verify an atomic-tool verdict

The atomic tools return a JSON verdict with an embedded _signature block (signed_payload = the exact signed bytes; signature = an armored SSHSIG). Verify it offline — by shell, or with the drop-in library for your language:

bash
# shell (ssh-keygen + python3 stdlib)./verify-verdict.sh examples/sample-verdict.json allowed_signers
js
// Node — zero dependencies (built-in crypto). npm i @elsas/verifyimport { verifyVerdict } from '@elsas/verify';const { ok, reason } = verifyVerdict(verdict);   // pinned elsas key, offlineif (!ok) throw new Error(`unverified elsas verdict: ${reason}`);
python
# Python — pip install elsas-verify  (only dep: cryptography)from elsas_verify import verify_verdictok, info = verify_verdict(verdict)assert ok, info["reason"]

Each verifier does two independent checks: (1) the verdict body matches the signed bytes (tamper-evidence), and (2) the SSHSIG verifies under the pinned elsas key (a signature by any other key is rejected). No network call is needed to verify.

Trust model

  • Signatures use SSHSIG (Ed25519) via ssh-keygen -Y sign. Verification is offline and zero-trust: you hold the payload, you verify locally.
  • The root of trust is allowed_signers — our public key, identity-pinned to [email protected]. A substituted signers file with a different key is rejected by the -I flag.
  • Confirm the pinned key independently against the live copy:
    bash
    curl -s https://elsas.it/.well-known/allowed_signers
    Key fingerprint: SHA256:gLVNll72kb8Iyni2vNMR6oHGqVh0Ynz+lBMhbS+cSa4
  • Each report also carries a _integrity.content_hash (sha256 over the canonical JSON) for tamper evidence — see SIGNATURE-VERIFY.md.

What's in here

FilePurpose
verify-report.shDependency-free report verifier (ssh-keygen + python3 stdlib)
verify-verdict.shDependency-free atomic-verdict verifier
packages/node/@elsas/verify — zero-dep Node library + CLI
packages/python/elsas-verify — Python library + CLI (pip install)
allowed_signersOur public signing key — the root of trust
schemas/report-v4.jsonJSON schema of a report payload
examples/sample-report.json (+ .sig)A real, signed report to verify against
examples/sample-verdict.jsonA real, signed atomic-tool verdict to verify against
SIGNATURE-VERIFY.mdThe full verification recipe and trust details

What's not here

This repo is the verification surface only. The curation pipeline, scoring prompts, relevance taxonomy, infrastructure and any operational configuration are intentionally not published — they are neither needed to verify a report nor useful to a third party. Verifiability does not require disclosing how the sausage is made; it requires that the result is checkable. That's what this is.

License

Tooling in this repository is released under the MIT License. Report payloads themselves carry their own license terms inside the report (_integrity._license_coverage).

Service: https://elsas.it · Docs: https://elsas.it/docs · Sample: https://elsas.it/sample

Source: README.md at commit ee6e403

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts