ModelsAtlas
Explore
Atlas / MCP servers / armature-tech / Armature MCP Analytics for TypeScript

Armature MCP Analytics for TypeScriptCAUTION

mcp/armature-tech/mcp-analytics
MCP server by armature-tech · Audited 2026-10-11
⚑ Report / re-scanSource ↗

V0 architecture plan for MCP analytics SDK

Verdict
CAUTION
Grade
D
Trust score
68 /100
Exposed tools
24 23r · 1w · 0d
Transport
stdio · streamable-http
License
Apache-2.0
Stars
1
01

Overview

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

Understand which MCP tools agents use, what users are trying to accomplish, and where calls fail—without building an observability pipeline.

[](https://www.npmjs.com/package/@armature-tech/mcp-analytics) [](https://github.com/armature-tech/mcp-analytics/actions/workflows/ci.yml) [](LICENSE)

Armature · Python SDK · Go SDK · Agent install

Install in 30 seconds

1. Install

~~~bash npm install @armature-tech/mcp-analytics @modelcontextprotocol/sdk@^1.29.0 zod ~~~

MCP SDK 1.29 or newer is required when your tools use Zod 4 raw-shape schemas. MCP SDK 1.20 accepts the package but silently drops fields from those schemas, including Armature's telemetry field.

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 ANALYTICSINGESTAPIKEY="..." export ANALYTICSINGEST_URL="https://app.armature.tech/api/mcp-analytics/ingest" # US ~~~

For an EU account, ANALYTICS_INGEST_URL is required and must be:

~~~bash export ANALYTICSINGESTURL="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

Run the doctor against the same environment and MCP server you plan to deploy:

~~~bash npx @armature-tech/mcp-analytics doctor --url http://localhost:3000/mcp ~~~

For a stdio s

Read from source at commit 177cc9276a02OBSERVED · 2026-10-11
02

Connect

Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.

claude-code
claude mcp add mcp-analytics --env ANALYTICS_INGEST_API_KEY=${ANALYTICS_INGEST_API_KEY} --env SDK_CANARY_INGEST_KEY=${SDK_CANARY_INGEST_KEY} --env SDK_CANARY_READ_API_KEY=${SDK_CANARY_READ_API_KEY} --env VERCEL_TOKEN=${VERCEL_TOKEN} -- npx -y @armature-tech/[email protected]
claude-desktop
{
  "mcpServers": {
    "mcp-analytics": {
      "command": "npx",
      "args": [
        "-y",
        "@armature-tech/[email protected]"
      ],
      "env": {
        "ANALYTICS_INGEST_API_KEY": "${ANALYTICS_INGEST_API_KEY}",
        "SDK_CANARY_INGEST_KEY": "${SDK_CANARY_INGEST_KEY}",
        "SDK_CANARY_READ_API_KEY": "${SDK_CANARY_READ_API_KEY}",
        "VERCEL_TOKEN": "${VERCEL_TOKEN}"
      }
    }
  }
}
03

Exposed tools (24)

23 read · 1 write · 0 destructive.

ToolRiskDescription
canary_echoread
canary_expected_errorread
canary_identityread
create_customerwrite
dispatcher_toolreadDispatcher-path tool.
echoread
failread
lateread
late_toolread
legacyreadPass telemetry.intent with a one-line user intent for analytics.
lookupreadLookup by id.
lookup_customerreadLook up a customer by id.
lookup_customer_notereadReturn a tiny hardcoded customer note.
lookup_customer_profilereadReturn a structured customer profile.
noopread
owned_toolreadOwns its telemetry.
pingreadPing.
previousreadA tool.\n\nInclude telemetry.call_purpose with a short description of this action. Include telemetry.user_intent and telemetry.user_frustration only on the first tool call after each new user message.
racerread
searchread
strict_echoread
trackreadTrack a parcel.${OLD_HINT_SUFFIX}
typedreadtyped tool
zechoread
04

Trust audit

CAUTIONgrade D · trust 68/100 Install with care. The audit found things worth knowing before you trust its output.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeWARN
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
declared (3 observation(s))
Network
declared (6 observation(s))
Shell
declared (2 observation(s))
Dependencies
not all pinned
Secrets in source
found

Findings (19)

MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
SKILL.md:429
- Run a tool against the local mock at `http://127.0.0.1:8787/api/mcp-analytics/ingest`
MEDIUMNetwork egress · net.raw_ip · CWE-200, CWE-319
experimental/mock-env/instrumented-demo-client.ts:35
const armatureTelemetryUrl = `http://127.0.0.1:${armatureAddress.port}/telemetry`;
MEDIUMHard-coded secrets · secret.db_uri · CWE-798, CWE-321
tests/fixtures/telemetry-contract-vectors.json:485
"database_url": "postgres://u:pw@h/db",
MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321
tests/ingest-delivery.test.ts:15
apiKey: "ami_eu_test-key-that-must-not-appear",
MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321
tests/telemetry-capture.test.ts:129
{ token: "sk-proj-AbCdEfGhIjKlMnOpQrStUv123456", blob: "QUFB" },
MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321
tests/telemetry-capture.test.ts:133
{ token: "sk-proj-AbCdEfGhIjKlMnOpQrStUv123456", blob: "[binary removed]" },
MEDIUMHard-coded secrets · secret.generic · CWE-798, CWE-321
tests/v2-adapter.test.ts:551
const secret = "sk-abcdefghijklmnopqrstuvwx";
MEDIUMHard-coded secrets · secret.private_key · CWE-798, CWE-321
tests/fixtures/telemetry-contract-vectors.json:421
"value_parts": ["-----BEGIN RSA PRIVATE KEY-----\n", "MIIEowIBAAKCAQEA7bq0\nMIIEowIBAAKCAQEA7bq1\n", "-----END RSA PRIVATE KEY-----"],
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
experimental/mock-env/dispatcher-recorder-example.ts:1
import { createAnalyticsRecorder } from "../../src/index.js";
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
experimental/mock-env/instrumented-demo-client.ts:5
import { defaultMcpAnalyticsConfig } from "../../src/index.js";
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
experimental/mock-env/instrumented-mock-example-mcp-server.ts:5
} from "../../src/index.js";
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/fixtures/http-instrumented-server.ts:15
import { createMcpAnalyticsServer } from "../../src/index.js";
LOWFilesystem / path · fs.traversal · CWE-22, CWE-59
tests/fixtures/stdio-instrumented-server.ts:11
import { createMcpAnalyticsServer } from "../../src/index.js";
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
CHANGELOG.md:581
`http://127.0.0.1:8787/api/mcp-analytics/ingest`. Customers who installed the SDK in a
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
CHANGELOG.md:589
mock setup needs to set `ANALYTICS_INGEST_URL=http://127.0.0.1:8787/api/mcp-analytics/ingest`
LOWNetwork egress · net.raw_ip · CWE-200, CWE-319
tests/doctor.test.ts:245
await verifyIngest(`http://127.0.0.1:${address.port}/ingest`, "ami_test_secret", 1000);
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
examples/minimal/package.json
@armature-tech/mcp-analytics, @modelcontextprotocol/sdk, zod, @types/node, tsx, typescript
Why it matters. 6 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWSupply chain · supply.unpinned · CWE-829, CWE-1357
package.json
zod, @types/node, tsx, typescript
Why it matters. 4 dependency range(s) float
Fix. pin exact versions or ship a lockfile
LOWPrompt injection · prompt.transfer_instruction · CWE-94, CWE-1427
CHANGELOG.md:397
Requests that DO carry HTTP headers are deliberately excluded from the fallback — many sessions share one long-lived HTTP server process, so their missing session id stays `null` and ingest keeps buck
Why it matters. an instruction to move sensitive data to an outside destination
Fix. remove; a skill never needs the user's secrets off the machine

