Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ALPNAI — Agent Performance Tools

REMOTE · ALPNAI.COM · SCANNED SEP 28

Agent cost, latency and quality analysis, report delivery and order status. Crypto payments paused.

Available components

+4 this week 70 Trust /100

Recent critical change

Authorization (15 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security60
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1280 tokens (~128/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 36% of tool parameters carry a description.Partial
  • Structured output schemas are declared (30% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ALPNAI — Agent Performance Tools MCP server?

ALPNAI — Agent Performance Tools is a hosted endpoint at https://alpnai.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · alpnai.com

# add to Claude Code
claude mcp add --transport http fredericmagnathy-ops-alpnai 'https://alpnai.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "fredericmagnathy-ops-alpnai": {
      "url": "https://alpnai.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fredericmagnathy-ops-alpnai": {
      "type": "http",
      "url": "https://alpnai.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.fredericmagnathy-ops-alpnai]
url = "https://alpnai.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fredericmagnathy-ops-alpnai": {
      "type": "remote",
      "url": "https://alpnai.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add fredericmagnathy-ops-alpnai --url 'https://alpnai.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fredericmagnathy-ops-alpnai:
    url: "https://alpnai.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fredericmagnathy-ops-alpnai": {
      "Transport": "http",
      "Url": "https://alpnai.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add fredericmagnathy-ops-alpnai -t streamable-http -u 'https://alpnai.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "fredericmagnathy-ops-alpnai": {
      "type": "http",
      "url": "https://alpnai.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +2
    • DNSSEC: unverified → pass ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 28 Sept 2026 · Probed https://alpnai.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=alpnai.com CN=WE1,O=Google Trust Services,C=US 13 Sept 2026 13 Dec 2026 ECDSA 256 ECDSA-SHA256 5ff4bb5cd916c9ee0e3951b6f52bf627
SANs: alpnai.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of alpnai.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
alpnai.com. present 60312 13 Verified
alpnai.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://alpnai.com/api/mcp Verified 200
http (plaintext) http://alpnai.com/api/mcp HTTPS enforced 302 https://alpnai.com/api/mcp
MCP tools · 10 exposed · ~1,280 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
analyze_agent_latency ~128

Find slow agent workflows and retry overhead before scaling. Supply recorded attempts with task_id, workflow, variant, cost_usd, success and optional latency_ms. Returns P50/P95 of summed recorded attempt durations per task, retry counts, duration coverage and an optional P95 threshold check for each workflow and variant. Missing durations produce null percentiles, not zero latency. This measures supplied durations, not live end-to-end service latency. Free calculation; requires an active ALPNAI agent key; no payment or automatic deployment.

NameTypeReqDescription
configobject––
runsarrayyes–
NameTypeReqDescription
groupsarrayyes–
measurementstringyes–
percentile_methodstringyes–
schema_versionstringyes–

No examples provided.

audit_agent_costs ~62

Free comparison of cost per successful task on supplied paired traces. Requires a sandbox agent key. No purchase, storage, external model call or automatic deployment. Success labels are supplied by the client.

NameTypeReqDescription
configobject––
runsarrayyes–
NameTypeReqDescription
automatic_deployment_authorizedbooleanyes–
configobjectyes–
data_provenancestringyes–
experimental_bias_controlstringyes–
input_attempt_recordsintegeryes–
methodologyobjectyes–
purposestringyes–
schema_versionstringyes–
workflowsarrayyes–

No examples provided.

check_agent_quality ~131

Check whether a candidate agent workflow regresses before replacing the baseline. Supply baseline and candidate attempts on matching task IDs with client-provided success labels and costs. Returns observed success rates, task-set matching, sample-size, success, latency and cost gates, plus a decision such as collect_more_data, quality_regression or candidate_for_controlled_trial. Optional thresholds use config. It evaluates the recorded labels, not the correctness of answers or future performance. Free calculation; requires an active ALPNAI agent key; no payment or automatic deployment.

NameTypeReqDescription
configobject––
runsarrayyes–
NameTypeReqDescription
configobjectyes–
schema_versionstringyes–
workflowsarrayyes–

No examples provided.

get_catalog ~39

Discover cost, latency and quality analysis APIs, their inputs, outputs, free reproducible example, authentication and current payment availability. No payment or budget debit.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_free_sample ~25

Read a dated primary-source sample about OpenAI. Not real-time or exhaustive.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_order ~97

Follow one existing commercial order owned by the authenticated agent, including after commerce is paused. May record a finalized blockchain receipt or release an expired, never-submitted reservation. Does not create an order, authorize spending or submit a payment. Pending results provide the same order ID and Retry-After; repeat get_order, never purchase again. Requires only the existing agent key.

NameTypeReqDescription
order_idstringyesThe original order_id returned by the purchase.

No output schema declared.

No examples provided.

purchase_changes ~208

Get Change Set for 0.05 USDC. Default mode sandbox creates a test receipt and debits only the test budget. Explicit mode live uses x402 only when commerce, owner mandate and billing eligibility are enabled. An unpaid result contains PaymentRequired in structuredContent and content. Retry the same tool and idempotency key with the signed PaymentPayload in params._meta["x402/payment"]. Confirmed settlement is returned in result._meta["x402/payment-response"]. For a pending order, call get_order with the original order_id; do not submit another payment. REST continuation and PAYMENT-SIGNATURE headers remain supported. Never send a private key.

NameTypeReqDescription
idempotency_keystringyes–
mandate_idstring–Owner-authorized commercial mandate ID. Alternatively send X-AlpNAI-Mandate in the MCP request headers.
modestring–Sandbox is the default. Live explicitly requests the existing authorized x402 purchase flow.
sincestring––

No output schema declared.

No examples provided.

purchase_evidence ~209

Get Evidence Pack for 0.25 USDC. Default mode sandbox creates a test receipt and debits only the test budget. Explicit mode live uses x402 only when commerce, owner mandate and billing eligibility are enabled. An unpaid result contains PaymentRequired in structuredContent and content. Retry the same tool and idempotency key with the signed PaymentPayload in params._meta["x402/payment"]. Confirmed settlement is returned in result._meta["x402/payment-response"]. For a pending order, call get_order with the original order_id; do not submit another payment. REST continuation and PAYMENT-SIGNATURE headers remain supported. Never send a private key.

NameTypeReqDescription
idempotency_keystringyes–
mandate_idstring–Owner-authorized commercial mandate ID. Alternatively send X-AlpNAI-Mandate in the MCP request headers.
modestring–Sandbox is the default. Live explicitly requests the existing authorized x402 purchase flow.
sincestring––

No output schema declared.

No examples provided.

purchase_snapshot ~207

Get Snapshot for 0.01 USDC. Default mode sandbox creates a test receipt and debits only the test budget. Explicit mode live uses x402 only when commerce, owner mandate and billing eligibility are enabled. An unpaid result contains PaymentRequired in structuredContent and content. Retry the same tool and idempotency key with the signed PaymentPayload in params._meta["x402/payment"]. Confirmed settlement is returned in result._meta["x402/payment-response"]. For a pending order, call get_order with the original order_id; do not submit another payment. REST continuation and PAYMENT-SIGNATURE headers remain supported. Never send a private key.

NameTypeReqDescription
idempotency_keystringyes–
mandate_idstring–Owner-authorized commercial mandate ID. Alternatively send X-AlpNAI-Mandate in the MCP request headers.
modestring–Sandbox is the default. Live explicitly requests the existing authorized x402 purchase flow.
sincestring––

No output schema declared.

No examples provided.

save_project_report ~174

Compute and save an aggregate performance report in the fixed Projects destination authorized by the account owner. Uses the existing free or paid report allowance. Requires an active agent key and explicit owner write permission. Reuse request_id with identical content to retry within the same permission grant. No report reading, deletion, subscription or payment authorization. Send measurements without secrets.

NameTypeReqDescription
inputobjectyesRecorded attempts, not prompts or secrets. Identical rows count as separate attempts. All three analysis tools accept this same input. The runtime validator additionally enforces six-decimal micro-US…
request_idstringyes–
titlestringyes–

No output schema declared.

No examples provided.

Common questions

What is the ALPNAI — Agent Performance Tools MCP server?

ALPNAI — Agent Performance Tools is an MCP server listed in the public MCP registry as io.github.fredericmagnathy-ops/alpnai. Agent cost, latency and quality analysis, report delivery and order status. Crypto payments paused. This page covers its hosted endpoint (https://alpnai.com/api/mcp).

Is the ALPNAI — Agent Performance Tools MCP server safe to use?

ALPNAI — Agent Performance Tools scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ALPNAI — Agent Performance Tools MCP server expose?

ALPNAI — Agent Performance Tools exposes 10 tools: get_catalog, get_free_sample, audit_agent_costs, analyze_agent_latency, check_agent_quality, and 5 more. Their descriptions and schemas cost roughly 1,280 tokens of context every time the server is loaded.

Does the ALPNAI — Agent Performance Tools MCP server require authentication?

No. We connected to ALPNAI — Agent Performance Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ALPNAI — Agent Performance Tools MCP server still maintained?

ALPNAI — Agent Performance Tools is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.