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.

Bunzee

REMOTE · BUNZEE.AI

Turn your app idea into IA, wireframes, PRD, style guides, and dev specs for coding agents.

Available components

0 this week 36 Trust /100

Last scanned (12 hours ago)

Scores higher than 19% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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 Security89
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
  • Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
  • Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified

Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.

What we tested

Checks we ran (5)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC

Checks we could not complete (6)

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.

  • Transport in Transport & Reachability (scores 0 for this)Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema blocked by authentication: the endpoint requires auth we don't have to read it.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
  • Capabilities in Capabilities (scores 0 for this)Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

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.

  • 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
  • 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
  • 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
  • 27 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 21 Nov 2026 · Probed https://bunzee.ai/mcp-server

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.bunzee.ai CN=Amazon RSA 2048 S24,O=Amazon,C=US 6 Nov 2026 24 May 2027 RSA 2048 SHA256-RSA 43df15a87f2ac992366843642f23798f
SANs: *.bunzee.ai, bunzee.ai
CN=Amazon RSA 2048 S24,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 8 Jul 2026 7 Jul 2029 RSA 2048 SHA256-RSA 56341b70d44850c618a59ee8d02502a3e354a24c
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of bunzee.ai. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814 8 Verified
bunzee.ai. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On connection
HTTP status 401
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy frame-ancestors 'self' https://buildhop.io https://www.buildhop.io; script-src 'self' 'nonce-uptB290OD4UOSWQ+I90ecA==' 'strict-dynamic' 'unsafe-inline' accounts.google.com cdn.jsdelivr.net cloud.umami.is d1f8f9xcsvx3ha.cloudfront.net cdn.tailwindcss.com unpkg.com *.googletagmanager.com *.google-analytics.com *.clarity.ms *.doubleclick.net *.googleadservices.com geolocation-db.com logo.clearbit.com client.crisp.chat; style-src 'self' 'unsafe-inline' fonts.googleapis.com cdnjs.cloudflare.com accounts.google.com client.crisp.chat; connect-src 'self' http://127.0.0.1:3000 https://new-great-test.bunzee.ai https://bunzee.ai https://geolocation-db.com https://accounts.google.com https://gateway.umami.is https://www.google.com https://www.google-analytics.com https://*.doubleclick.net https://*.googleadservices.com https://*.clarity.ms https://*.google-analytics.com https://*.googlesyndication.com https://*.onfastspring.com https://*.fastspring.com https://d1f8f9xcsvx3ha.cloudfront.net https://d20jzv1ghtxgkk.cloudfro
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://bunzee.ai/mcp-server Auth required 401
http (plaintext) http://bunzee.ai/mcp-server HTTPS enforced 301 https://bunzee.ai:443/mcp-server
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the Bunzee MCP server?

Bunzee is a hosted endpoint at https://bunzee.ai/mcp-server, 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 · bunzee.ai

# add to Claude Code
claude mcp add --transport http ai-bunzee-bunzee 'https://bunzee.ai/mcp-server'
Common questions

What is the Bunzee MCP server?

Bunzee is an MCP server listed in the public MCP registry as ai.bunzee/bunzee. Turn your app idea into IA, wireframes, PRD, style guides, and dev specs for coding agents. This page covers its hosted endpoint (https://bunzee.ai/mcp-server).

Is the Bunzee MCP server safe to use?

Bunzee scores 36 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.

Does the Bunzee MCP server require authentication?

Yes. Bunzee asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Bunzee MCP server still maintained?

Bunzee 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 Bunzee MCP server?

VerifyMCP ran 5 checks on Bunzee, covering TLS certificate, Authorization, HTTPS, HSTS header and 1 more. 6 items could not be completed, a gap on our side rather than a finding about Bunzee: Transport, Schema quality, Stability, Tool coverage and 2 more. 6 categories score 0 for that reason, because we only credit what we can confirm. 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.