Gates applied: no_behavioural_pass.

Audited 2026-10-11 · audit v0.4.1 · source sha 177cc9276a02full audit observations/trust-audit/mcp-server/armature-tech__mcp-analytics.json · Report an issue / request a re-scan
05

Audit history

Every audit this server has had. A grade with a past is a grade somebody is still checking.

DateSourceVerdictGradeScoreChange
2026-10-11177cc9276a02CAUTIOND68first audit
06

Questions

What is the @armature-tech/mcp-analytics MCP server?

V0 architecture plan for MCP analytics SDK

What tools does @armature-tech/mcp-analytics expose?

24 in total: 23 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.

Is @armature-tech/mcp-analytics safe to connect to an agent?

With care. The audit graded it D (68/100) and found 19 things worth knowing before you trust this server, listed below with the exact line each was found on.

What credentials does @armature-tech/mcp-analytics need?

It reads ANALYTICS_INGEST_API_KEY, SDK_CANARY_INGEST_KEY, SDK_CANARY_READ_API_KEY and VERCEL_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.

How does @armature-tech/mcp-analytics run?

It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @armature-tech/mcp-analytics at 0.0.0-development.

How current is this page?

The grade is for one exact copy of the source (177cc9276a02), read on 2026-10-11. The repository is watched and re-audited when it changes.

Advertisement