Is the Awesome Tools MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Awesome Tools MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Awesome Tools MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: submit_feedback.

What tools does the Awesome Tools MCP server have?

7 tools: 1 irreversible, 2 write, 4 read. submit_feedback, submit_tool, verify_my_backlink, search_tools, get_tool, list_categories and list_tags.

Does the Awesome Tools MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Awesome Tools MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Awesome Tools MCP server changed its tools?

Not since anlyon.dev started tracking it. Last scanned Nov 7, 2026.

Awesome Tools MCP server

tools.awesome/mcpawesome.toolsstreamable-httpv1.0.0Scanned 7 days ago

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

7 tools: 1 do something that can't be undone, 2 change things and 4 only read.

Reads private data · 0
Reads text others write · 0
Can send data out · 0
No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

Anlyon lists the tools and adopts none.
Each tool you adopt gets approvals and receipts.
Your agent never holds the key.

Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.

What the Awesome Tools MCP server can do

The Awesome Tools MCP server is published by awesome.tools, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (submit_feedback) and create or change data (2 tools: submit_tool and verify_my_backlink), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 7, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 1Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

submit_feedbackSend feedback to the Awesome Tools team, optionally about a tool slug.No findings
Why it is in this group
- The name "submit_feedback" says "submit": a word for a change.
- The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it
Send feedback to the Awesome Tools team, optionally about a tool slug.

Changes things 2Creates or changes something that can be changed back.Claude Code: ask

submit_toolSubmit your own SaaS or AI tool.No findings
Why it is in this group
- The name "submit_tool" says "submit": a word for a change.
Description, as the server wrote it
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.
verify_my_backlinkCheck the Awesome Tools badge or link on your site for an unpublished free listing.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
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.

Only reads 4Looks things up and changes nothing.Show 4 read-only tools

get_toolGet a tool by slug.No findings
Why it is in this group
- The name "get_tool" says "get": a word for reading.
Description, as the server wrote it
Get a tool by slug. Published tools return public details. Unpublished submissions return their status, eligibility, and free/paid next steps.
list_categoriesList categories with published tool counts.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it
List categories with published tool counts. Use the slugs in submit_tool.
list_tagsList tags with published tool counts.No findings
Why it is in this group
- The name "list_tags" says "list": a word for reading.
Description, as the server wrote it
List tags with published tool counts.
search_toolsSearch published tools on Awesome Tools.No findings
Why it is in this group
- The name "search_tools" says "search": a word for reading.
Description, as the server wrote it
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).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0: Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 8, 2026, 06:19 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable: yes
HTTP status of an anonymous initialize: 200
tools/list served without credentials: yes
Tools that change things, listed without credentials: 3
Protocol version: 2025-06-18
WWW-Authenticate on 401: not observed
resource_metadata in WWW-Authenticate: not observed
RFC 9728 protected resource metadata: not observed
Authorization servers: not observed
Legacy HTTP+SSE transport: no
Dynamic client registration: not observed
Client ID metadata documents: not observed

HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
Matched text
https://awesome.tools/mcp: tools/list returned 7 tools to an anonymous client, including submit_feedback (irreversible), submit_tool (write), verify_my_backlink (write)
What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http awesome https://awesome.tools/mcp

claude mcp add --transport http awesome https://awesome.tools/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__awesome__search_tools",
      "mcp__awesome__get_tool",
      "mcp__awesome__list_categories",
      "mcp__awesome__list_tags"
    ],
    "ask": [
      "mcp__awesome__submit_tool",
      "mcp__awesome__verify_my_backlink",
      "mcp__awesome__submit_feedback"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as awesome. Review it before you use it.

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/tools.awesome/mcp/verify?hash=fc4db75da1f479e943b86c79fe9ad62662c614fb9181e84eca96f984dfcfcd66" | jq -e '.changed == false'

Pinned hash fc4db75da1f4, from Nov 7, 2026, 15:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/tools.awesome/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/tools.awesome/mcp.svg)](https://anlyon.dev/servers/tools.awesome/mcp)

Source: MCP Registry · repository. Synced Nov 7, 2026, 15:18 UTC.