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.

Bill Of Materials Integrity

REMOTE · MCP-FACTORY.BOWLING-ANTHONY.WORKERS.DEV

Pure, bounded analysis of an explicit bill-of-materials graph: validates structure, finds missing...

0 this week 75 Trust /100

Last scanned (22 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

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 Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 615 tokens (~615/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 10 Oct 26 0
    • Stability: 0.93 → pass security
  • 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
  • 7 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 6 Sept 26 0

    First indexed and scored.

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 21 Nov 2026 · Probed https://mcp-factory.bowling-anthony.workers.dev/bill-of-materials-integrity/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=bowling-anthony.workers.dev CN=WE1,O=Google Trust Services,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA256 2de31afee4286b1013f05eeccc161d62
SANs: bowling-anthony.workers.dev, *.bowling-anthony.workers.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp-factory.bowling-anthony.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp-factory.bowling-anthony.workers.dev/bill-of-materials-integrity/mcp Verified 200
http (plaintext) http://mcp-factory.bowling-anthony.workers.dev/bill-of-materials-integrity/mcp Inconclusive 405
MCP tools · 1 exposed · ~170 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
bill_of_materials_integrity ~170

Pure, bounded analysis of an explicit bill-of-materials graph: validates structure, finds missing references, duplicate IDs, duplicate edges, and cycles (whole graph, even parts unreachable from the root), and - when the graph is completely clean - exactly explodes root quantity through every assembly level with exact-decimal arithmetic, aggregating shared components reached via different branches. No network access and no manufacturing/supplier certification: this checks the data you supply, not the real world. Price: 0.05 USDC per completed bounded job on Base.

NameTypeReqDescription
partsarrayyes–
quantitystringyesPositive exact decimal, <=12 integer digits, <=6 fraction digits.
rootstringyesID of the part to explode from. Must match one of parts[].id.

No output schema declared.

No examples provided.

Install

How do I install the Bill Of Materials Integrity MCP server?

Bill Of Materials Integrity is a hosted endpoint at https://mcp-factory.bowling-anthony.workers.dev/bill-of-materials-integrity/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 · mcp-factory.bowling-anthony.workers.dev

# add to Claude Code
claude mcp add --transport http com-mcpscores-bill-of-materials-integrity 'https://mcp-factory.bowling-anthony.workers.dev/bill-of-materials-integrity/mcp'
Common questions

What is the Bill Of Materials Integrity MCP server?

Bill Of Materials Integrity is an MCP server listed in the public MCP registry as com.mcpscores/bill-of-materials-integrity. Pure, bounded analysis of an explicit bill-of-materials graph: validates structure, finds missing... This page covers its hosted endpoint (https://mcp-factory.bowling-anthony.workers.dev/bill-of-materials-integrity/mcp).

Is the Bill Of Materials Integrity MCP server safe to use?

Bill Of Materials Integrity scores 75 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 Bill Of Materials Integrity MCP server expose?

Bill Of Materials Integrity exposes 1 tool: bill_of_materials_integrity. Their descriptions and schemas cost roughly 170 tokens of context every time the server is loaded.

Does the Bill Of Materials Integrity MCP server require authentication?

No. We connected to Bill Of Materials Integrity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Bill Of Materials Integrity MCP server still maintained?

Bill Of Materials Integrity is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Bill Of Materials Integrity MCP server?

VerifyMCP ran 12 checks on Bill Of Materials Integrity, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Bill Of Materials Integrity: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.