Skip to content

CEA Digital B2A Fulfillment Factory MCP server

io.ceadigital/b2a-fulfillment-factoryceadigital.iostreamable-httpv1.0.0Scanned

High-speed institutional API data gateway for SEC EDGAR, OSV CVE, FDIC, USGS, NPI, and GCP Catalog.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 4
  • Can send data out · 0
  • No findings

With Anlyon

2 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.dev only lists and labels, and these labels are the same either way.

What the CEA Digital B2A Fulfillment Factory MCP server can do

The CEA Digital B2A Fulfillment Factory MCP server is published by ceadigital.io, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: security_cve_audit and package_health_pulse), but cannot delete data. 2 tools only read.

1 tool reads private data (vault_knowledge_search); 4 tools bring in text other people can write (gcp_catalog_search, vault_knowledge_search, security_cve_audit and 1 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Nov 5, 2026, version 1.0.0.

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.

4 tools

Changes things 2Claude Code: ask
  • package_health_pulseParallel health pulse inspection across NPM and PyPI ecosystems.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
    Parallel health pulse inspection across NPM and PyPI ecosystems.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • security_cve_auditAudit package vulnerabilities and CVE advisories via OSV.dev database.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
    Audit package vulnerabilities and CVE advisories via OSV.dev database.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
Only reads 2Show 2 read-only tools

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 outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http b2a-fulfillment-factory https://ceadigital.io/mcp
claude mcp add --transport http b2a-fulfillment-factory https://ceadigital.io/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__b2a-fulfillment-factory__gcp_catalog_search",
      "mcp__b2a-fulfillment-factory__vault_knowledge_search"
    ],
    "ask": [
      "mcp__b2a-fulfillment-factory__security_cve_audit",
      "mcp__b2a-fulfillment-factory__package_health_pulse"
    ],
    "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 b2a-fulfillment-factory. Review it before you use it.

Capability tags behind 4 rules
  • mcp__b2a-fulfillment-factory__gcp_catalog_search untrusted-input
  • mcp__b2a-fulfillment-factory__vault_knowledge_search private-data, untrusted-input
  • mcp__b2a-fulfillment-factory__security_cve_audit untrusted-input
  • mcp__b2a-fulfillment-factory__package_health_pulse 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://anlyon.dev/api/v1/servers/io.ceadigital/b2a-fulfillment-factory/verify?hash=c5df2744ee5b76fd1907989fee2dcc758b64df6bf5197481819d6304ff37249d" | jq -e '.changed == false'

Pinned hash c5df2744ee5b, from Nov 5, 2026, 17:18 UTC.

Watch

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

https://anlyon.dev/servers/io.ceadigital/b2a-fulfillment-factory/changes.xml

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

Badge

anlyon.dev badge for io.ceadigital/b2a-fulfillment-factory
[![anlyon.dev](https://anlyon.dev/badge/io.ceadigital/b2a-fulfillment-factory.svg)](https://anlyon.dev/servers/io.ceadigital/b2a-fulfillment-factory)

Source: MCP Registry. Synced Nov 5, 2026, 17:17 UTC.

CEA Digital B2A Fulfillment Factory MCP server: questions and answers

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

Is the CEA Digital B2A Fulfillment Factory MCP server safe?

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

Can the CEA Digital B2A Fulfillment Factory MCP server delete data?

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

Can the CEA Digital B2A Fulfillment Factory 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 CEA Digital B2A Fulfillment Factory MCP server have?

4 tools: 2 write, 2 read. security_cve_audit, package_health_pulse, gcp_catalog_search and vault_knowledge_search.

Does the CEA Digital B2A Fulfillment Factory MCP server send data to outside services?

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

Has the CEA Digital B2A Fulfillment Factory MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 5, 2026.