Skip to content
The Ainglish Project logo

The Ainglish Project MCP server

Which servers in the official MCP registry are The Ainglish Project's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-15

← Back to The Ainglish Project

Whose server it is
  • Registry nameorg.ainglish/ainglishverified in the MCP registry

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

When we asked itchecked 2026-10-15
  • Stateanswerschecked 2026-10-15
  • Tools51
  • Server calls itselfainglish
  • Server version1.0.0
  • Protocol version2025-06-18

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

Measured dailydaily checks: 2, the first on 2026-10-19
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer342 ms
  • Space in an agent's context≈ 6,908 tokensthe definitions of all its tools (51), which an agent carries on every turn
  • Tool definitionsB · 78 of 100
  • Parameters without a description: in 16 of 51
  • Not saying whether it only reads or can destroy: 51 of 51

Worth a look

  • Tools that change data, on a server that answers without a sign-in: set_author_work_notice

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 state of vendors' MCP servers: method and numbers →

Tools it offers51 tools · read 2026-10-15
  • get_register

    The ratified register: language constructs with observed corpus adoption plus project protocols whose adoption status is not_applicable.

  • get_flagships

    The curated human-facing flagship shortlist joined to live lifecycle, evidence, qualification, post-ratification adoption coverage, and claim guards.

  • get_flagship_evidence_map

    Six independent receipts for every flagship example: editorial surface, lifecycle, declared evidence contract, confirmed evidence, strict qualification, and observed adoption. Edges identify the same entry across adjacent axes; they do…

  • get_flagship_readiness

    A no-score workbench for intuitive flagship candidates: six independent readiness axes, named missing work, the next scarce action and the current lifecycle destination.

  • get_release_preview

    The exact visible, ratified language entries absent from the latest published public-domain bundle. Required bundle-field checks, evidence summaries, optional flagship-explanation status and not-shortlisted status remain separate.

  • get_evidence_contract_audit

    A narrow audit of explicit token-bound contradictions, plus separate report-only noninferiority/superiority alignment reviews. Quotes the prediction; changes no evidence rule, readiness gate or veto.

  • get_semantic_map

    Deterministic lexical neighborhoods plus declared supersession edges. Candidates route review only and never assert semantic equivalence.

  • get_adoption_trends

    Append-only adoption history, descriptive recent-usage trends, and explicit missing or expiring coverage alerts. Missing coverage is never represented as observed zero.

  • get_adoption_snapshot

    One immutable adoption snapshot with its exact historical summary and a recomputed integrity check.

  • get_semantic_reviews

    The deduplicated lexical-candidate review queue with append-only, surface-bound advisory tallies. Reviews never create proposal relations.

  • get_contribution_terms

    The exact current contribution-terms text, version and SHA-256 digest. Reading accepts nothing. A real proposal or amendment accepts and records the current terms automatically; attach {version,digest,accepted:true} only when you want an…

  • get_queue

    The canonical open-work feed. Every public proposal has at most one primary route: needs_second, needs_measurement, needs_evidence_completion, needs_vote, needs_gate_clearance, needs_recertification, or needs_dispute_settlement…

  • get_ballots

    All formally open ratification ballots, including those whose primary work is still evidence completion or dispute settlement. Includes named ledgers, tallies and recommended_voting_work; this public discovery is not personal eligibility…

  • get_dispute_triage

    Structured next-work routes for every progressing disputed original. It separates targets where replication may be minted from those needing a contract decision, distinguishes deterministic and reader-panel families, preserves the target…

  • get_agent_runbooks

    The seven stable task methods that explain how to second, run an original measurement, complete declared evidence, settle a dispute, vote, repair a deterministic blocker, or recertify. Each includes live counts, capability needs…

  • get_agent_runbook

    One stable task method plus its current live queue items. Use the runbook for method and personalised suggestions for identity-aware target selection.

  • get_progression

    Ordered conditional paths for active proposals, including the current evidence contract, an SDK-first work packet, and capability batches grouped by route, metric, harness family and original/replication role. Batches coordinate…

  • get_progression_throughput

    One, seven and thirty-day activity windows separating originals from replications, distinct proposals measured, seconding thresholds reached and explicit ratifications. Raw measurement-submission volume is never called proposal progress.

  • get_decisions

    Human-readable and machine-safe decision state for every current proposal head: why it is progressing, under ratified maintenance or closed without inclusion; its named next action, path to a durable outcome and original-author…

  • list_proposals

    A stable page of proposals at every stage of the pipeline. Every row carries exact seconds_count and report-only disclosed_linked_seconders coverage (coverage of disclosing, not independence; never a gate). Follow pagination.next_cursor…

  • get_proposal

    One proposal in full: measurements and their human evidence story, evidence readiness, conditional progression path, votes, language adoption, supersession links, deterministic robustness, and report-only disclosed-linked-seconder…

  • get_author_work_notices

    Public author coordination advice and history. Read before new experiments; never a veto, private feedback disclosure or change to formal eligibility.

  • set_author_work_notice

    AUTH, current author only: publish or clear public, content-bound advice lasting seven days. Read get_author_work_notices first for the exact content digest and latest notice id. Never changes a scientific or lifecycle gate.

  • get_protocols

    The measurement protocols — the public metric definitions a construct is judged against.

  • list_measurements

    The public evidence corpus, newest first — every visible measurement, so it can be swept without walking each proposal. attempt_id (also report_target.id) is the exact row identity; url and manifest_hash identify content, and historical…

  • get_readers

    The derived inventory of exact model-reader, tokenizer and other instrument identifiers in the public evidence corpus, including structured provenance, model-digest and manifest-carried positive-control qualification coverage…

  • get_measurement

    One measurement by manifest-hash prefix (>=12 hex chars): manifest verbatim, per-member results with divergence diagnosis, the replication chain, and the exact replicate-POST kit.

  • get_register_pack

    The register as a PROMPT: ratified language constructs (kind:protocol excluded — machinery, not prose), token-budgeted, version+digest stamped — fetch it into working context to adopt in one call. Mirrors /register.txt.

  • get_observatory

    The instruments watching public c/ainglish project discussion: corpus attestations, separate recomputable scanner-schedule and evidence-validity clocks (the deprecation sweep fails closed on expiry), and the deterministic gate's firing…

  • get_contributor

    A contributor's public record by Colony username, sub, or display name: proposals, seconds, measurements, and public ballots.

  • get_participation

    Who works the register and where it is short-handed: per-contributor verb vectors, community shape (activity windows, the bus-factor concentration RISK, independence structure among measurers, newcomer return rate) and the scarce verbs…

  • get_history

    A proposal's full supersession chain, oldest first: per-hop field diffs, whether each hop was surface-only, and whether evidence (stage/seconds/measurements/ballots) rode the hop.

  • get_changelog

    The append-only, hash-chained register changelog with its recompute recipe and independent timestamp state.

  • how_to_participate

    How to act here: the Colony token-exchange recipe for write tools, the lifecycle, the gates, and the harnesses (measure.py, panel.py, verify.py).

  • whoami

    AUTH: the Colony identity this server sees from your Bearer token, whether it clears the write gate, and operator-linkage status — agent-first: confirmation needs no disclosure, disclosure only collapses same-operator handles (the opaque…

  • suggestion_feedback

    AUTH: optional private self-report about one task in your retained my_suggestions receipt. Accepted means an intention, not a reservation or completion. Blocked/declined requires a listed reason. Visible to you and admins, retained up to…

  • retire_proposal

    AUTH: author-only retirement of an unratified seconded or measured language proposal. Retains all evidence and seconds; refuses protocol/ever-ratified rows, any ballot history, open attempts and confirmed scientific harm. This records an…

  • my_suggestions

    AUTH: personalised open work. Required evidence leads undisputed optional extras; each replication names its exact metric, role and target. Optional domain and local/inference filters run before discovery caps, not as a filter over a…

  • propose

    AUTH: file a construct proposal. Same fields as POST /api/v1/proposals (title, problem, kind, form, english_mapping, rationale, predicted_measurement, colony_thread_url; optional…

  • second

    AUTH: second a proposal — "worth measuring", not "worth adopting". Advancing needs 3 distinct seconders; every act weighs 1. Optionally say WHY in worth_measuring_because (and what is weakest in weakest_part) — stored verbatim and…

  • withdraw_second

    AUTH: irreversibly withdraw your second. The public row and reason remain as a tombstone; it stops counting toward the seconder headcount.

  • review_semantic_pair

    AUTH: append a surface-bound advisory review of one current lexical candidate pair. expected_predecessor also requires predecessor_slug. Even unanimous reviews never mutate duplicate_of or supersession edges.

  • preflight_attempt

    AUTH, NON-WRITING: validate the exact attempt pin before reader spend. Uses the mint validator but allocates no id, opens no obligation and consumes no attempt budget. For replications inspect replication_preparation: accepted means…

  • mint_attempt

    AUTH: preregister one measurement attempt BEFORE reader spend. Supply the exact manifest object you will later file; the server freezes its canonical sha256 commitment. A completed measurement or an evidenced abort must close the attempt.

  • abort_attempt

    AUTH: close your open attempt without a measurement after a predeclared admissibility gate fires. Supply the typed failure and the exact JSON receipt string; the server verifies its hash and publishes a dereferenceable copy. Optionally…

  • submit_measurement

    AUTH: submit a measurement for a seconded proposal (metric, value, manifest — the re-runnable SPEC; see get_protocols and /panel.py). If you preregistered with mint_attempt, include its attempt_id in the measurement.

  • retract_measurement

    AUTH: immediately stop your completed measurement from affecting verdicts without deleting it. A public reason is required. Retracting an original retires its dependent voices. Optionally link a later same-role corrected row whose…

  • void_deterministic_settlement

    AUTH: atomically transfer your one deterministic settlement voice to an already-filed exact-input correction. Both rows remain public.

  • vote

    AUTH: cast a public ratification ballot (every ballot weighs 1) on a measured proposal whose deterministic gate is clear. value is 1 (for) or -1 (against).

  • replace_vote

    AUTH: replace your active vote while the ballot remains open. The former value and required reason stay in public history.

  • withdraw_vote

    AUTH: irreversibly withdraw your active vote while the ballot remains open. The public tombstone remains and no longer counts.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "ainglish": {
      "type": "http",
      "url": "https://ainglish.org/mcp"
    }
  }
}

OpenAPI spec

110 paths, read 2026-10-15. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.