Skip to content

Minerals MCP server

dev.minerals/mineralsminerals.devstreamable-httpv0.2.0Scanned

The marketplace for agents. It routes each design request to the right library or tool.

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

Tools: 0 delete, 1 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 1
  • 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 Radar only lists and labels, and these labels are the same either way.

What the Minerals MCP server can do

The Minerals MCP server is published by minerals.dev, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (suggest_listing) and create or change data (2 tools: report_outcome and offer), but cannot delete data. 2 tools only read.

1 tool can send data out of your system (suggest_listing).

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 21, 2026, version 0.2.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.

5 tools

Can't be undone 1Claude Code: ask
  • suggest_listingSends a proposal for a design library or tool to the Minerals curator.Can send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Sends a proposal for a design library or tool to the Minerals curator. Applies only when your person made the thing or asks you to recommend it, and only with their yes to exactly what will be sent. No code, file contents or repository names are sent; an email only if your person gives one. Returns one line that says the request was sent.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • offerGives the exact words for one choice, Yes or Not now, about one free item or one 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
    Gives the exact words for one choice, Yes or Not now, about one free item or one listing. Applies when one result of find_design clearly leads. The words are shown as the client's own choice prompt where there is one, otherwise in one line. Called with the ref, it returns the words; called again with the same ref and "answer", it takes the choice. Yes returns what get_listing returns for that ref. Not now returns the entry to record in minerals.json. One offer per working session; never the same thing twice in a project. No offer is needed for an item from a listing in `accepted`. No offer is needed when your person asked for the item or listing by name; that request is their yes.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • report_outcomeRecords whether what get_listing returned was used.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
    Records whether what get_listing returned was used. Applies after get_listing, once the work is done. The curator reads the reports to judge what stays listed. Returns one line that says it was recorded.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • find_designSearches the Minerals shelf of design libraries and tools.No findings

    Why it is in this group

    • The name "find_design" says "find": a word for reading.
    Description, as the server wrote it
    Searches the Minerals shelf of design libraries and tools. Applies when your person asks for, or you are about to choose, a UI component, block, texture, animation, icon set, typeface, colour system, sound or design reference, or asks to change one. Takes one to three keywords as "query" and the moment the work is at as "moment". Returns at most three rows, best first: items for a precise request, listings for a broad one. With nothing sent, it returns the six moments and what is on the shelf. What it returns is a suggestion for your person. When the project already has a component library, icon set, type system or colour system, another of the same kind is returned only with "replace" true. Refs sent as "have" or "declined" from minerals.json are left out, and with "quiet" true nothing is suggested.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_listingReturns the pull for a ref from find_design.No findings

    Why it is in this group

    • The name "get_listing" says "get": a word for reading.
    Description, as the server wrote it
    Returns the pull for a ref from find_design. Applies once your person has chosen a listing or an item. For an item ref (listing/item) it returns the exact pull instruction and the license link; for a listing ref, its free items to choose from. The result also carries `receipt`: the one line that confirms the pull to the person. Only free items are returned; the file comes from the supplier.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

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.

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 out1
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 21, 2026, 19:19 UTC, unchanged since Nov 21, 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://minerals.dev/mcp: tools/list returned 5 tools to an anonymous client, including suggest_listing (irreversible), report_outcome (write), offer (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.

Install

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

claude mcp add --transport http minerals https://minerals.dev/mcp
claude mcp add --transport http minerals https://minerals.dev/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__minerals__find_design",
      "mcp__minerals__get_listing"
    ],
    "ask": [
      "mcp__minerals__report_outcome",
      "mcp__minerals__offer",
      "mcp__minerals__suggest_listing"
    ],
    "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 minerals. Review it before you use it.

Capability tags behind 1 rule
  • mcp__minerals__suggest_listing outbound

Pin

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://radar.anlyon.com/api/v1/servers/dev.minerals/minerals/verify?hash=bfd2c7d0d0df78ba4a13b710981883bce382cb0d9bfe2fb8ed7a07fa4af9b497" | jq -e '.changed == false'

Pinned hash bfd2c7d0d0df, from Nov 21, 2026, 14:18 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.minerals/minerals/changes.xml

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

Badge

Anlyon Radar badge for dev.minerals/minerals
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.minerals/minerals.svg)](https://radar.anlyon.com/servers/dev.minerals/minerals)

Source: MCP Registry · repository. Synced Nov 21, 2026, 15:17 UTC.

Minerals MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Minerals MCP server safe?

No scan can promise that. What its definitions show: 5 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 Minerals MCP server delete data?

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

Can the Minerals MCP server do things that cannot be undone?

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

What tools does the Minerals MCP server have?

5 tools: 1 irreversible, 2 write, 2 read. suggest_listing, report_outcome, offer, find_design and get_listing.

Does the Minerals MCP server need sign-in or OAuth?

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

Does the Minerals MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): suggest_listing.

Has the Minerals MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.