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.

io.github.aaadjrbr/nobrainner

REMOTE · APP.NOBRAINNER.XYZ

NoBrainner Spaced Repetition Flashcards, Study Stats & Multi-Language AI Deck Generation

0 this week 23 Trust /100

Last scanned (10 hours ago)

Scores higher than 6% of remote servers

Reachable. Last reached 20 Oct 2026.

Category Education and Research

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 Security57
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 28 Sept 26 −10
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +10
    • Authorization: unverified → fail ▼ security
    • Transport: Transport check failed: the endpoint responded but didn't complete an MCP handshake over sse. security
  • 26 Sept 26 −10
    • Authorization: fail → unverified ▼ security
    • Transport: Transport check failed: declared sse, but the endpoint returned HTTP 429. security
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 +10
    • Authorization: unverified → fail ▼ security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 11 Aug 26 0

    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 20 Oct 2026 · Probed https://app.nobrainner.xyz/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nobrainner.xyz CN=WR3,O=Google Trust Services,C=US 7 Oct 2026 5 Jan 2027 RSA 2048 SHA256-RSA 925e6dd348f375d61201de492804421c
SANs: nobrainner.xyz, *.nobrainner.xyz
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.nobrainner.xyz. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
nobrainner.xyz. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
sse https://app.nobrainner.xyz/api/mcp Not MCP 200
http (plaintext) http://app.nobrainner.xyz/api/mcp HTTPS enforced 301 https://app.nobrainner.xyz:443/api/mcp
MCP tools

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 →

No tool schema has been captured from this endpoint yet.

Install

How do I install the io.github.aaadjrbr/nobrainner MCP server?

io.github.aaadjrbr/nobrainner is a hosted endpoint at https://app.nobrainner.xyz/api/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 · app.nobrainner.xyz

# add to Claude Code
claude mcp add --transport http aaadjrbr-nobrainner 'https://app.nobrainner.xyz/api/mcp'
Common questions

What is the io.github.aaadjrbr/nobrainner MCP server?

io.github.aaadjrbr/nobrainner is an MCP server listed in the public MCP registry as io.github.aaadjrbr/nobrainner. NoBrainner Spaced Repetition Flashcards, Study Stats & Multi-Language AI Deck Generation. This page covers its hosted endpoint (https://app.nobrainner.xyz/api/mcp).

Is the io.github.aaadjrbr/nobrainner MCP server safe to use?

io.github.aaadjrbr/nobrainner scores 23 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.

Does the io.github.aaadjrbr/nobrainner MCP server require authentication?

Its publisher declares no required credentials for io.github.aaadjrbr/nobrainner. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the io.github.aaadjrbr/nobrainner MCP server still maintained?

io.github.aaadjrbr/nobrainner is still listed as active in the MCP registry. We last reached this channel on 20 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.