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.

Sanity Check — Technical Architecture Review

REMOTE · SANITY.AIMLDS.ORG

Automated architecture sanity check: 19 rule-cited checks, verdict report. Paid runs US$99.

63 Trust /100

Last scanned (23 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 4 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 410 tokens (~102/item across 4 items; 4 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 Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 60% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
  • Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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.

  • 3 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 2 Nov 26 62

    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 4 Nov 2026 · Probed https://sanity.aimlds.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aimlds.org CN=WE1,O=Google Trust Services,C=US 4 Oct 2026 2 Jan 2027 ECDSA 256 ECDSA-SHA256 2228a153c7a9455b1377ae326a39781a
SANs: aimlds.org, *.aimlds.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of sanity.aimlds.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
aimlds.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://sanity.aimlds.org/mcp Verified 200
http (plaintext) http://sanity.aimlds.org/mcp HTTPS enforced 301 https://sanity.aimlds.org/mcp
MCP tools · 4 exposed · ~352 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
sanity_check_catalogue ~42

List the architecture checks the Sanity Check runs (families, plain-language descriptions), what is NOT assessed, pricing, and how run credits work. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sanity_check_credit_status ~86

Check payment state without spending anything: pass 'credit' (a web run-credit id from Stripe checkout) to see its status, or 'api_key' to see its run-credit balance. Free.

NameTypeReqDescription
api_keystring–An API key created at POST /api/v1/keys.
creditstring–A run-credit id (Stripe checkout session id).

No output schema declared.

No examples provided.

sanity_check_run ~176

Run the full Technical Architecture Sanity Check on YOUR intake and return the verdict summary + report links (PDF/DOCX/HTML/Markdown/JSON). Costs ONE run credit: pass 'credit' (a web run-credit id) or 'api_key' (a key with balance). The intake is the SanityCheckIntakeV1 object (sections a-g; schema at https://sanity.aimlds.org/api/v1/intake-schema). Never include credentials in an intake — credential-shaped values are refused.

NameTypeReqDescription
api_keystring––
creditstring––
intakeobjectyesSanityCheckIntakeV1 — sections a (context), b (architecture), c (spend bands), d (data flows), e (AI), f (security posture), g (pain).

No output schema declared.

No examples provided.

sanity_check_sample ~48

Run the published sample intake (a fictional fintech with deliberately weak answers) live through the same checker and return its verdict + top findings. Free preview — this is the sample, not your architecture.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Sanity Check — Technical Architecture Review MCP server?

Sanity Check — Technical Architecture Review is a hosted endpoint at https://sanity.aimlds.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 · sanity.aimlds.org

# add to Claude Code
claude mcp add --transport http nrupala-sanity-check 'https://sanity.aimlds.org/mcp'
Common questions

What is the Sanity Check — Technical Architecture Review MCP server?

Sanity Check — Technical Architecture Review is an MCP server listed in the public MCP registry as io.github.nrupala/sanity-check. Automated architecture sanity check: 19 rule-cited checks, verdict report. Paid runs US$99. This page covers its hosted endpoint (https://sanity.aimlds.org/mcp).

Is the Sanity Check — Technical Architecture Review MCP server safe to use?

Sanity Check — Technical Architecture Review scores 63 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 Sanity Check — Technical Architecture Review MCP server expose?

Sanity Check — Technical Architecture Review exposes 4 tools: sanity_check_catalogue, sanity_check_sample, sanity_check_credit_status, sanity_check_run. Their descriptions and schemas cost roughly 352 tokens of context every time the server is loaded.

Does the Sanity Check — Technical Architecture Review MCP server require authentication?

No. We connected to Sanity Check — Technical Architecture Review without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Sanity Check — Technical Architecture Review MCP server still maintained?

Sanity Check — Technical Architecture Review is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.