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.

Gearlist

REMOTE · GEARLIST.BUILD

Free, source-checked directory of AI agent tools, MCP servers and skills, with read-only search.

Available components

+8 this week 78 Trust /100

Last scanned (19 hours ago)

Scores higher than 71% 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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 560 tokens (~112/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 Management47
  • Stability observed for 14 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

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

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 +1

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

  • 18 Nov 26 +1

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

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
  • 15 Nov 26 +5
    • HTTPS: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
  • 14 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 13 Nov 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.

  • 11 Nov 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.

  • 10 Nov 26 0
    • The server rewrote its instructions, which are the text every model session 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://gearlist.build/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=gearlist.build CN=WE1,O=Google Trust Services,C=US 7 Nov 2026 5 Feb 2027 ECDSA 256 ECDSA-SHA256 dca3ba5b0998a5f40e859d20dbad2a16
SANs: gearlist.build, raft.gearlist.build, *.raft.gearlist.build
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 gearlist.build. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
build. DS published 30770, 38839 8, 8 Verified
gearlist.build. 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
Header Value
content-security-policy default-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://gearlist.build/mcp Verified 200
http (plaintext) http://gearlist.build/mcp HTTPS enforced 308 https://gearlist.build/mcp
MCP tools · 5 exposed · ~417 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_gear ~62

Get one Gearlist entry by its id, as returned by search_gear, with what was checked and when. Entries are documentation-checked only. Nothing was installed or audited.

NameTypeReqDescription
idstringyesEntry id, for example 'playwright-mcp'.
NameTypeReqDescription
checkedobjectyesWhat Gearlist checked for this entry, copied from its own fields. A field the entry does not have is left out.
entryobjectyes–
noticestringyes–

No examples provided.

list_categories ~21

List the Gearlist categories with the number of entries in each.

Input schema present but exposes no named parameters.

NameTypeReqDescription
catalog_updatedstringyes–
categoriesarrayyes–
noticestringyes–
total_entriesintegeryes–

No examples provided.

list_skills ~37

List the agent skills published in the Gearlist repository, with the command that installs each one. Ask the human before running any install command.

Input schema present but exposes no named parameters.

NameTypeReqDescription
install_allstringyesInstalls the skills you pick from this repository.
noticestringyes–
repositorystringyes–
skillsarrayyes–

No examples provided.

recommend_stack ~116

Find a short set of Gearlist entries whose own text shares the most words with a job you describe, spread across groups, quoting where each match appears. Matches are on words, so check each entry suits the job before suggesting it.

NameTypeReqDescription
jobstringyesThe job in plain words, for example 'test my web app in a real browser'. Common words such as 'my' or 'the' are ignored.
limitinteger–How many entries to return, from 1 to 10. Default 6.
NameTypeReqDescription
catalog_updatedstringyes–
countintegeryesItems returned.
itemsarrayyes–
jobstringyes–
matchstringyesfound: each item has at least half of the job's words, and at least two when the job has two or more, in its name, id, group, description or audience. none: no entry does.
next_stepstringyesWhat to do with the result.
noticestringyes–
total_matchesintegeryesEntries that fit the job, before the limit.
wordsarrayyesThe job's words that were looked for, after common words were dropped and word endings trimmed.

No examples provided.

search_gear ~181

Search the Gearlist catalog of source-checked AI agent tools, MCP servers and skills. Matches words in the name, category, description, audience and access notes, best match first. Each result includes its access notes, which you should show the human. Entries are documentation-checked only, not installed or audited.

NameTypeReqDescription
categorystring–Optional. Limit results to one category. list_categories gives the names and counts.
limitinteger–How many entries to return, from 1 to 50. Default 10.
querystringyesWords to look for, for example 'browser automation' or 'send email'. Entries that match every word come first, then entries that match some of them. Common words such as 'the' or 'tool' are ignored.…
NameTypeReqDescription
catalog_updatedstringyes–
categorystring––
countintegeryesResults returned.
full_matchesintegeryesEntries that match every word.
matchstringyesall: every result matches every word. partial: some results match only some words, listed after the full matches. none: nothing matched.
noticestringyes–
querystringyes–
resultsarrayyes–
total_matchesintegeryesEntries that match at least one word.

No examples provided.

Install

How do I install the Gearlist MCP server?

Gearlist is a hosted endpoint at https://gearlist.build/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 · gearlist.build

# add to Claude Code
claude mcp add --transport http build-gearlist-gearlist 'https://gearlist.build/mcp'
Common questions

What is the Gearlist MCP server?

Gearlist is an MCP server listed in the public MCP registry as build.gearlist/gearlist. Free, source-checked directory of AI agent tools, MCP servers and skills, with read-only search. This page covers its hosted endpoint (https://gearlist.build/mcp).

Is the Gearlist MCP server safe to use?

Gearlist 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 Gearlist MCP server expose?

Gearlist exposes 5 tools: search_gear, get_gear, list_categories, list_skills, recommend_stack. Their descriptions and schemas cost roughly 417 tokens of context every time the server is loaded.

Does the Gearlist MCP server require authentication?

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

Is the Gearlist MCP server still maintained?

Gearlist 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 Gearlist MCP server?

VerifyMCP ran 13 checks on Gearlist, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.