Aglet Tool Technique that adopts MCP (Model Context Protocol) servers.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"aglet-builtin-tool-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# aglet-builtin-tool-mcp > Aglet Tool Technique that adopts MCP (Model Context Protocol) servers. Part of the [Aglet](https://github.com/zyssyz123/agentkit) pluggable Agent runtime — a framework where every Element (perception, memory, planner, tool, executor, safety, output, observability, extensibility) **and** every Technique within an Element is a swappable plugin distributed as its own PyPI package. ## Install ```bash pip install aglet-builtin-tool-mcp ``` This package registers itself with Aglet's `Registry` at import time via Python entry points. Once installed, list it with: ```bash aglet techniques # if your installed version of aglet-cli is recent ``` ## Usage In your `agent.yaml`: ```yaml elements: # Add the Element / technique block this package contributes. ``` See the [main repo's examples](https://github.com/zyssyz123/agentkit/tree/main/examples) for full configurations. ## License Apache-2.0
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.