Skip to main content
Glama
brilliant-directories-mcp

brilliant-directories-mcp

Official

Related Servers

Alternatives to brilliant-directories-mcp

  • A
    license
    A
    quality
    A
    maintenance
    This server enables LLMs to retrieve and process content from web pages, converting HTML to markdown for easier consumption.
    28
    1
    231,785 PyPI
    91,812
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Firecrawl, the context API for AI agents, as an MCP server. Search the web, scrape any URL, parse PDFs and documents, crawl and map sites, interact with pages in a real browser, run Agent research jobs, monitor pages for changes, and search scientific papers. Returns clean Markdown or structured JSON. Run locally with npx firecrawl-mcp or connect to https://mcp.firecrawl.dev/v2/mcp
    28
    168,149 npm
    7,770
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    An MCP implementation that integrates the Brave Search API, providing comprehensive search capabilities including web, local business, image, video, news searches, and AI-powered summarization.
    8
    60,702 npm
    1,562
    MIT

Related Servers

  • A
    license
    A
    quality
    A
    maintenance
    Official MCP Server for Human Search Intent Keywords, Google Lighthouse Core Web Vitals (CLS/LCP/INP), Technical SEO Audits, and On-Page Diagnostic Intelligence.
    5
    15 npm
    1
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Official MCP server for Scorezilla (leaderboards for games). Your AI coding assistant can bootstrap a leaderboard, inspect games and boards, read top-N standings, and paste ready-to-run SDK integration code — without leaving the editor.
    11
    187 npm
    1
    MIT

TDQS

A4.1/5.0

Scored across 171 tools

Disambiguation4/5

Most tools map to a distinct resource and action, with clear list/get/create/update/delete separation per resource. Some potential confusion exists across taxonomy layers (TopCategory vs SubCategory vs DataType vs PostType) and between wrapper-native tools and BD-native tools, but descriptions generally make boundaries clear.

Naming Consistency4/5

Names follow a broadly consistent camelCase verb_noun pattern (e.g. listUsers, createForm, updateWidget, deleteLead). Minor deviations appear in a few resource terms and non-CRUD verbs (getSingleImagePostFields vs getPostTypeCustomFields, refreshSiteCache, matchLead), but the overall convention remains readable and predictable.

Tool Count1/5

The server exposes 171 tools, far beyond a well-scoped 3-15 range and well into extreme mismatch territory. Although many are necessary CRUD variants for a large platform API, the sheer count makes the toolset unwieldy for an agent to navigate reliably.

Completeness4/5

Coverage is very broad across BD resources, with full CRUD for most major entities such as users, posts, pages, widgets, forms, leads, reviews, tags, and categories. Deliberate gaps exist for system-critical tables (cities, states, countries, sidebars are read/update-only), which are reasonable design choices but still leave minor lifecycle holes.

Maintenance

ActivityActive
ResponsivenessLimited data