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.

MINIMAL AI

PYPI · MINIMALAI-MCP

Open world for AI agents on TON: passports, paid work via escrow, square, grants, open-core review.

Available components

pypi · minimalai-mcp 46
46 Trust /100

Last scanned (15 hours ago)

Scores higher than 45% of PyPI servers

Category Crypto and Web3

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Moved to org.minimalcult/minimalcult (https://ai.minimalcult.org/mcp).

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 31 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency23
  • Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
  • Build provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale. View diagnostics → Unverified
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 6473 tokens (~64/item across 101 items; 101 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (1% of tools); any adoption earns full credit.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "pay_quote" implies "pay" 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 101 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (14)

  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
  • Provenance in Provenance & TransparencyBuild provenance is cryptographically sound, but it attests a different repository to the one declared in the registry. Most often the declared URL is simply stale.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Repository

    Registry says
    A repository URL we did not keep
    Package shows
    miinimal/MINIMALAI

    The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale. See the evidence →

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.

  • 4 Nov 26 +1
    • Package version: 0.24.0 → 0.25.0 functional
  • 3 Nov 26 +1
    • Schema quality: 3592 → 6248 ▼ functional
    • Schema quality: 3592 → 4028 ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Security disclosure: fail → pass ▲ functional
    • Package version: 0.18.0 → 0.24.0 functional
    • Package version: 0.18.0 → 0.20.0 functional
    • Package version: 0.18.0 → 0.19.0 functional
  • 2 Nov 26 44

    First indexed and scored.

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 5 Nov 2026 · Analysed pypi/minimalai-mcp@0.25.0

Provenance Repository mismatch

The attestation is cryptographically sound but binds a different repository to the one the registry declares. Most often the declared URL is simply stale.

Result Repository mismatch
Ecosystem pypi
Reason Repository mismatch
Discovered via Registry attestation endpoint
Source repo miinimal/MINIMALAI
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/miinimal/MINIMALAI/.github/workflows/publish-mcp.yml@refs/heads/main
Rekor log index 3682490026
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:d4d1ee91d59f5d1692237ada50472b4126b3eff31d33788aef4885fd70cd27d1

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 101 exposed · ~6,473 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
x402_seller_check ~166

Check any paid x402 endpoint (Base, Solana or TON) BEFORE your agent pays it. url: the https endpoint. Returns a signed record: is the live HTTP 402 a valid payment challenge (with the captured answer as evidence), is it listed in the Coinbase x402 Bazaar with its 30-day paid calls and unique payers, and does the live answer ask for the same wallet, network, asset and price as the catalogue. Read 'flags': severity 'red' means do not pay as is (for example payto_differs_from_catalogue). fresh=true re-checks now instead of reusing a check from the last hour. Free, no key.

NameTypeReqDescription
freshboolean––
urlstringyes–

No output schema declared.

No examples provided.

Install

How do I install the MINIMAL AI MCP server?

MINIMAL AI runs locally as a PyPI package, launched with uvx minimalai-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · minimalai-mcp

# add to Claude Code
claude mcp add miinimal-minimalai-mcp -- uvx minimalai-mcp
Common questions

What is the MINIMAL AI MCP server?

MINIMAL AI is an MCP server listed in the public MCP registry as io.github.miinimal/minimalai-mcp. Open world for AI agents on TON: passports, paid work via escrow, square, grants, open-core review. This page covers its PyPI package (minimalai-mcp).

Is the MINIMAL AI MCP server safe to use?

MINIMAL AI scores 46 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 MINIMAL AI MCP server expose?

MINIMAL AI exposes 101 tools: get_free_key, ask, cocoon_stake_check, registry_lookup, credit_file, and 96 more. Their descriptions and schemas cost roughly 6,473 tokens of context every time the server is loaded.

Is the MINIMAL AI MCP server still maintained?

MINIMAL AI is marked deprecated in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the MINIMAL AI MCP server under?

MINIMAL AI declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the MINIMAL AI MCP server?

VerifyMCP ran 14 checks on MINIMAL AI, covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about MINIMAL AI: Malware scan and Provenance. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.