Skip to content

MintScope — NFT collection analysis MCP server

io.github.ert1981/mintscopeert1981streamable-httpv0.7.0Scanned

NFT collection risk and quality analysis plus new-collection discovery (OpenSea + on-chain).

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • No findings

Sign-in required, no OAuth metadata. Remote posture

Anlyon alternative

1 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the MintScope — NFT collection analysis MCP server can do

The MintScope — NFT collection analysis MCP server is published by the GitHub account ert1981. It has 2 tools. It can create or change data (1 tool: discover_new_nft_collections), but cannot delete data. 1 tool only reads.

2 tools bring in text other people can write (analyze_nft_collection and discover_new_nft_collections).

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

Last scanned Oct 30, 2026, version 0.7.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.

2 tools

Changes things 1Claude Code: ask
  • discover_new_nft_collectionsNew NFT collections launched on Ethereum and Base in the last day, week or month, found from onchain contract deployments and ranked by evidence-based risk analysis.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    New NFT collections launched on Ethereum and Base in the last day, week or month, found from onchain contract deployments and ranked by evidence-based risk analysis. Not a profit prediction. A full scan can take a few minutes.

    Annotations the server declares

    • title: New NFT launches
    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • analyze_nft_collectionEvidence-based NFT collection risk report: verified OpenSea market data, realized sales versus listings, creator evidence, risk flags, missing data and a confidence level.Reads text others writeNo findings

    Why it is in this group

    • The name "analyze_nft_collection" says "analyze": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Evidence-based NFT collection risk report: verified OpenSea market data, realized sales versus listings, creator evidence, risk flags, missing data and a confidence level. Not a profit prediction.

    Annotations the server declares

    • title: NFT collection risk report
    • readOnlyHint: true
    • openWorldHint: true

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

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
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.

Sign-in required, no OAuth metadata

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

Reachable
yes
HTTP status of an anonymous initialize
503
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: initialize answered HTTP 503.

Posture changes

  1. Nov 14, 2026
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

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.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 503; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 503
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 1 to 0
    • Protocol version: 2025-06-18 to none

Install

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

claude mcp add --transport http mintscope https://mintscope-zrvv.onrender.com/mcp
claude mcp add --transport http mintscope https://mintscope-zrvv.onrender.com/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__mintscope__analyze_nft_collection"
    ],
    "ask": [
      "mcp__mintscope__discover_new_nft_collections"
    ],
    "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 mintscope. Review it before you use it.

Capability tags behind 2 rules
  • mcp__mintscope__analyze_nft_collection untrusted-input
  • mcp__mintscope__discover_new_nft_collections untrusted-input

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/io.github.ert1981/mintscope/verify?hash=f6260ad561d6818f4285b8b2b5c5321a7d3606ee093c6b1b0f8eb9e0459841a5" | jq -e '.changed == false'

Pinned hash f6260ad561d6, from Oct 30, 2026, 21:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.ert1981/mintscope/changes.xml

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

Badge

Anlyon Radar badge for io.github.ert1981/mintscope
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ert1981/mintscope.svg)](https://radar.anlyon.com/servers/io.github.ert1981/mintscope)

Source: MCP Registry. Synced Oct 30, 2026, 21:17 UTC.

MintScope — NFT collection analysis MCP server: questions and answers

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

Is the MintScope — NFT collection analysis MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 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 MintScope — NFT collection analysis MCP server delete data?

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

Can the MintScope — NFT collection analysis MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the MintScope — NFT collection analysis MCP server have?

2 tools: 1 write, 1 read. discover_new_nft_collections and analyze_nft_collection.

Does the MintScope — NFT collection analysis MCP server need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the MintScope — NFT collection analysis MCP server send data to outside services?

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

Has the MintScope — NFT collection analysis MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 30, 2026.