Skip to content

Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server

com.ppftec/shieldbookppftec.comstreamable-httpv1.0.2Scanned

EU Cyber Resilience Act information: scope check, reporting deadlines, SBOM summary, security.txt

9 tools: 8 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 8 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • 1 finding

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

8 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server can do

The Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server is published by ppftec.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (8 tools: cra_scope_questions, cra_scope_check, sbom_ci_snippet, security_txt_generate and 4 more), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (sbom_vulnerabilities).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 21, 2026, version 1.0.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 8Claude Code: ask
  • cra_report_draftFits when a manufacturer is preparing the EU Cyber Resilience Act Article 14 reports for an actively exploited vulnerability or a severe incident and wants to know what each report…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fits when a manufacturer is preparing the EU Cyber Resilience Act Article 14 reports for an actively exploited vulnerability or a severe incident and wants to know what each report must contain. Takes the event type, the awareness time and any facts known so far (product, Member States, nature, measures, sensitivity, severity and impact, malicious actor, fix, root cause, mitigations). Returns, for the early warning, the notification and the final report, the due time, each content item the CRA asks for with its article point, the facts given for it and what is still missing, plus the duty to inform users (Art. 14(8)). Does not fill or submit the ENISA Single Reporting Platform form and does not decide whether an event must be reported.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Draft the content of CRA Article 14 reports
  • cra_reporting_deadlinesFits when a manufacturer has become aware of an actively exploited vulnerability or a severe incident affecting the security of a product with digital elements and asks when the EU…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fits when a manufacturer has become aware of an actively exploited vulnerability or a severe incident affecting the security of a product with digital elements and asks when the EU Cyber Resilience Act Article 14 reports are due. Takes the event type and the awareness time (ISO 8601 with zone), optionally when a fix became available or when the 72-hour notification was sent. Returns the due times (UTC) of the 24-hour early warning, the 72-hour notification and the final report, the article for each and how to submit on ENISA's Single Reporting Platform. Does not cover GDPR or NIS2 breach deadlines and does not decide whether an event must be reported.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Compute CRA Article 14 reporting deadlines
  • cra_scope_checkFits when the user asks whether the EU Cyber Resilience Act (Regulation (EU) 2024/2847) applies to a software or hardware product, or which CRA product class it falls into.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fits when the user asks whether the EU Cyber Resilience Act (Regulation (EU) 2024/2847) applies to a software or hardware product, or which CRA product class it falls into. Start with answers {}; each call returns the next question, or the result once all answers are given: in scope / outside scope / needs a closer reading, the provisional class (default, important class I or II, critical) and the cited articles (Art. 2, 3, 7, Annex III/IV). Does not cover other laws (NIS2, GDPR, AI Act); not a conformity assessment or legal advice.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Check whether a product is in scope of the CRA
  • cra_scope_questionsFits when the user wants to see every question and answer option of the Shieldbook scope check for the EU Cyber Resilience Act at once, for example to prepare answers.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fits when the user wants to see every question and answer option of the Shieldbook scope check for the EU Cyber Resilience Act at once, for example to prepare answers. Returns the questions, their options, the ruleset version and its verification date. Gives no result; for a guided check that returns one question at a time and then the result: cra_scope_check.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List the CRA scope-check questions
  • cra_technical_documentation_checklistFits when a manufacturer wants to know what the EU Cyber Resilience Act technical documentation (Annex VII) must contain and which conformity assessment routes a product class allo…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fits when a manufacturer wants to know what the EU Cyber Resilience Act technical documentation (Annex VII) must contain and which conformity assessment routes a product class allows (Art. 32). Optional inputs: the product class (default, important class I or II, critical) and whether the product includes hardware. Returns the eight Annex VII items with their article points, the keeping, language and CE-marking duties, and the conformity routes. Does not review documents and is not a conformity assessment; for the product class itself: cra_scope_check.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: List what the CRA technical documentation must contain
  • sbom_ci_snippetFits when the user wants their CI to produce an SBOM automatically for an npm, pip, Poetry, Maven, Gradle, Go or Cargo project on GitHub Actions or GitLab CI.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Fits when the user wants their CI to produce an SBOM automatically for an npm, pip, Poetry, Maven, Gradle, Go or Cargo project on GitHub Actions or GitLab CI. Returns a ready-to-commit workflow or job that writes a CycloneDX JSON SBOM, with actions pinned to commit SHAs and the generator version. Covers no other CI systems or ecosystems; for reading an existing SBOM: sbom_summarize.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Generate SBOM steps for CI
  • sbom_vulnerabilitiesFits when the user shares a CycloneDX or SPDX JSON SBOM and asks which components have known vulnerabilities.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Fits when the user shares a CycloneDX or SPDX JSON SBOM and asks which components have known vulnerabilities. Sends only the package URLs (type, name, version) of the components to the public OSV.dev database and returns, per affected component, the advisory IDs, and for up to 25 advisories the summary, aliases (for example CVE IDs) and fixed versions, with the OSV source. At most 1,000 components with versioned package URLs per call; nothing is stored. A lookup by package identifier, not proof that the vulnerable code is used; no match does not mean no vulnerability. For the SBOM's contents and missing fields: sbom_summarize.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • title: Look up known vulnerabilities for SBOM components
  • security_txt_generateFits when the user wants to publish a contact for vulnerability reports on a website, or to create or check a security.txt file (RFC 9116).1 finding

    Why it is in this group

    • The name "security_txt_generate" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "security_txt_generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "security_txt_generate" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Fits when the user wants to publish a contact for vulnerability reports on a website, or to create or check a security.txt file (RFC 9116). Takes contact URIs (mailto:, https:, tel:), an optional expiry date and optional fields (policy, encryption key, acknowledgments, languages, canonical URL, hiring). Returns the file text, or a message per invalid field. Does not write a full vulnerability disclosure policy or check a live website.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Generate a security.txt file
