A client library and toolkit for interacting with ALPNAI services, including payment-based access to data products (snapshot, changes, evidence) and audit/reporting capabilities
This server exhibits severe definition quality gaps across nearly all dimensions. Tool names lack consistent verb-noun structure (e.g., 'AlpNAIBuyer.purchase' vs 'checkAuthorization'). Descriptions vary wildly in quality: some are detailed (validateQuote: 94 chars), others are vague ('FileJournal.exclusive': 79 chars, unclear what 'operation' parameter does). Critical parameter descriptions are missing or incomplete, 'operation' in FileJournal.exclusive is described only as 'Async operation to execute under lock' with no guidance on signature or return type. Input schemas are partially visible but lack proper JSON Schema structure with explicit type definitions for complex objects (e.g., 'a' parameter in checkAuthorization is typed as 'object' with no nested schema). Output schemas are entirely undocumented. Error handling is minimal, no recovery guidance, no error categorization. Security concerns: checkAuthorization and validateQuote expose payment/authorization logic without clear permission gates. No pagination support visible. Tool composition is poor: FileJournal.exclusive, load, and save should be internal implementation details, not exposed tools. Baseline comparison: average tool description is 194 chars; this server averages ~85 chars with many under 50. Average params per tool is 4; this server ranges 1-8 with inconsistent naming (payer vs from, now vs expiry).
Poll the status of a pending purchase order
Execute a purchase of an ALPNAI product (snapshot, changes, or evidence) with payment authorization and settlement tracking
Read data from ALPNAI endpoints (catalog, snapshot, changes, evidence, or orders)
Execute an operation with exclusive filesystem-based locking for a given identity
Load a purchase record entry from the filesystem journal
Durably save a purchase record entry to the filesystem journal with atomic writes
Free Spend Proof audit client. Validates and submits task cost audit data without requiring purchases or wallet signing.
Tool names lack consistent verb-noun structure. Mix of camelCase class methods (AlpNAIBuyer.purchase), snake_case (save_project), and bare verbs (checkAuthorization). LLMs struggle to parse intent from inconsistent naming conventions.
Input schemas lack proper JSON Schema structure. Parameters typed as bare 'object' with no nested property definitions (e.g., 'a' in checkAuthorization, 'q' in validateQuote, 'operation' in FileJournal.exclusive). LLMs cannot infer required fields or nested structure.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 32 | 2026-07-28+ | v2 |
ALPNAI sandbox client for purchasing data products (snapshot, changes, evidence) with payment authorization and state management
EIP-3009 only. Used both before the injected signer and after factory return. Validates payment authorization parameters including sender, receiver, amount, and time validity windows.
Accept an existing policy-controlled wallet adapter; no key loading or wallet setup. Creates payment payloads for EVM-based transactions on Base network.
Generate reviewed public discovery declarations for ALPNAI products with public header prerequisites and schema validation
Save a computed ALPNAI report through an owner-granted write-only agent with idempotent request tracking
Free ALPNAI Trace Audit. Validates and submits trace events without credentials, redirects, retries or payments.
Validate all payment-bearing facts before the payment factory is called. Checks quote structure, payment requirements, commercial terms, and public discovery declarations.
Verify ALPNAI performance sample contract and independently recompute core metrics (cost, latency, quality) without account, API key, signing, purchase or persistent writes
Output schemas entirely undocumented. No tool describes what it returns, field types, or structure. Agents cannot plan downstream calls or extract required data (e.g., what does AlpNAIBuyer.purchase return? An order ID? A receipt? A status object?).
FileJournal tools (exclusive, load, save) should not be exposed as MCP tools. These are internal implementation details of a Journal interface. Exposing them violates single-responsibility principle and confuses agents about whether to call FileJournal.save or AlpNAIBuyer.purchase.
No error handling guidance. Tools like checkAuthorization and validateQuote fail with cryptic codes ('authorization_outside_policy', 'invalid_quote') but provide no recovery hints. Agents cannot self-correct or know whether to retry, ask the user, or abort.