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.

Bro Find AI

REMOTE · BROFINDAI.COM

Search a curated directory of AI tools, AI agents and MCP servers by task, pricing and platform.

Available components

0 this week 76 Trust /100

Last scanned (19 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Security57
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 543 tokens (~108/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 19 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 18 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 17 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 16 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 15 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 13 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
  • 12 Nov 26 0
    • Tool “search_ai_tools” rewrote its description, which is the text the model reads security
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 21 Nov 2026 · Probed https://brofindai.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brofindai.com CN=WE1,O=Google Trust Services,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA256 5d0d3c7fadd8aeb50ed48f8b767c6a8b
SANs: brofindai.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 insecure

Validation of brofindai.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
brofindai.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://brofindai.com/api/mcp Verified 200
http (plaintext) http://brofindai.com/api/mcp HTTPS enforced 301 https://brofindai.com/api/mcp
MCP tools · 5 exposed · ~504 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
get_tool_details ~70

Get full details of a specific AI tool by its slug identifier (e.g. 'chatgpt', 'midjourney'). Returns name, description, URL, category, pricing, votes, and metadata.

NameTypeReqDescription
slugstringyesThe tool's slug identifier (lowercase, hyphenated)

No output schema declared.

No examples provided.

list_categories ~28

List all AI tool categories in the BroFindAI directory with the number of tools in each category.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_mcp_servers ~92

Browse the BroFindAI MCP (Model Context Protocol) servers directory. Filter by category or search by keyword.

NameTypeReqDescription
categorystring–Filter by MCP server category (e.g. 'Databases', 'Browser Automation')
limitnumber–Maximum results to return (default 10, max 50)
querystring–Search keyword for MCP server name, description, or tags

No output schema declared.

No examples provided.

list_tags ~49

List every tag and platform in use across the directory with tool counts, plus how many tools have a known/unknown API and open-source status. Call this to discover valid filter values for search_ai_tools.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_ai_tools ~265

Search the BroFindAI directory of 1230+ AI tools by keyword, category, pricing, platform, tags, API availability, or open-source status. Returns matching tools with full structured metadata.

NameTypeReqDescription
apiboolean–true = only tools with a confirmed public API; false = only tools confirmed to have none. Tools where this is unknown are excluded either way.
categorystring–Filter by category: 'Writing & Content', 'Coding & Dev Tools', 'Image Generation', 'Chatbots & Assistants', 'SEO & Marketing', 'Video', 'Audio & Voice', 'Business', 'Research', 'Data & Analytics', 'O…
limitnumber–Maximum results to return (default 10, max 50)
opensourceboolean–true = only confirmed open-source tools; false = only confirmed proprietary. Tools where this is unknown are excluded either way.
platformstring–Only tools available on this platform
pricingstring–Filter by pricing model
querystring–Search keyword (matches name, tagline, description, and tags)
tagsarray–Only tools carrying ALL of these tags (e.g. ['coding','autocomplete']). Call list_tags for the vocabulary.

No output schema declared.

No examples provided.

Install

How do I install the Bro Find AI MCP server?

Bro Find AI is a hosted endpoint at https://brofindai.com/api/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 · brofindai.com

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

What is the Bro Find AI MCP server?

Bro Find AI is an MCP server listed in the public MCP registry as com.brofindai/brofindai. Search a curated directory of AI tools, AI agents and MCP servers by task, pricing and platform. This page covers its hosted endpoint (https://brofindai.com/api/mcp).

Is the Bro Find AI MCP server safe to use?

Bro Find AI scores 76 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 Bro Find AI MCP server expose?

Bro Find AI exposes 5 tools: search_ai_tools, list_categories, get_tool_details, list_tags, list_mcp_servers. Their descriptions and schemas cost roughly 504 tokens of context every time the server is loaded.

Does the Bro Find AI MCP server require authentication?

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

Is the Bro Find AI MCP server still maintained?

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

What did VerifyMCP test on the Bro Find AI MCP server?

VerifyMCP ran 12 checks on Bro Find AI, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Bro Find AI: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.