Only reads 1Show 1 read-only tool
  • sbom_summarizeFits when the user shares a CycloneDX or SPDX JSON SBOM (software bill of materials) and wants to know what it lists or whether basic fields are missing.No findings

    Why it is in this group

    • The name "sbom_summarize" says "summarize": a word for reading.
    Description, as the server wrote it
    Fits when the user shares a CycloneDX or SPDX JSON SBOM (software bill of materials) and wants to know what it lists or whether basic fields are missing. Returns format, spec version, product name and version, component count, up to 100 component names and findings on missing fields. Limits: 2,000,000 characters, 64 nesting levels, 50,000 components; processed in memory and not stored. Does not read XML or tag-value SBOMs and does no full schema validation, vulnerability (CVE) scanning or licence check.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Summarize an SBOM

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://shieldbook.ppftec.com/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://shieldbook.ppftec.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://shieldbook.ppftec.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "security_txt_generate" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "security_txt_generate" says "generate": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http shieldbook https://shieldbook.ppftec.com/mcp
claude mcp add --transport http shieldbook https://shieldbook.ppftec.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__shieldbook__sbom_summarize"
    ],
    "ask": [
      "mcp__shieldbook__cra_scope_questions",
      "mcp__shieldbook__cra_scope_check",
      "mcp__shieldbook__sbom_ci_snippet",
      "mcp__shieldbook__security_txt_generate",
      "mcp__shieldbook__cra_reporting_deadlines",
      "mcp__shieldbook__cra_report_draft",
      "mcp__shieldbook__cra_technical_documentation_checklist",
      "mcp__shieldbook__sbom_vulnerabilities"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shieldbook. Review it before you use it.

Capability tags behind 1 rule
  • mcp__shieldbook__sbom_vulnerabilities untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.ppftec/shieldbook/verify?hash=3e7532b13e3880a371f3c4aa112c4c04304770c955e089a850375baa0c1d1f29" | jq -e '.changed == false'

Pinned hash 3e7532b13e38, from Nov 21, 2026, 13:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.ppftec/shieldbook/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.ppftec/shieldbook
[![Anlyon Radar](https://radar.anlyon.com/badge/com.ppftec/shieldbook.svg)](https://radar.anlyon.com/servers/com.ppftec/shieldbook)

Source: MCP Registry. Synced Nov 21, 2026, 13:17 UTC.

Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server have?

9 tools: 8 write, 1 read. cra_scope_questions, cra_scope_check, sbom_ci_snippet, security_txt_generate, cra_reporting_deadlines, cra_report_draft, cra_technical_documentation_checklist, sbom_vulnerabilities and 1 more.

Does the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Shieldbook – EU Cyber Resilience Act (CRA), SBOM MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.