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.

Jaybird Digital

REMOTE · JAYBIRDDIGITAL.COM

Build and host a website from the chat, with no account or API key, and get a live address to show.

67 Trust /100

Last scanned (10 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Documents and Files

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 Security66
Transport & Reachability100
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1186 tokens (~148/item across 8 items; 8 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 Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 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
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +5
    • Tool “delete_website” rewrote its description, which is the text the model reads security
    • Tool “delete_website_file” rewrote its description, which is the text the model reads security
    • Tool “read_website_file” rewrote its description, which is the text the model reads security
    • Tool “save_website_files” rewrote its description, which is the text the model reads security
    • Tool “search_domains” rewrote its description, which is the text the model reads security
    • Tool “list_sites” rewrote its description, which is the text the model reads security
    • Tool “start_website” rewrote its description, which is the text the model reads security
    • Tool “save_website_files” is now declared destructive security
    • Schema quality: 71 → 86 ▼ functional
    • Schema quality: pass → fail ▼ functional
    • Tool coverage: 14% → 100% ▲ functional
    • Tool coverage: 14% → 71% ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • Schema quality: fair → excellent functional
    • Schema quality: fair → good functional
    • Server version: 1.3.0 → 1.3.1 functional
    • Server version: 1.2.0 → 1.3.0 functional
    • Server version: 1.1.0 → 1.2.0 functional
    • Server version: 1.0.1 → 1.1.0 functional
    • New tool “list_website_files” functional
    • New tool “list_sites” functional
    • “delete_website_file” reworded the description of “path” cosmetic
    • “read_website_file” reworded the description of “path” cosmetic
    • “save_website_files” reworded the description of “files” cosmetic
    • “search_domains” reworded the description of “query” cosmetic
    • “start_website” reworded the description of “about” cosmetic
    • “start_website” reworded the description of “businessName” cosmetic
    • “delete_website” reworded the description of “editKey” cosmetic
    • “delete_website” reworded the description of “websiteId” cosmetic
    • “delete_website_file” reworded the description of “editKey” cosmetic
    • “delete_website_file” reworded the description of “websiteId” cosmetic
    • “read_website_file” reworded the description of “editKey” cosmetic
    • “read_website_file” reworded the description of “websiteId” cosmetic
    • “save_website_files” reworded the description of “editKey” cosmetic
    • “save_website_files” reworded the description of “websiteId” cosmetic
    • “delete_website” made “editKey” optional cosmetic
    • “delete_website_file” made “editKey” optional cosmetic
    • “read_website_file” made “editKey” optional cosmetic
    • “save_website_files” made “editKey” optional cosmetic
  • 2 Nov 26 61

    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 5 Nov 2026 · Probed https://jaybirddigital.com/api/start/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=jaybirddigital.com CN=WE1,O=Google Trust Services,C=US 10 Oct 2026 8 Jan 2027 ECDSA 256 ECDSA-SHA256 8b5d91108249220c0e1e8b07be521b49
SANs: jaybirddigital.com, dev.jaybirddigital.com, *.dev.jaybirddigital.com
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 secure

Validation of jaybirddigital.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
jaybirddigital.com. present 2371 13 Verified
jaybirddigital.com. Verified address RRset verified with the apex keys
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
strict-transport-security max-age=15552000; includeSubDomains
content-security-policy default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self' 'sha256-BaHQAiZX2xJwerUapsqshTbXoylajty16zg7HPulCp0=' https://js.stripe.com https://*.js.stripe.com https://connect-js.stripe.com https://challenges.cloudflare.com https://static.cloudflareinsights.com; style-src 'self' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: blob: https:; media-src 'self' blob: https:; connect-src 'self' https://*.supabase.co wss://*.supabase.co https://api.stripe.com https://cloudflareinsights.com; frame-src 'self' https:; report-uri /api/csp-report
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self "https://js.stripe.com" "https://connect-js.stripe.com")

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://jaybirddigital.com/api/start/mcp Verified 200
http (plaintext) http://jaybirddigital.com/api/start/mcp HTTPS enforced 301 https://jaybirddigital.com/api/start/mcp
MCP tools · 8 exposed · ~1,128 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
delete_website ~119

Permanently deletes a whole website: every file, its address and its keep link. It cannot be undone. To remove one file instead, use delete_website_file. A website with a plan is refused with has_a_plan; the person removes it from their dashboard.

NameTypeReqDescription
editKeystring–The editKey start_website returned, which proves the website is the caller's. Leave it out for a website in the connected account.
websiteIdstringyesThe websiteId start_website returned, or one list_sites shows.

No output schema declared.

No examples provided.

delete_website_file ~183

Removes one saved file from a website, then checks the remaining pages against the rules start_website returned, and returns the same report as save_website_files. Other files stay. A path that is not saved fails with no_such_file. Removing index.html leaves the website with no home page until one is saved. To delete the whole website, use delete_website.

NameTypeReqDescription
editKeystring–The editKey start_website returned, which proves the website is the caller's. Leave it out for a website in the connected account.
pathstringyesThe file's path from the website's root, exactly as it was saved, such as index.html, about.html or images/shop.jpg. list_website_files shows every path.
websiteIdstringyesThe websiteId start_website returned, or one list_sites shows.

No output schema declared.

No examples provided.

list_sites ~96

Lists the websites in the person's Jaybird Digital account, sorted by name, with each one's id, name and live address. Websites started with start_website while the account was connected, or opened with their editKey, are listed under startedWebsites (up to 20, kept ones first). An account with none gets an empty list. Needs the person to connect their account; called without one, it asks them to sign in.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_website_files ~118

Lists every file saved on a website, with each path and its size in bytes, beside the viewUrl, keepUrl, pages, passed and any problems. It changes nothing. The paths are the ones read_website_file and delete_website_file take.

NameTypeReqDescription
editKeystring–The editKey start_website returned, which proves the website is the caller's. Leave it out for a website in the connected account.
websiteIdstringyesThe websiteId start_website returned, or one list_sites shows.

No output schema declared.

No examples provided.

read_website_file ~167

Returns one saved file from a website with its path, encoding and content: pages, stylesheets and scripts as utf8 text, pictures and fonts as base64. It changes nothing. A path that is not saved fails with no_such_file; list_website_files shows which paths exist.

NameTypeReqDescription
editKeystring–The editKey start_website returned, which proves the website is the caller's. Leave it out for a website in the connected account.
pathstringyesThe file's path from the website's root, exactly as it was saved, such as index.html, about.html or images/shop.jpg. list_website_files shows every path.
websiteIdstringyesThe websiteId start_website returned, or one list_sites shows.

No output schema declared.

No examples provided.

save_website_files ~188

Adds or replaces files on a website and checks every page against the rules start_website returned. Files not sent stay as they are; delete_website_file removes one. Returns the viewUrl, keepUrl, pages, passed, and problems naming each rule a page breaks; the person can keep the website once passed is true. A website holds up to 40 files and 12 MB, with pages up to 300 KB and other files up to 2 MB.

NameTypeReqDescription
editKeystring–The editKey start_website returned, which proves the website is the caller's. Leave it out for a website in the connected account.
filesarrayyes1 to 40 files to add or replace. A file whose path is already saved is overwritten.
websiteIdstringyesThe websiteId start_website returned, or one list_sites shows.

No output schema declared.

No examples provided.

search_domains ~99

Asks a domain registrar, live, which names can be registered, and returns up to about a dozen, each with its name, whether it is available and whether it is premium. Availability can change at any moment. Nothing is bought or held; a name is bought from the website's keep page.

NameTypeReqDescription
querystringyesA whole domain name such as sweetcrumbs.com, or a word to build names from such as sweetcrumbs.

No output schema declared.

No examples provided.

start_website ~158

Creates a new, empty website and returns its websiteId, the editKey for changing it, the viewUrl where it can be seen, the keepUrl where the person keeps it, and the rules and size limits its files must meet. Each call makes a separate website; to change one already started, save to its websiteId instead. No account is needed: a draft lasts 7 days unless the person keeps it, and with an account connected it joins that account.

NameTypeReqDescription
aboutstring–Optional: what the person said the website is for, in their words.
businessNamestringyesThe website's name as the person gave it, such as their business's name. It is shown in the website's address.

No output schema declared.

No examples provided.

Install

How do I install the Jaybird Digital MCP server?

Jaybird Digital is a hosted endpoint at https://jaybirddigital.com/api/start/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 · jaybirddigital.com

# add to Claude Code
claude mcp add --transport http com-jaybirddigital-website 'https://jaybirddigital.com/api/start/mcp'
Common questions

What is the Jaybird Digital MCP server?

Jaybird Digital is an MCP server listed in the public MCP registry as com.jaybirddigital/website. Build and host a website from the chat, with no account or API key, and get a live address to show. This page covers its hosted endpoint (https://jaybirddigital.com/api/start/mcp).

Is the Jaybird Digital MCP server safe to use?

Jaybird Digital scores 67 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 Jaybird Digital MCP server expose?

Jaybird Digital exposes 8 tools: start_website, save_website_files, list_website_files, read_website_file, search_domains, and 3 more. Their descriptions and schemas cost roughly 1,128 tokens of context every time the server is loaded.

Does the Jaybird Digital MCP server require authentication?

No. We connected to Jaybird Digital without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Jaybird Digital MCP server still maintained?

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