Is Brilliant Directories MCP safe to use?

Brilliant Directories MCP has an HVTrust score of 67.0/100 (Grade B), ranked #405 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Brilliant Directories MCP?

Brilliant Directories MCP scores 67.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 18 GitHub stars and is categorized under MCP Servers.

Brilliant Directories MCP

brilliantdirectories/brilliant-directories-mcp

Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, pages, and more from any AI agent. OpenAPI 3.1 spec included.

MCP Servers JavaScript Listed MIT

Is Brilliant Directories MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.9 / 10

Provenance Attested

Signed commits 0%

Last push 13d ago

Compare Brilliant Directories MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Brilliant Directories MCP scores 67.0/100 (Grade B), ranked #405 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.9/10; recent commits are unsigned; last pushed 2026-09-13. Every point is earned from checkable signals — never paid placement. How scoring works →

How Brilliant Directories MCP compares in MCP Servers

#240 MCP Server for WinDbg Crash Analysis 67.0 ±0
#241 E18e MCP 67.0 ±0
#242 Brilliant Directories MCP 67.0 this agent
#243 Docspace MCP 67.0 ±0
#244 MCP Proxmox 67.0 ±0

Bars show each HVTrust score; the tick marks Brilliant Directories MCP’s 67.0.

Where the 67.0 comes from

HVTrust dimensions vs the MCP Servers average

67.0 / 100 · 100.0% confidence

Brilliant Directories MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

12.4 / 25

2.1 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.8 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.0 / 20

0.9 above avg 12.1

AdoptionLog-scaled stars · package downloads

7.1 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/10. Tighten the weakest checks to improve public safety evidence.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for Brilliant Directories MCP View MCP Servers Report missing data

40.6

Activity sub-score · out of 100

#242

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-13

13 days ago

Commits (4 wk)

Downloads (7d)

1,059

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼4

was #401

Analysis

Activity Inputs

40.6 / 100

StarsRepository reach

7.7 / 30

FreshnessLast push recency

23.2 / 25

ActivityRecent commits

6.0 / 25

CommunityFork signal

3.6 / 20

Supply Chain Trust

Package Provenance

Verified

npm attestation

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Sep 19, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 9

Vulnerabilities 0

Common questions about Brilliant Directories MCP

Brilliant Directories MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does Brilliant Directories MCP publish package provenance?

Yes. Brilliant Directories MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does Brilliant Directories MCP have an OpenSSF Scorecard?

Brilliant Directories MCP has an OpenSSF Scorecard score of 3.9/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Brilliant Directories MCP actively maintained?

Maintained. Last push was 13 days ago.

What license does Brilliant Directories MCP use?

Brilliant Directories MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Brilliant Directories MCP's commits signed?

0% of the last 100 commits to Brilliant Directories MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface

Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support

high confidence

Implemented

Brilliant Directories MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

Detected changes to Brilliant Directories MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-12

Provenance Added

Package provenance attestation detected

Maintain Brilliant Directories MCP?

For maintainers

HVTrust scores Brilliant Directories MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Anthropic

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 657 spots (#1049 → #392)

2026-09-23

HVTrust Changed

HVTrust up 43.6pts (23.6 → 67.2)

2026-09-22

Newly Listed

First tracked at rank #1049

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 102 spots (#316 → #418)

2026-09-20

HVTrust Changed

HVTrust down 4.1pts (70.6 → 66.5)

2026-09-20

Activity Score Changed

Activity score down 9pts (50 → 41)

2026-09-11

Rank Moved

Rank dropped 35 spots (#268 → #303)

2026-09-08

Rank Moved

Rank rose 23 spots (#286 → #263)

2026-09-07

Rank Moved

Rank dropped 18 spots (#268 → #286)

2026-09-05

Grade Changed

Trust grade D → B

2026-09-05

Rank Moved

Rank rose 636 spots (#896 → #260)

2026-09-05

HVTrust Changed

HVTrust up 25.2pts (46.0 → 71.2)

2026-09-04

Rank Moved

Rank dropped 25 spots (#871 → #896)

2026-09-03

Rank Moved

Rank dropped 59 spots (#812 → #871)

2026-09-02

Grade Changed

Trust grade B → D

2026-09-02

Rank Moved

Rank dropped 627 spots (#185 → #812)

2026-09-02

HVTrust Changed

HVTrust down 25.3pts (71.4 → 46.1)

2026-08-31

Grade Changed

Trust grade D → B

2026-08-31

Rank Moved

Rank rose 525 spots (#702 → #177)

2026-08-31

HVTrust Changed

HVTrust up 25.2pts (46.3 → 71.5)

2026-08-30

Scorecard Added

OSSF Scorecard: 3.9/10

2026-08-30

Grade Changed

Trust grade C → D

2026-08-30

Rank Moved

Rank dropped 415 spots (#287 → #702)

2026-08-30

HVTrust Changed

HVTrust down 18.1pts (64.4 → 46.3)

2026-08-29

Grade Changed

Trust grade B → C

2026-08-29

Rank Moved

Rank dropped 47 spots (#240 → #287)

2026-08-27

Rank Moved

Rank dropped 14 spots (#225 → #239)

2026-08-26

Rank Moved

Rank dropped 17 spots (#208 → #225)

2026-08-24

Grade Changed

Trust grade D → B

2026-08-24

Rank Moved

Rank rose 375 spots (#583 → #208)

2026-08-24

HVTrust Changed

HVTrust up 23.9pts (42.7 → 66.6)

2026-08-22

Grade Changed

Trust grade B → D

2026-08-22

Rank Moved

Rank dropped 383 spots (#199 → #582)

2026-08-22

HVTrust Changed

HVTrust down 24.3pts (67.0 → 42.7)

2026-08-19

Grade Changed

Trust grade D → B

2026-08-19

Rank Moved

Rank rose 377 spots (#583 → #206)

2026-08-19

HVTrust Changed

HVTrust up 24.0pts (42.6 → 66.6)

2026-08-17

Grade Changed

Trust grade B → D

2026-08-17

Rank Moved

Rank dropped 391 spots (#194 → #585)

2026-08-17

HVTrust Changed

HVTrust down 24.5pts (67.1 → 42.6)

2026-08-13

Grade Changed

Trust grade D → B

2026-08-13

Rank Moved

Rank rose 375 spots (#571 → #196)

2026-08-13

HVTrust Changed

HVTrust up 24.0pts (42.7 → 66.7)

2026-08-12

Tool Surface Changed

Detected tool/plugin surface changed: marketplace → declared

2026-08-12

Provenance Added

Package provenance attestation detected

2026-08-12

Rank Moved

Rank rose 122 spots (#693 → #571)

2026-08-12

HVTrust Changed

HVTrust up 7.1pts (35.6 → 42.7)

2026-08-10

Rank Moved

Rank dropped 29 spots (#664 → #693)

2026-08-08

Newly Listed

First tracked at rank #660

GitHub → npm: brilliant-directories-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/brilliant-directories-mcp.svg)](https://hvtracker.net/agents/brilliant-directories-mcp)
            
HTML:
            <a href="https://hvtracker.net/agents/brilliant-directories-mcp"><img src="https://hvtracker.net/badge/brilliant-directories-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON