SALT19 Agent Utility Grid
REMOTE · API.SALT19.COM · SCANNED SEP 20
MCP/x402 tools with bounded decisions, adaptive pricing, and Proof402 machine-commerce receipts.
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability53
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
- Structured output schemas are declared (52% 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 33 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 34 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
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.
remote · api.salt19.com
claude mcp add --transport http gabrielallit1-salt19-agent-utility-grid 'https://api.salt19.com/mcp'
{
"mcpServers": {
"gabrielallit1-salt19-agent-utility-grid": {
"url": "https://api.salt19.com/mcp"
}
}
} {
"servers": {
"gabrielallit1-salt19-agent-utility-grid": {
"type": "http",
"url": "https://api.salt19.com/mcp"
}
}
} [mcp_servers.gabrielallit1-salt19-agent-utility-grid] url = "https://api.salt19.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gabrielallit1-salt19-agent-utility-grid": {
"type": "remote",
"url": "https://api.salt19.com/mcp",
"enabled": true
}
}
} openclaw mcp add gabrielallit1-salt19-agent-utility-grid --url 'https://api.salt19.com/mcp' --transport streamable-http
mcp_servers:
gabrielallit1-salt19-agent-utility-grid:
url: "https://api.salt19.com/mcp" {
"McpServers": {
"gabrielallit1-salt19-agent-utility-grid": {
"Transport": "http",
"Url": "https://api.salt19.com/mcp"
}
}
} assistant mcp add gabrielallit1-salt19-agent-utility-grid -t streamable-http -u 'https://api.salt19.com/mcp'
{
"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.
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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +1
- 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 security
- 14 Sept 26 +1
- 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 security
- 13 Sept 26 0
- 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 security
- Server version: 0.5.0 → 0.5.1 functional
- 12 Sept 26 +1
- 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 security
- 10 Sept 26 +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.
- 8 Sept 26 +1
- Tool “agent-decision-preflight” rewrote its description, which is the text the model reads security
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 20 Sept 2026 · Probed https://api.salt19.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=salt19.com | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4769346789efac56136400f11c9ac0c8 |
| SANs: salt19.com, api.salt19.com, *.api.salt19.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 insecure
Validation of api.salt19.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| salt19.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.salt19.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.salt19.com/mcp | HTTPS enforced | 301 | https://api.salt19.com/mcp |
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 →
agent-claim-output-verifier Agent Claim Output Verifier ~321
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
agent-code-change-risk-gate Agent Code Change Risk Gate ~317
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "diff" for the agent-code-change-risk-gate tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
agent-decision-preflight Agent Decision Preflight ~298
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "decision_type" for the agent-decision-preflight tool. |
| target | object | yes | Input parameter "target" for the agent-decision-preflight tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
agent-plan-verifier Agent Plan Verifier ~300
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "goal" for the agent-plan-verifier tool. |
| plan | array | yes | Input parameter "plan" for the agent-plan-verifier tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
base-contract-state Base Contract State ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
No output schema declared.
No examples provided.
base-token-allowance Base Token Allowance ~173
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
| spender | string | yes | – |
| token_address | string | yes | – |
No output schema declared.
No examples provided.
base-token-balance Base Token Balance ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
| token_address | string | yes | – |
No output schema declared.
No examples provided.
base-transaction-status Base Transaction Status ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
No output schema declared.
No examples provided.
base-wallet-balance Base Wallet Balance ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
No output schema declared.
No examples provided.
commerce-decision Commerce Decision ~296
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "payment_required" for the commerce-decision tool. |
| policy | object | yes | Input parameter "policy" for the commerce-decision tool. |
| request | object | yes | Input parameter "request" for the commerce-decision tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
commerce-receipt Commerce Receipt ~418
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | – | yes | Input parameter "delivery" for the commerce-receipt tool. |
| expected_delivery | object | – | Input parameter "expected_delivery" for the commerce-receipt tool. |
| payment_payload | object | yes | Input parameter "payment_payload" for the commerce-receipt tool. |
| payment_required | object | yes | Input parameter "payment_required" for the commerce-receipt tool. |
| policy | object | – | Input parameter "policy" for the commerce-receipt tool. |
| request | object | yes | Input parameter "request" for the commerce-receipt tool. |
| settlement | object | yes | Input parameter "settlement" for the commerce-receipt tool. |
| target_salt19_operation_id | string | – | Input parameter "target_salt19_operation_id" for the commerce-receipt tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
commerce-verify Commerce Verify ~406
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | – | yes | Input parameter "delivery" for the commerce-verify tool. |
| expected_delivery | object | – | Input parameter "expected_delivery" for the commerce-verify tool. |
| payment_payload | object | yes | Input parameter "payment_payload" for the commerce-verify tool. |
| payment_required | object | yes | Input parameter "payment_required" for the commerce-verify tool. |
| policy | object | – | Input parameter "policy" for the commerce-verify tool. |
| request | object | yes | Input parameter "request" for the commerce-verify tool. |
| settlement | object | yes | Input parameter "settlement" for the commerce-verify tool. |
| target_salt19_operation_id | string | – | Input parameter "target_salt19_operation_id" for the commerce-verify tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
dependency-go-no-go Dependency Go No Go ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "package" for the dependency-go-no-go tool. |
| version | string | – | Input parameter "version" for the dependency-go-no-go tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
dependency-upgrade-go-no-go Dependency Upgrade Go No Go ~374
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | 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 | yes | 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 | yes | Input parameter "target_version" for the dependency-upgrade-go-no-go tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
find-salt19-tool Find the Best SALT19 Tool ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_usd | number | – | Optional hard maximum price for the eventual paid tool call. |
| need | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| alternatives | array | yes | – |
| next_action | object | yes | – |
| selected | object|null | yes | – |
| selection_id | string | yes | – |
No examples provided.
github-repo-facts Github Repo Facts ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
No output schema declared.
No examples provided.
github-repo-preflight Github Repo Preflight ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "repo" for the github-repo-preflight tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
model-memory-fit Model Memory Fit ~328
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "parameter_count_b" for the model-memory-fit tool. |
| quantization_bits | number | yes | 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 | yes | Input parameter "vram_gb" for the model-memory-fit tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
npm-package-facts Npm Package Facts ~157
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
| version | string | – | – |
No output schema declared.
No examples provided.
npm-package-intel Npm Package Intel ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "package" for the npm-package-intel tool. |
| version | string | – | Input parameter "version" for the npm-package-intel tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
nws-active-alerts Nws Active Alerts ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
repo-adoption-go-no-go Repo Adoption Go No Go ~271
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "repo" for the repo-adoption-go-no-go tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
report-payment-capability Report x402 Payment Capability ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| autonomous_spend_allowed | string | – | – |
| decline_reason | string | yes | – |
| 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 | – | – |
No output schema declared.
No examples provided.
report-x402-authorization-progress Report x402 Authorization Progress ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_timestamp | string | – | – |
| error_code | string | – | – |
| handoff_id | string | yes | – |
| sdk | string | – | – |
| signer_available | string | – | – |
| signer_kind | string | – | – |
| stage | string | yes | – |
No output schema declared.
No examples provided.
salt19-pricing SALT19 Live Pricing ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_price_usd | number | – | – |
| tier | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| products | array | yes | – |
| start_here | object | yes | – |
No examples provided.
sec-company-facts Sec Company Facts ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
| concepts | array | – | – |
No output schema declared.
No examples provided.
sec-recent-filings Sec Recent Filings ~159
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
url-http-preflight Url Http Preflight ~320
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | Input parameter "url" for the url-http-preflight tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
url-to-llm-markdown Url To Llm Markdown ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | yes | – |
No output schema declared.
No examples provided.
usgs-earthquakes Usgs Earthquakes ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| _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 | – | – |
No output schema declared.
No examples provided.
verify-decision-receipt Verify SALT19 Decision Receipt ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | SALT19 decision receipt UUID |
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No examples provided.
x402-authorization-handoff SALT19 x402 Authorization Handoff ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | yes | 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 | yes | – |
| session_id | string | – | – |
No output schema declared.
No examples provided.
x402-payment-preflight SALT19 x402 Payment Preflight ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| autonomous_spend_allowed | boolean | – | – |
| max_price_usd | number | – | – |
| product | string | yes | – |
| supported_assets | array | – | – |
| supported_networks | array | – | – |
| supports_x402 | boolean | – | – |
| wallet_address | string | – | Optional public EVM address only; never provide a private key. |
No output schema declared.
No examples provided.
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.