Armature analytics wrapper SDK for Python MCP 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":"armature-mcp-analytics","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.
# Armature MCP Analytics for Python Understand which MCP tools agents use, what users are trying to accomplish, and where calls fail—without building an observability pipeline. [](https://pypi.org/project/armature-mcp-analytics/) [](https://pypi.org/project/armature-mcp-analytics/) [](https://github.com/armature-tech/mcp-analytics-python/actions/workflows/ci.yml) [](LICENSE) [Armature](https://armature.tech) · [TypeScript SDK](https://github.com/armature-tech/mcp-analytics) · [Go SDK](https://github.com/armature-tech/mcp-analytics-go) · [Agent install](SKILL.md) ## Install in 30 seconds ### 1. Install For servers using the standalone FastMCP package: ~~~bash pip install "armature-mcp-analytics[fastmcp]" ~~~ If FastMCP comes from the official MCP Python SDK: ~~~bash pip install "armature-mcp-analytics[mcp]" ~~~ ### 2. Add your regional ingest configuration Create a server in the Armature dashboard for your account's region, then copy **both** generated environment variables into your server environment: ~~~bash export ANALYTICS_INGEST_API_KEY="..." export ANALYTICS_INGEST_URL="https://app.armature.tech/api/mcp-analytics/ingest" # US ~~~ For an EU account, `ANALYTICS_INGEST_URL` is required and must be: ~~~bash export ANALYTICS_INGEST_URL="https://eu.armature.tech/api/mcp-analytics/ingest" ~~~ The URL may be omitted only for US accounts because the SDK defaults to the US endpoint. Keeping the generated URL explicit is recommended and makes the deployment region unambiguous. ### Verify the installation locally The language-independent doctor can inspect a running Python MCP server: ~~~bash npx @armature-tech/mcp-analytics doctor --u…
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.