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.

Learnosity Build Aide

REMOTE · MCP.LEARNOSITY.COM

Build Learnosity integrations from Learnosity's own documentation and integration skills.

+4 this week 75 Trust /100

Last scanned (16 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Code Search and Documentation

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 Security74
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 963 tokens (~64/item across 15 items; 8 tools + 7 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 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 (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

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 →

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.

  • 21 Nov 26 +1
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 20 Nov 26 0
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 19 Nov 26 +1
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 18 Nov 26 0
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 17 Nov 26 +1
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 16 Nov 26 0
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 15 Nov 26 +1
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
  • 14 Nov 26 0
    • Resource “source_index” now points somewhere else: learnosity://help-site/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://author-guide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://feedback-aide/index → learnosity://github/index security
    • Resource “source_index” now points somewhere else: learnosity://demos/index → learnosity://github/index security
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 21 Nov 2026 · Probed https://mcp.learnosity.com/build/build-aide

TLS valid

Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.learnosity.com CN=Amazon RSA 2048 M04,O=Amazon,C=US 21 Aug 2026 6 Mar 2027 RSA 2048 SHA256-RSA b93956e12aa64185391a2bebd21d1a7
SANs: *.learnosity.com
CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 773124f2a952e3ed18a58bdb85d1bc0ce5f27
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.learnosity.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
learnosity.com. No DS 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
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://mcp.learnosity.com/build/build-aide Verified 200
http (plaintext) http://mcp.learnosity.com/build/build-aide HTTPS enforced 301 https://mcp.learnosity.com:443/build/build-aide
MCP tools · 8 exposed · ~464 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
get_feedback_link ~94

Call this when a user wants to give feedback, report a problem, or suggest an improvement about the Learnosity MCP server or its documentation. Returns a friendly message and a link to the Learnosity MCP Feedback Page to share with the user. This does not collect feedback in the chat. Do not ask the user for their email, credentials, ratings, or any structured feedback fields in the chat - the linked page collects everything.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

list_docs_categories ~50

List cached Learnosity categories. Use list_docs_sources or learnosity://sources/index to discover valid source ids. If no source is provided, categories from every configured source are returned.

NameTypeReqDescription
source–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_docs_sources ~36

List the configured Learnosity documentation sources. Use this tool or learnosity://sources/index to discover valid source ids before searching or reading.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

read_document ~53

Read a cached Learnosity document from a required source and article id. Use list_docs_sources or learnosity://sources/index to discover valid source ids.

NameTypeReqDescription
article_idstringyes–
sourcestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_docs_sources ~117

Search cached Learnosity documentation sources. Use list_docs_sources or learnosity://sources/index to discover valid source ids. If no sources are provided, the search spans every configured source. Hits that touch a lower-level API outside the golden path are withheld unless off_golden_path_reason carries the user's real reason for steering off it; that parameter is required on every such request.

NameTypeReqDescription
category_id–––
limitinteger––
off_golden_path_reason–––
querystringyes–
sources–––

Structured output declared, but exposes no named fields.

No examples provided.

skills_list ~36

List Learnosity integration skills with ids, titles, goals, and APIs

NameTypeReqDescription
apis–––
limitinteger––

Structured output declared, but exposes no named fields.

No examples provided.

skills_read ~38

Read one Learnosity integration skill by id and return its Markdown body

NameTypeReqDescription
max_bytesinteger––
skill_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

skills_search ~40

Search Learnosity integration skills by id, title, goal, APIs, or body content

NameTypeReqDescription
limitinteger––
querystringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Learnosity Build Aide MCP server?

Learnosity Build Aide is a hosted endpoint at https://mcp.learnosity.com/build/build-aide, 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 · mcp.learnosity.com

# add to Claude Code
claude mcp add --transport http learnosity-build-aide 'https://mcp.learnosity.com/build/build-aide'
Common questions

What is the Learnosity Build Aide MCP server?

Learnosity Build Aide is an MCP server listed in the public MCP registry as io.github.Learnosity/build-aide. Build Learnosity integrations from Learnosity's own documentation and integration skills. This page covers its hosted endpoint (https://mcp.learnosity.com/build/build-aide).

Is the Learnosity Build Aide MCP server safe to use?

Learnosity Build Aide scores 75 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 Learnosity Build Aide MCP server expose?

Learnosity Build Aide exposes 8 tools: list_docs_sources, search_docs_sources, list_docs_categories, read_document, skills_list, and 3 more. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.

Does the Learnosity Build Aide MCP server require authentication?

No. We connected to Learnosity Build Aide without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Learnosity Build Aide MCP server still maintained?

Learnosity Build Aide is still listed as active in the MCP registry. We last reached this channel on 21 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 Learnosity Build Aide MCP server?

VerifyMCP ran 13 checks on Learnosity Build Aide, 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.