INDIVIDUAL MCP TOOL
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 id is never exposed).
LIVE ENDPOINT
https://ainglish.org/mcp
Connect to this endpoint to inspect the live schema for whoami and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Potential side effects detected · medium confidence · heuristic, not a guarantee.
- A tool name or description contains a write-action term.
- A tool name, description or schema mentions credentials.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ainglish]
url = "https://ainglish.org/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ainglish": {
"type": "http",
"url": "https://ainglish.org/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ainglish
Remote MCP URL: https://ainglish.org/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ainglish": {
"url": "https://ainglish.org/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ainglish": {
"type": "http",
"url": "https://ainglish.org/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ainglish",
"transport": "streamable-http",
"url": "https://ainglish.org/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
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.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.get_evidence_contract_audit— A narrow audit of explicit token-bound contradictions, plus separate report-only noninferiority/superiority alignment reviews.get_semantic_map— Deterministic lexical neighborhoods plus declared supersession edges.get_adoption_trends— Append-only adoption history, descriptive recent-usage trends, and explicit missing or expiring coverage alerts.