_ registry / mcp http-sse · checked 8h ago

Learnosity Build Aide MCP

https://mcp.learnosity.com

Registry code: dc63cf9beed9c848

api record

Learnosity integration skills and help site articles.

The golden path for a typical Learnosity integration is author-api, items-api and reports-api. Start from the skill 'golden-path-author-items-reports' when a question is about building an integration rather than about one specific API.

endpoint
https://mcp.learnosity.com/build/build-aide
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is Learnosity Build Aide MCP live?
Yes — it answered the hub's last check (checked 8h ago). It answered 100% of checks over the last 30 days.
Is Learnosity Build Aide MCP free to use?
Yes — the hub reached it with no key and no payment.
What tools does Learnosity Build Aide MCP have?
8 tools: read_document, search_docs_sources, skills_list, skills_read, skills_search, list_docs_sources, get_feedback_link, list_docs_categories.
Is Learnosity Build Aide MCP safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
764ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
3 open 5 never probed 3 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_docs_sources open 8h ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_feedback_link open 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_docs_categories open 8h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "source": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 17 lines
  • read_document unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "source",
        "article_id"
      ],
      "properties": {
        "source": {
          "type": "string"
        },
        "article_id": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • search_docs_sources unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10
        },
        "query": {
          "type": "string"
        },
        "sources": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "category_id": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "off_golden_path_reason": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "default": null
        }
      },
      "additionalProperties": false
    }
    arguments 52 lines
  • skills_list unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "apis": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "default": null
        },
        "limit": {
          "type": "integer",
          "default": 200
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • skills_read unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "skill_id"
      ],
      "properties": {
        "skill_id": {
          "type": "string"
        },
        "max_bytes": {
          "type": "integer",
          "default": 200000
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
  • skills_search unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "default": 20
        },
        "query": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id dc63cf9beed9c848.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/dc63cf9beed9c848/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/dc63cf9beed9c848/badge.svg)](https://brick.blue/agent/dc63cf9beed9c848?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.