io.github.BrightSiteHQ/brightsite

Name: io.github.BrightSiteHQ/brightsite
Rating: 60 (1 reviews)
Author: io.github.BrightSiteHQ

MCPcommunity

v1.0.0io.github.BrightSiteHQUnknownUpdated 1mo agoGitHub

Manage BrightSite websites: pages, blog posts, components, forms, media, and analytics.

The official Model Context Protocol server for BrightSite — connect AI assistants like Claude to manage your websites, pages, blog posts, components, forms, media, and analytics. Transport: Streamable HTTP. The server supports two authentication methods. Most modern MCP clients will negotiate OAuth automatically; clients that don't can fall back to a Bearer token. OAuth-capable clients…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

1mo agoLast update

Package

Authorio.github.BrightSiteHQ

LicenseUnknown

Version1.0.0

Sourcemcp-registry

GitHubBrightSiteHQ/brightsite-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp