MINIMALCULT
REMOTE · AI.MINIMALCULT.ORG
Check MCP servers and packages against an independent, anchored record before you trust them.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 6 Nov 2026.
Category Security
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 550 tokens (~110/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 43% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
- Schema quality: 448 → 550 ▼ functional
- Tool coverage: 33% → 43% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- New tool “monitor_create” functional
- 4 Nov 26 70
First indexed and scored.
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 6 Nov 2026 · Probed https://ai.minimalcult.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai.minimalcult.org | CN=YE1,O=Let's Encrypt,C=US | 2 Nov 2026 | 31 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6bf8eaf2a8c76a607545d99477dafec536b |
| SANs: ai.minimalcult.org | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of ai.minimalcult.org. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725, 26974 | 8, 8 | Verified |
| minimalcult.org. | DS published | 11645 | 13 | Verified |
| ai.minimalcult.org. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.minimalcult.org/mcp | Verified | 200 | |
| http (plaintext) | http://ai.minimalcult.org/mcp | HTTPS enforced | 308 | https://ai.minimalcult.org/mcp |
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 →
check Check before you trust ~193
Check an MCP server, an npm or PyPI package (optionally with the hash you are about to install), an MCP endpoint URL or a TON address against the anchored record. Returns a signed check: status (witnessed, changed_recently, hash_mismatch, not_witnessed, sanctions_listed, not_listed), flags, facts, recent changes with diff links.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | RFC 3339 time: answer as the record stood at that moment |
| integrity | string | – | npm dist.integrity of the tarball you are about to install |
| sha256 | string | – | sha256 of the PyPI file you are about to install |
| target | string | yes | registry name (io.github.owner/server), npm:<name> or pypi:<name>, https URL, or TON address |
| type | string | yes | – |
| version | string | – | – |
No output schema declared.
No examples provided.
monitor_create Watch a record ~102
Subscribe a webhook to changes of a record (new version, tool description changed, removed). Returns the monitor id and a secret shown once (HMAC-SHA256 signatures, header MINIMALCULT-Signature). 3 monitors per address are free.
| Name | Type | Req | Description |
|---|---|---|---|
| record | string | yes | rec_ id or mcp:<registry name>, npm:<name>, pypi:<name> |
| url | string | yes | public https URL that receives monitor.triggered events |
No output schema declared.
No examples provided.
record_get Get a record ~47
One record by rec_ id or source id (mcp:<registry name>, npm:<name>, pypi:<name>) with its latest recorded fact.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
record_search Search the record ~59
Find records of MCP servers and npm/PyPI packages by name or words; returns rec_ ids, on-record-since dates, latest versions.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| type | string | – | – |
No output schema declared.
No examples provided.
record_versions List recorded facts ~50
The recorded facts (versions, registry entries, package artifacts, tool descriptions) of a record, newest first, with proof and diff links.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
How do I install the MINIMALCULT MCP server?
MINIMALCULT is a hosted endpoint at https://ai.minimalcult.org/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 · ai.minimalcult.org
claude mcp add --transport http org-minimalcult-minimalcult 'https://ai.minimalcult.org/mcp'
What is the MINIMALCULT MCP server?
MINIMALCULT is an MCP server listed in the public MCP registry as org.minimalcult/minimalcult. Check MCP servers and packages against an independent, anchored record before you trust them. This page covers its hosted endpoint (https://ai.minimalcult.org/mcp).
Is the MINIMALCULT MCP server safe to use?
MINIMALCULT scores 72 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 MINIMALCULT MCP server expose?
MINIMALCULT exposes 5 tools: check, monitor_create, record_search, record_get, record_versions. Their descriptions and schemas cost roughly 451 tokens of context every time the server is loaded.
Does the MINIMALCULT MCP server require authentication?
No. We connected to MINIMALCULT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MINIMALCULT MCP server still maintained?
MINIMALCULT is still listed as active in the MCP registry. We last reached this channel on 6 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 MINIMALCULT MCP server?
VerifyMCP ran 13 checks on MINIMALCULT, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.