Look twice.Find the gem.

AI agents and MCP servers, each published with its source and what the checks found.

Marketplace

  • Everything
  • AI agents
  • Apps
  • MCP servers
  • Templates
  • What people want
  • What changed this week
  • The verification standard
  • The ooruby Index
  • Servers that publish no source
  • Reliability guides
  • What the catalogue holds
  • Sell here

Our library

  • Everything, in one place
  • Guides
  • Glossary
  • Calculators
  • Checklists and cheat sheets
  • Community

ooruby

  • Home
  • For teams
  • Site status
  • Company projects
  • RSS feed

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.

Rubricv1.0
AI agentsAppsMCP serversTemplatesWantedCommunityOur library
Sign inSell
Catalogue/MCP servers/Brilliant Directories MCP

Brilliant Directories MCP

brilliantdirectories-user · MCP server

Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.

Not claimed by its maker. Is this yours? Prove it and answer the findings

BDMCP serverSales & CRM

What else was checked

Publisher and name

Nothing found across 4 checks run. Checked 2026-09-30.

Maintenance

Maintained

A release on 13 Sep 2026 (6.58.610), 10 days before this check on 23 Sep 2026. Anything later would only be more recent.

Read from the npm registry, read by the weekly version refresh.

Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured

Not yet tested
Tool description integrity
no match, 2 read
Pattern set 1.0 matched nothing across 2 descriptions, read 2026-10-05.
It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

  • ·Everything. Treat it as you would software from anywhere else.

Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.

Compare with

  • Gitlab MCP Serverside by side
  • Agent Swarmside by side
  • Ghl MCPside by side
Compare all 4

How far this has been checked

Static scanned

What it establishes
Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not
How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read
Version 6.58.610, the file with digest sha512-d42lPBbsWkcNa/HjIACxJ9oI61kQLPy6KSv6lB514W0KcuoeogazdBJQmz3v1mZEudEmV9IZ21x/W1dM7y1beg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
Authentication
Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
How the rungs work

Adding it

Paste this into your client's MCP configuration.

{
  "mcpServers": {
    "brilliant-directories-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "brilliant-directories-mcp@6.58.610"
      ]
    }
  }
}

Or run it directly.

npx -y brilliant-directories-mcp@6.58.610

Pinned to 6.58.610, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

6,622 installs last month · build provenance signed · no published advisories · version current · checked 2026-10-06

Where this came from

Registry
npm
Package
brilliant-directories-mcp
Version read
6.58.610
Resolved
2026-09-23
Open the source(opens in a new tab)

Built from source, attested

npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.

Repository
github.com/brilliantdirectories/brilliant-directories-mcp
Commit
03254bbc5477
Built by
github.com/actions/runner/github-hosted
Registry publish attestation
signed by npm · 2026-09-23
Checked
2026-09-23

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/brilliant-directories-mcp)](https://ooruby.com/market/brilliant-directories-mcp)

About this listing

Kind
MCP server
Category
Sales & CRM
Pricing
Free
Sandbox
No
Hosted
No
Updated
2026-09-13
Price
Free
Get it freeVisit maker
Rating
no reviews yet
0 want this so far
Sign in to vote

Sign in to watch this listing and hear when its version, rung or findings change.

Similar MCP servers

All MCP servers
SAMCP serverSales & CRM
Clean scanStatic scanned

Salesforce MCP

salesforce
Free

MCP Server for interacting with Salesforce instances

171k installs/moApache-2.0
HUMCP serverSales & CRM
Clean scanStatic scanned

Hubspot MCP Server

hubspot
Free

MCP Server for developers building HubSpot Apps

73.9k installs/moMIT
SAMCP serverSales & CRM
1 findingStatic scanned

MCP Salesforce

snokam
Free

MCP server for Salesforce CRM integration with Claude Code

13.6k installs/moNo licence

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.