All servers · Code & repositories
Agentic Engineering Periodic System
academy.ase/periodic-system · v2026.4.1
New (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | prompts, tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Practices for building software with coding agents, each with a test you check on your repo.
Connect
streamable-http · https://ase.academy/mcp
claude mcp add --transport http periodic-system https://ase.academy/mcp{
"mcpServers": {
"periodic-system": {
"url": "https://ase.academy/mcp"
}
}
}Tools as reported by the server
overviewThe Agentic Engineering Periodic System: what it is, how to read it (rows, columns, judging and reading rules), the roles. Call this first.find_elementsFind 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_elementOne 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_checklistWhat 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.
Website · JSON · Text for agents · Registry updated 2026-10-22