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.

FindAIforWork Directory

REMOTE · FINDAIFORWORK.COM

Search and compare AI tools for work from a curated, read-only directory.

+3 this week 78 Trust /100

Last scanned (4 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 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 Security77
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 291 tokens (~72/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Oct 26 72

    First indexed and scored.

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 5 Nov 2026 · Probed https://findaiforwork.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=findaiforwork.com CN=WE1,O=Google Trust Services,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA256 f5db1b0d7c906e5b135cfbce57fc62b0
SANs: findaiforwork.com, www.findaiforwork.com, *.www.findaiforwork.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 secure

Validation of findaiforwork.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
findaiforwork.com. present 2371 13 Verified
findaiforwork.com. Verified address RRset verified with the apex keys
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
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://findaiforwork.com/mcp Verified 200
http (plaintext) http://findaiforwork.com/mcp HTTPS enforced 301 https://findaiforwork.com/mcp
MCP tools · 4 exposed · ~213 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
compare_tools ~44

Compare two to five published tools side by side. Unknown slugs are reported in missing instead of being guessed.

NameTypeReqDescription
slugsarrayyesTwo to five listing slugs

No output schema declared.

No examples provided.

get_tool ~43

Return the full public listing for one tool by slug, including its Markdown copy and related tools.

NameTypeReqDescription
slugstringyesListing slug, for example "chatgpt"

No output schema declared.

No examples provided.

list_categories ~26

List every active category with its slug, description and the number of published tools in it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tools ~100

Search published AI software listings by free text, category slug or pricing model. Returns a total plus compact summaries.

NameTypeReqDescription
categorystring–Category slug from list_categories
limitinteger–Maximum results, 1-25; defaults to 10
pricingstring–Pricing model filter
querystring–Free text matched against name, tagline, description
sortstring–Result order; defaults to latest

No output schema declared.

No examples provided.

Install

How do I install the FindAIforWork Directory MCP server?

FindAIforWork Directory is a hosted endpoint at https://findaiforwork.com/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 · findaiforwork.com

# add to Claude Code
claude mcp add --transport http brand-lc-findaiforwork 'https://findaiforwork.com/mcp'
Common questions

What is the FindAIforWork Directory MCP server?

FindAIforWork Directory is an MCP server listed in the public MCP registry as io.github.brand-lc/findaiforwork. Search and compare AI tools for work from a curated, read-only directory. This page covers its hosted endpoint (https://findaiforwork.com/mcp).

Is the FindAIforWork Directory MCP server safe to use?

FindAIforWork Directory scores 78 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 FindAIforWork Directory MCP server expose?

FindAIforWork Directory exposes 4 tools: search_tools, get_tool, list_categories, compare_tools. Their descriptions and schemas cost roughly 213 tokens of context every time the server is loaded.

Does the FindAIforWork Directory MCP server require authentication?

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

Is the FindAIforWork Directory MCP server still maintained?

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