# SALT19 Agent Utility Grid (remote · api.salt19.com) MCP/x402 tools with bounded decisions, adaptive pricing, and Proof402 machine-commerce receipts. - Trust score: 82/100 (high trust) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-09-20 ## Components - remote · `api.salt19.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/gabrielallit1-salt19-agent-utility-grid/api.md), [page](https://verifymcp.io/servers/gabrielallit1-salt19-agent-utility-grid/api) ## Channel facts - Endpoint: `https://api.salt19.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.5.1` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-09-20. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 53/100 - AI-judged instruction clarity (good). - Context-footprint check failed: tool/resource definitions use about 7365 tokens (~223/item across 33 items; 33 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 90/100 - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 92/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 74% of tool parameters carry a description. - Structured output schemas are declared (52% of tools); any adoption earns full credit. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 33 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a current MCP spec version (2026-07-28). ## Install ### How do I install the SALT19 Agent Utility Grid MCP server? SALT19 Agent Utility Grid is a hosted endpoint at https://api.salt19.com/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. ### Claude ```bash claude mcp add --transport http gabrielallit1-salt19-agent-utility-grid 'https://api.salt19.com/mcp' ``` ### Cursor ```json { "mcpServers": { "gabrielallit1-salt19-agent-utility-grid": { "url": "https://api.salt19.com/mcp" } } } ``` ### VS Code ```json { "servers": { "gabrielallit1-salt19-agent-utility-grid": { "type": "http", "url": "https://api.salt19.com/mcp" } } } ``` ### Codex ```toml [mcp_servers.gabrielallit1-salt19-agent-utility-grid] url = "https://api.salt19.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "gabrielallit1-salt19-agent-utility-grid": { "type": "remote", "url": "https://api.salt19.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add gabrielallit1-salt19-agent-utility-grid --url 'https://api.salt19.com/mcp' --transport streamable-http ``` ### Hermes ```yaml mcp_servers: gabrielallit1-salt19-agent-utility-grid: url: "https://api.salt19.com/mcp" ``` ### Netclaw ```json { "McpServers": { "gabrielallit1-salt19-agent-utility-grid": { "Transport": "http", "Url": "https://api.salt19.com/mcp" } } } ``` ### Vellum ```bash assistant mcp add gabrielallit1-salt19-agent-utility-grid -t streamable-http -u 'https://api.salt19.com/mcp' ``` ### Other ```json { "mcpServers": { "gabrielallit1-salt19-agent-utility-grid": { "type": "http", "url": "https://api.salt19.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-09-20 (score 82, +1) No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-18 (score 81, +1) No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-16 (score 80, +1) - [security] Tool “agent-claim-output-verifier” rewrote its description, which is the text the model reads - [security] Tool “agent-code-change-risk-gate” rewrote its description, which is the text the model reads - [security] Tool “agent-decision-preflight” rewrote its description, which is the text the model reads - [security] Tool “agent-plan-verifier” rewrote its description, which is the text the model reads - [security] Tool “commerce-decision” rewrote its description, which is the text the model reads - [security] Tool “commerce-receipt” rewrote its description, which is the text the model reads - [security] Tool “commerce-verify” rewrote its description, which is the text the model reads - [security] Tool “dependency-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “dependency-upgrade-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “github-repo-preflight” rewrote its description, which is the text the model reads - [security] Tool “npm-package-intel” rewrote its description, which is the text the model reads - [security] Tool “repo-adoption-go-no-go” rewrote its description, which is the text the model reads ### 2026-09-14 (score 79, +1) - [security] Tool “agent-claim-output-verifier” rewrote its description, which is the text the model reads - [security] Tool “agent-code-change-risk-gate” rewrote its description, which is the text the model reads - [security] Tool “agent-decision-preflight” rewrote its description, which is the text the model reads - [security] Tool “agent-plan-verifier” rewrote its description, which is the text the model reads - [security] Tool “dependency-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “dependency-upgrade-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “repo-adoption-go-no-go” rewrote its description, which is the text the model reads ### 2026-09-13 (score 78, 0) - [security] Tool “agent-claim-output-verifier” rewrote its description, which is the text the model reads - [security] Tool “agent-code-change-risk-gate” rewrote its description, which is the text the model reads - [security] Tool “agent-decision-preflight” rewrote its description, which is the text the model reads - [security] Tool “agent-plan-verifier” rewrote its description, which is the text the model reads - [security] Tool “dependency-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “dependency-upgrade-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “github-repo-preflight” rewrote its description, which is the text the model reads - [security] Tool “npm-package-intel” rewrote its description, which is the text the model reads - [security] Tool “repo-adoption-go-no-go” rewrote its description, which is the text the model reads - [functional] Server version: 0.5.0 → 0.5.1 ### 2026-09-12 (score 78, +1) - [security] Tool “agent-claim-output-verifier” rewrote its description, which is the text the model reads - [security] Tool “agent-code-change-risk-gate” rewrote its description, which is the text the model reads - [security] Tool “dependency-go-no-go” rewrote its description, which is the text the model reads - [security] Tool “npm-package-intel” rewrote its description, which is the text the model reads ### 2026-09-10 (score 77, +1) No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-09-08 (score 76, +1) - [security] Tool “agent-decision-preflight” rewrote its description, which is the text the model reads ## MCP tools (33) ### `find-salt19-tool` (~128 tokens) Find the Best SALT19 Tool FREE START-HERE ROUTER. Describe the fresh external fact, live state, developer intelligence, or bounded decision you need. Returns the best current SALT19 tool, live price, schema, alternatives, and exact x402 preflight next step. No payment is required for routing. Input parameters: - `max_price_usd` (number): Optional hard maximum price for the eventual paid tool call. - `need` (string, required): Natural-language description of the external state or machine operation needed. - `prefer_fresh_state` (boolean): Prefer low-friction Fresh-State primitives when they satisfy the request. Output parameters: - `alternatives` (array) - `next_action` (object) - `selected` (object|null) - `selection_id` (string) ### `salt19-pricing` (~65 tokens) SALT19 Live Pricing FREE catalog/pricing surface. Returns current discoverable SALT19 products, live x402 prices, schemas, and Fresh-State acquisition roles so an agent can budget before choosing a paid call. Input parameters: - `max_price_usd` (number) - `tier` (string) Output parameters: - `count` (integer) - `products` (array) - `start_here` (object) ### `base-contract-state` (~150 tokens) Base Contract State Inspect whether a Base address currently has deployed bytecode and return code size plus best-effort ERC-20 metadata. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `address` (string, required) ### `base-token-allowance` (~173 tokens) Base Token Allowance Read a live ERC-20 allowance on Base for an owner/spender pair without an API key. Returns the current block and raw token units. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `owner` (string, required) - `spender` (string, required) - `token_address` (string, required) ### `base-token-balance` (~166 tokens) Base Token Balance Read a live ERC-20 token balance on Base and return raw units plus best-effort token decimals/symbol metadata without signup or an API key. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `owner` (string, required) - `token_address` (string, required) ### `base-transaction-status` (~158 tokens) Base Transaction Status Check current Base transaction receipt state and return PENDING, CONFIRMED_SUCCESS, or CONFIRMED_REVERTED with block and gas evidence. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `transaction_hash` (string, required) ### `base-wallet-balance` (~147 tokens) Base Wallet Balance Read a wallet's live native ETH balance on Base at the latest block without an API key. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `address` (string, required) ### `github-repo-facts` (~157 tokens) Github Repo Facts Return current public GitHub repository facts such as archive state, license, stars, forks, branch and latest push without the premium adoption decision. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `repo` (string, required) ### `npm-package-facts` (~157 tokens) Npm Package Facts Return live npm registry facts for the latest or requested package version without the higher-priced vulnerability and adoption decision layer. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `package` (string, required) - `version` (string) ### `nws-active-alerts` (~155 tokens) Nws Active Alerts Return current U.S. National Weather Service active alerts for a state or territory as compact structured JSON. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `area` (string, required) - `limit` (integer) ### `sec-company-facts` (~158 tokens) Sec Company Facts Return selected latest SEC XBRL company facts from EDGAR's live companyfacts feed with source dates and units. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `cik` (string, required) - `concepts` (array) ### `sec-recent-filings` (~159 tokens) Sec Recent Filings Return recent SEC EDGAR filings for a company CIK from the live SEC submissions feed, normalized for agent consumption. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `cik` (string, required) - `limit` (integer) ### `url-to-llm-markdown` (~222 tokens) Url To Llm Markdown Fetch a public web page, remove scripts/styles/navigation noise, and return bounded LLM-friendly Markdown plus canonical URL and fetch provenance. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Security boundary: public HTTP(S) only. Credentialed URLs, localhost, .local/.internal hosts, loopback, RFC1918/private, link-local and cloud-metadata targets are rejected; every redirect target is revalidated; fetches are time-bounded and response-size bounded. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `max_chars` (integer) - `url` (string, required) ### `usgs-earthquakes` (~165 tokens) Usgs Earthquakes Query recent USGS earthquake events by lookback window and minimum magnitude and return compact live event state. Price: $0.01 via x402. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier preserved across challenge/payment/retries. - `_x402_payment_signature` (string): Optional x402 payment proof. Omit on the first call; include after satisfying the challenge. - `hours` (integer) - `limit` (integer) - `min_magnitude` (number) ### `agent-claim-output-verifier` (~321 tokens) Agent Claim Output Verifier Map an autonomous agent claim or output to supplied evidence and return SUPPORTED, PARTIALLY_SUPPORTED, NOT_PROVEN, or CONTRADICTED with explicit unsupported elements, contradictions, missing evidence, and recommended verification. Price: $0.50 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `claim` (string, required): Input parameter "claim" for the agent-claim-output-verifier tool. - `context` (string): Input parameter "context" for the agent-claim-output-verifier tool. - `evidence` (array): Input parameter "evidence" for the agent-claim-output-verifier tool. - `required_standard` (string): Input parameter "required_standard" for the agent-claim-output-verifier tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `agent-code-change-risk-gate` (~317 tokens) Agent Code Change Risk Gate Static pre-merge risk gate for autonomous code changes: inspect a supplied unified diff for security-sensitive surfaces, destructive operations, architecture/constraint conflicts, test requirements, rollback risk, and bounded breaking-change risk before an agent merges or deploys. Price: $1.25 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `constraints` (array): Input parameter "constraints" for the agent-code-change-risk-gate tool. - `context` (string): Input parameter "context" for the agent-code-change-risk-gate tool. - `diff` (string, required): Input parameter "diff" for the agent-code-change-risk-gate tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `agent-decision-preflight` (~298 tokens) Agent Decision Preflight Before an autonomous coding agent installs or adopts software, return a bounded GO, WARN, or BLOCK decision with evidence and a portable SALT19 verification receipt. Price: $0.50 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `constraints` (object): Input parameter "constraints" for the agent-decision-preflight tool. - `decision_type` (string, required): Input parameter "decision_type" for the agent-decision-preflight tool. - `target` (object, required): Input parameter "target" for the agent-decision-preflight tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `agent-plan-verifier` (~300 tokens) Agent Plan Verifier Verify an autonomous agent plan before execution for missing preconditions, destructive steps, unsafe ordering, goal misalignment, constraint violations, and repair actions, returning a bounded GO/WARN/BLOCK result. Price: $0.75 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `constraints` (array): Input parameter "constraints" for the agent-plan-verifier tool. - `goal` (string, required): Input parameter "goal" for the agent-plan-verifier tool. - `plan` (array, required): Input parameter "plan" for the agent-plan-verifier tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `commerce-decision` (~296 tokens) Commerce Decision Before an autonomous agent pays an x402 challenge, bind the request, accepted payment offer, and machine spending policy into a deterministic GO/WARN/BLOCK decision with SHA-256 commitments. Price: $0.02 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `payment_required` (object, required): Input parameter "payment_required" for the commerce-decision tool. - `policy` (object, required): Input parameter "policy" for the commerce-decision tool. - `request` (object, required): Input parameter "request" for the commerce-decision tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `commerce-receipt` (~418 tokens) Commerce Receipt Verify an x402 commercial state and persist a signed Ed25519 Proof402 receipt whose Commerce State Root commits request, offer, policy, payment, settlement, and delivery evidence; receipts are later Merkle-batched for public inclusion proofs. Price: $0.05 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `delivery` (required): Input parameter "delivery" for the commerce-receipt tool. - `expected_delivery` (object): Input parameter "expected_delivery" for the commerce-receipt tool. - `payment_payload` (object, required): Input parameter "payment_payload" for the commerce-receipt tool. - `payment_required` (object, required): Input parameter "payment_required" for the commerce-receipt tool. - `policy` (object): Input parameter "policy" for the commerce-receipt tool. - `request` (object, required): Input parameter "request" for the commerce-receipt tool. - `settlement` (object, required): Input parameter "settlement" for the commerce-receipt tool. - `target_salt19_operation_id` (string): Input parameter "target_salt19_operation_id" for the commerce-receipt tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `commerce-verify` (~406 tokens) Commerce Verify Verify that an x402 v2 payment payload, settlement evidence, original request, accepted offer, spending policy, and delivered response are mutually bound; SALT19 operations can additionally be checked against authoritative D1 commercial state. Price: $0.03 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `delivery` (required): Input parameter "delivery" for the commerce-verify tool. - `expected_delivery` (object): Input parameter "expected_delivery" for the commerce-verify tool. - `payment_payload` (object, required): Input parameter "payment_payload" for the commerce-verify tool. - `payment_required` (object, required): Input parameter "payment_required" for the commerce-verify tool. - `policy` (object): Input parameter "policy" for the commerce-verify tool. - `request` (object, required): Input parameter "request" for the commerce-verify tool. - `settlement` (object, required): Input parameter "settlement" for the commerce-verify tool. - `target_salt19_operation_id` (string): Input parameter "target_salt19_operation_id" for the commerce-verify tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `dependency-go-no-go` (~286 tokens) Dependency Go No Go Dependency approval decision for coding agents: decide whether an npm dependency or package is safe to install or adopt and return GO, WARN, or BLOCK using vulnerabilities, security, license, maintenance, deprecation, and package metadata. Price: $0.25 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `package` (string, required): Input parameter "package" for the dependency-go-no-go tool. - `version` (string): Input parameter "version" for the dependency-go-no-go tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `dependency-upgrade-go-no-go` (~374 tokens) Dependency Upgrade Go No Go Compare current and target npm versions and return GO/WARN/BLOCK plus UPGRADE/DEFER/BLOCK guidance, bounded semver risk, OSV security implications, recommended tests, and explicit NOT_PROVEN runtime, peer, migration, and ecosystem compatibility boundaries. Price: $0.20 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `constraints` (array): Input parameter "constraints" for the dependency-upgrade-go-no-go tool. - `current_version` (string, required): Input parameter "current_version" for the dependency-upgrade-go-no-go tool. - `framework` (string): Input parameter "framework" for the dependency-upgrade-go-no-go tool. - `package` (string, required): Input parameter "package" for the dependency-upgrade-go-no-go tool. - `runtime` (string): Input parameter "runtime" for the dependency-upgrade-go-no-go tool. - `target_version` (string, required): Input parameter "target_version" for the dependency-upgrade-go-no-go tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `github-repo-preflight` (~266 tokens) Github Repo Preflight GitHub repository due diligence for coding agents: evaluate whether a public or open-source repository is safe and maintained enough to adopt using license, maintenance, release freshness, activity, project health, and risk signals. Price: $0.10 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `repo` (string, required): Input parameter "repo" for the github-repo-preflight tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `model-memory-fit` (~328 tokens) Model Memory Fit Can this AI model run on my graphics card? Estimate model memory requirements and check whether a quantized LLM fits available GPU VRAM before loading or local inference. Price: $0.05 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `parameter_count_b` (number, required): Input parameter "parameter_count_b" for the model-memory-fit tool. - `quantization_bits` (number, required): Input parameter "quantization_bits" for the model-memory-fit tool. - `runtime_overhead_ratio` (number): Input parameter "runtime_overhead_ratio" for the model-memory-fit tool. - `vram_gb` (number, required): Input parameter "vram_gb" for the model-memory-fit tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `npm-package-intel` (~273 tokens) Npm Package Intel Check whether an npm package is deprecated or vulnerable before installing it, including vulnerabilities, license, maintenance, freshness, dependency health, and package.json risk signals. Price: $0.05 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `package` (string, required): Input parameter "package" for the npm-package-intel tool. - `version` (string): Input parameter "version" for the npm-package-intel tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `repo-adoption-go-no-go` (~271 tokens) Repo Adoption Go No Go Repository adoption decision for autonomous coding agents using public GitHub maintenance, archive, license, and repository-health evidence, with explicit UNKNOWN and NOT_PROVEN boundaries for dependency, security, compatibility, integration, and project-fit claims. Price: $0.35 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `repo` (string, required): Input parameter "repo" for the repo-adoption-go-no-go tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `url-http-preflight` (~320 tokens) Url Http Preflight Inspect a URL before an autonomous agent calls it, and preflight or verify a website or external API endpoint is healthy and safe to call by checking HTTP status, redirects, latency, and security headers. Price: $0.03 via x402. Generate one _salt19_operation_id per intended purchase, preserve it across retries, and add _x402_payment_signature after satisfying the challenge. A stable _salt19_operation_id is required and makes semantic retries at-most-once. _salt19_operation_id is recommended but optional for standard x402 compatibility. Security boundary: public HTTP(S) only. Credentialed URLs, localhost, .local/.internal hosts, loopback, RFC1918/private, link-local and cloud-metadata targets are rejected; every redirect target is revalidated; fetches are time-bounded and response-size bounded. Input parameters: - `_salt19_handoff_id` (string): Optional SALT19 authorization handoff correlation. Preserve the same value across challenge, local signing, and paid retry. - `_salt19_operation_id` (string): Optional but recommended semantic purchase identifier. Generate once per intended purchase and preserve it across challenge, payment, timeout recovery, and retries for the strongest at-most-once cont… - `_x402_payment_signature` (string): Optional x402 PAYMENT-SIGNATURE proof. Omit on the first call to receive the payment challenge; include after satisfying that challenge. - `url` (string, required): Input parameter "url" for the url-http-preflight tool. Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `verify-decision-receipt` (~73 tokens) Verify SALT19 Decision Receipt Free integrity lookup for a SALT19 decision receipt. verified=true proves the stored evidence still matches its recorded digest; it does not prove the underlying software is safe. _salt19_operation_id is recommended but optional for standard x402 compatibility. Input parameters: - `id` (string, required): SALT19 decision receipt UUID Output parameters: - `operation_id`: Client-controlled semantic purchase identifier when applicable. - `response`: Tool-specific structured response payload when execution completes. - `status` (string): SALT19 execution, payment, availability, or verification state. - `tool` (string): Canonical SALT19 tool identifier when the result is tool-specific. ### `x402-payment-preflight` (~124 tokens) SALT19 x402 Payment Preflight Free buyer-side compatibility preflight. Returns the live SALT19 price, Base/USDC requirement, optional public wallet-balance sufficiency, and the exact next action without signing or moving funds. Input parameters: - `autonomous_spend_allowed` (boolean) - `max_price_usd` (number) - `product` (string, required) - `supported_assets` (array) - `supported_networks` (array) - `supports_x402` (boolean) - `wallet_address` (string): Optional public EVM address only; never provide a private key. ### `report-payment-capability` (~135 tokens) Report x402 Payment Capability Free cooperative telemetry tool for reporting whether a client can use x402/Base/USDC or why it declined. Never submit private keys, payment signatures, or secret wallet material. Input parameters: - `autonomous_spend_allowed` (string) - `decline_reason` (string, required) - `max_purchase_usd` (number) - `product` (string) - `session_id` (string): Optional opaque session label; stored only as a SHA-256 fingerprint. - `supported_assets` (array) - `supported_networks` (array) - `supports_x402` (boolean) - `wallet_available` (string) ### `x402-authorization-handoff` (~108 tokens) SALT19 x402 Authorization Handoff Free handoff tool that generates a live PAYMENT-REQUIRED challenge for a concrete paid request, returns exact REST and MCP retry templates, and creates a correlation ID. It never signs or moves buyer funds. Input parameters: - `arguments` (object, required): The exact paid tool arguments that will be retried after authorization. Do not include private keys, seed phrases, or payment signatures. - `operation_id` (string) - `product` (string, required) - `session_id` (string) ### `report-x402-authorization-progress` (~100 tokens) Report x402 Authorization Progress Free cooperative telemetry for the local buyer authorization path. Report stage metadata only; never include private keys, seed phrases, raw signatures, or PAYMENT-SIGNATURE values. Input parameters: - `client_timestamp` (string) - `error_code` (string) - `handoff_id` (string, required) - `sdk` (string) - `signer_available` (string) - `signer_kind` (string) - `stage` (string, required) ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/gabrielallit1-salt19-agent-utility-grid/api#diagnostics ## Score history - 2026-09-20: 82 - 2026-09-19: 81 - 2026-09-18: 81 - 2026-09-17: 80 - 2026-09-16: 80 - 2026-09-15: 79 - 2026-09-14: 79 - 2026-09-13: 78 - 2026-09-12: 78 - 2026-09-11: 77 - 2026-09-10: 77 - 2026-09-09: 76 - 2026-09-08: 76 - 2026-09-07: 75 - 2026-09-06: 75 - 2026-09-05: 75 - 2026-09-04: 74 - 2026-09-03: 74 - 2026-09-02: 73 - 2026-09-01: 73 - 2026-08-31: 72 - 2026-08-30: 72 - 2026-08-29: 71 - 2026-08-28: 69 - 2026-08-27: 68 - 2026-08-26: 68 - 2026-08-25: 66 - 2026-08-24: 67 ## Common questions ### What is the SALT19 Agent Utility Grid MCP server? SALT19 Agent Utility Grid is an MCP server listed in the public MCP registry as io.github.GabrielAllit1/salt19-agent-utility-grid. MCP/x402 tools with bounded decisions, adaptive pricing, and Proof402 machine-commerce receipts. This page covers its hosted endpoint (https://api.salt19.com/mcp). ### Is the SALT19 Agent Utility Grid MCP server safe to use? SALT19 Agent Utility Grid scores 82 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 SALT19 Agent Utility Grid MCP server expose? SALT19 Agent Utility Grid exposes 33 tools: find-salt19-tool, salt19-pricing, base-contract-state, base-token-allowance, base-token-balance, and 28 more. Their descriptions and schemas cost roughly 7,174 tokens of context every time the server is loaded. ### Does the SALT19 Agent Utility Grid MCP server require authentication? No. We connected to SALT19 Agent Utility Grid without credentials and it answered, so anything it exposes is reachable by anyone who knows the address. ### Is the SALT19 Agent Utility Grid MCP server still maintained? SALT19 Agent Utility Grid is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ## Links - Remote endpoint: https://api.salt19.com/mcp - Website: https://salt19.com/agent-utility-grid/ - Changelog RSS feed: https://verifymcp.io/servers/gabrielallit1-salt19-agent-utility-grid/api.xml - Changelog JSON feed: https://verifymcp.io/servers/gabrielallit1-salt19-agent-utility-grid/api.json - HTML version of this page: https://verifymcp.io/servers/gabrielallit1-salt19-agent-utility-grid/api