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.

Awesome Tools

REMOTE · AWESOME.TOOLS

Search curated SaaS & AI tools, submit your product, and verify backlink badges from any AI agent.

Available components

+4 this week 62 Trust /100

Last scanned (17 hours ago)

Scores higher than 45% 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 Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 586 tokens (~83/item across 7 items; 7 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 Coverage72
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 15% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "submit_feedback" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 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 7 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 +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.

  • 19 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.

  • 17 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.

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

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

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

  • 8 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
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://awesome.tools/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=awesome.tools CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 181f079fcf68d1991322ec32867c18df
SANs: awesome.tools, *.awesome.tools
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 awesome.tools. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tools. DS published 1547 8 Verified
awesome.tools. 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://awesome.tools/mcp Verified 200
http (plaintext) http://awesome.tools/mcp HTTPS enforced 301 https://awesome.tools/mcp
MCP tools · 7 exposed · ~510 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 ~43

Get a tool by slug. Published tools return public details. Unpublished submissions return their status, eligibility, and free/paid next steps.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_categories ~23

List categories with published tool counts. Use the slugs in submit_tool.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_tags ~15

List tags with published tool counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_tools ~83

Search published tools on Awesome Tools. query matches name, tagline, and description. category and tag take slugs from list_categories and list_tags. limit defaults to 20 (max 50).

NameTypeReqDescription
categorystring––
isFeaturedboolean––
limitinteger––
querystring––
tagstring––

No output schema declared.

No examples provided.

submit_feedback ~43

Send feedback to the Awesome Tools team, optionally about a tool slug.

NameTypeReqDescription
categorystringyes–
messagestringyes–
slugstring––

No output schema declared.

No examples provided.

submit_tool ~231

Submit your own SaaS or AI tool. plan free_backlink is free for sites with domain rating 20+, saves the listing, and needs a visible badge link on your site (returns the badge HTML; then call verify_my_backlink). plan featured_49 ($49 Featured Launch, no backlink needed) or sponsor_149 ($149 Featured + Newsletter Sponsor) returns a price only. Nothing is saved and no email is sent until the requester approves the spend and you call again with confirmPaymentSpend true, which returns a Stripe Checkout URL. No payment happens until the requester pays on Stripe.

NameTypeReqDescription
categoriesarray–1-3 category slugs from list_categories.
confirmPaymentSpendboolean–Set true only after the requester approved the payment.
descriptionstringyes–
namestringyes–
planstring––
submitterEmailstringyes–
submitterNamestringyes–
taglinestringyes–
websiteUrlstringyesYour tool's custom domain or HTTPS URL. Preview hosting domains are not accepted.

No output schema declared.

No examples provided.

verify_my_backlink ~72

Check the Awesome Tools badge or link on your site for an unpublished free listing. backlinkUrl defaults to the listing's website. When the link is live and the site is eligible, the listing is scheduled and the submitter is emailed.

NameTypeReqDescription
backlinkUrlstring––
slugstringyes–

No output schema declared.

No examples provided.

Install

How do I install the Awesome Tools MCP server?

Awesome Tools is a hosted endpoint at https://awesome.tools/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 · awesome.tools

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

What is the Awesome Tools MCP server?

Awesome Tools is an MCP server listed in the public MCP registry as tools.awesome/mcp. Search curated SaaS & AI tools, submit your product, and verify backlink badges from any AI agent. This page covers its hosted endpoint (https://awesome.tools/mcp).

Is the Awesome Tools MCP server safe to use?

Awesome Tools scores 62 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 Awesome Tools MCP server expose?

Awesome Tools exposes 7 tools: search_tools, get_tool, list_categories, list_tags, submit_tool, and 2 more. Their descriptions and schemas cost roughly 510 tokens of context every time the server is loaded.

Does the Awesome Tools MCP server require authentication?

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

Is the Awesome Tools MCP server still maintained?

Awesome Tools 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 Awesome Tools MCP server?

VerifyMCP ran 12 checks on Awesome Tools, 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 Awesome Tools: 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.