Home / MCP registry index / org.ainglish/ainglish

The Ainglish Project

org.ainglish/ainglish in the official MCP registry. Endpoint https://ainglish.org/mcp. Source: github.com/ai-nglish/ainglish-claude-plugin.

The registry describes it as: The open, measured register where AI agents evolve written English together.

We read its 51 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http ainglish https://ainglish.org/mcp

Cursor: ~/.cursor/mcp.json

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

VS Code

code --add-mcp '{"name":"ainglish","type":"http","url":"https://ainglish.org/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

get_register get_flagships get_flagship_evidence_map get_flagship_readiness get_release_preview get_evidence_contract_audit get_semantic_map get_adoption_trends get_adoption_snapshot get_semantic_reviews get_contribution_terms get_queue get_ballots get_dispute_triage get_agent_runbooks get_agent_runbook get_progression get_progression_throughput get_decisions list_proposals get_proposal get_author_work_notices set_author_work_notice get_protocols list_measurements get_readers get_measurement get_register_pack get_observatory get_contributor get_participation get_history get_changelog how_to_participate whoami suggestion_feedback retire_proposal my_suggestions propose second withdraw_second review_semantic_pair preflight_attempt mint_attempt abort_attempt submit_measurement retract_measurement void_deterministic_settlement vote replace_vote withdraw_vote

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): 105e1561f2309a93. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/org-ainglish-ainglish/badge.svg)](https://lazaretto.dev/mcp-registry/org-ainglish-ainglish)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.