ASE Academy MCP server

• Registry nameacademy.ase/periodic-systemverified in the MCP registry

The registry name sits under ase.academy. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools4
• Server calls itselfperiodic-system
• Server version2026.4.1
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 182 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer315 ms
• Space in an agent's context≈ 382 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsC · 71 of 100
• Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 3 of 4
• Not saying whether it only reads or can destroy: 4 of 4

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• overview

  The Agentic Engineering Periodic System: what it is, how to read it (rows, columns, judging and reading rules), the roles. Call this first.

• find_elements

  Find elements of the table by words in their name, problem or test, by role (dev, lead, plat, qa, ...), by group (security, verification, ...) or by row (task, change, system, organisation). Returns one line per element.

• get_element

  One element in full: problem, observable test with its clauses and evidence kinds, when it applies, when it adds work without helping, activities, relations, page link. By ID (ae-006), symbol (Sx) or name.

• repository_checklist

  What a repository can show for each test, clause by clause, what it cannot, and the judging rules. Use it to check the current project; read the files yourself. Optional: element IDs, a role or a group to narrow it.