MACH Base
REMOTE · API.MACH.GALLERY
Investigate Base transactions, check wallet funds and contracts. Read-only MCP. USDC via x402.
Available components
Last scanned (13 hours ago)
Scores higher than 12% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 402. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Oct 26 −63
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 22 Oct 26 0
- Stability: 0.97 → pass security
- 13 Oct 26 0
- Tool “base_eth_call” rewrote its description, which is the text the model reads security
- Tool “base_gas_price” rewrote its description, which is the text the model reads security
- Tool “base_logs” rewrote its description, which is the text the model reads security
- Tool “base_nonce” rewrote its description, which is the text the model reads security
- Tool “base_receipt” rewrote its description, which is the text the model reads security
- Tool “base_total_supply” rewrote its description, which is the text the model reads security
- Tool “base_transaction” rewrote its description, which is the text the model reads security
- Tool “base_allowance” rewrote its description, which is the text the model reads security
- Tool “base_block” rewrote its description, which is the text the model reads security
- Tool “base_block_number” rewrote its description, which is the text the model reads security
- Tool “base_contract_code” rewrote its description, which is the text the model reads security
- Tool “base_contract_info” rewrote its description, which is the text the model reads security
- Tool “base_erc20_balance” rewrote its description, which is the text the model reads security
- Tool “base_erc20_transfers” rewrote its description, which is the text the model reads security
- Tool “base_transaction_context” rewrote its description, which is the text the model reads security
- Tool “base_wallet_balance” rewrote its description, which is the text the model reads security
- Tool “base_wallet_snapshot” rewrote its description, which is the text the model reads security
- Schema quality: 67 → 75 ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- New tool “mach_choose” functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Authorization: unverified → partial ▲ security
- Tool “base_allowance” rewrote its description, which is the text the model reads security
- Tool “base_block” rewrote its description, which is the text the model reads security
- Tool “base_block_number” rewrote its description, which is the text the model reads security
- Tool “base_contract_code” rewrote its description, which is the text the model reads security
- Tool “base_contract_info” rewrote its description, which is the text the model reads security
- Tool “base_erc20_balance” rewrote its description, which is the text the model reads security
- Tool “base_erc20_transfers” rewrote its description, which is the text the model reads security
- Tool “base_eth_call” rewrote its description, which is the text the model reads security
- Tool “base_gas_price” rewrote its description, which is the text the model reads security
- Tool “base_logs” rewrote its description, which is the text the model reads security
- Tool “base_nonce” rewrote its description, which is the text the model reads security
- Tool “base_receipt” rewrote its description, which is the text the model reads security
- Tool “base_total_supply” rewrote its description, which is the text the model reads security
- Tool “base_transaction” rewrote its description, which is the text the model reads security
- Tool “base_wallet_balance” rewrote its description, which is the text the model reads security
- Tool “base_wallet_snapshot” rewrote its description, which is the text the model reads security
- Schema quality: 46 → 68 ▼ functional
- Tool coverage: 0% → 96% ▲ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: fair → excellent functional
- Destructive annotations: 0 → pass functional
- New tool “base_transaction_context” functional
- “base_allowance” reworded the description of “owner” cosmetic
- “base_allowance” reworded the description of “spender” cosmetic
- “base_allowance” reworded the description of “token” cosmetic
- “base_block” reworded the description of “block” cosmetic
- “base_contract_code” reworded the description of “address” cosmetic
- “base_contract_info” reworded the description of “address” cosmetic
- “base_erc20_balance” reworded the description of “token” cosmetic
- “base_erc20_transfers” reworded the description of “from_address” cosmetic
- “base_erc20_transfers” reworded the description of “from_block” cosmetic
- “base_erc20_transfers” reworded the description of “to_address” cosmetic
- “base_erc20_transfers” reworded the description of “to_block” cosmetic
- “base_erc20_transfers” reworded the description of “token” cosmetic
- “base_eth_call” reworded the description of “block” cosmetic
- “base_eth_call” reworded the description of “data” cosmetic
- “base_eth_call” reworded the description of “to” cosmetic
- “base_logs” reworded the description of “address” cosmetic
- “base_logs” reworded the description of “from_block” cosmetic
- “base_logs” reworded the description of “to_block” cosmetic
- “base_logs” reworded the description of “topics” cosmetic
- “base_nonce” reworded the description of “address” cosmetic
- “base_receipt” reworded the description of “tx_hash” cosmetic
- “base_total_supply” reworded the description of “token” cosmetic
- “base_transaction” reworded the description of “tx_hash” cosmetic
- “base_wallet_balance” reworded the description of “address” cosmetic
- “base_wallet_snapshot” reworded the description of “address” cosmetic
- “base_wallet_snapshot” reworded the description of “tokens” cosmetic
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 21 Nov 2026 · Probed https://api.mach.gallery/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.mach.gallery | CN=YR1,O=Let's Encrypt,C=US | 21 Sept 2026 | 20 Dec 2026 | RSA 2048 | SHA256-RSA | 644c9bdebc7ae50ba1f4adef7907025bfbd |
| SANs: api.mach.gallery | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.mach.gallery. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| gallery. | DS published | 58981 | 8 | Verified |
| mach.gallery. | DS published | 3976, 3976 | 15, 15 | Verified |
| api.mach.gallery. | Verified address RRset verified with the apex keys |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 402 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mach.gallery/mcp | HTTP error | 402 | |
| http (plaintext) | http://api.mach.gallery/mcp | HTTPS enforced | 308 | https://api.mach.gallery/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 →
base_allowance ~101
Check a Base token approval before an agent acts: return the ERC-20 allowance for one token, owner and spender. Does not grant approval. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | ERC-20 token owner address on Base mainnet. |
| spender | string | yes | ERC-20 spender address whose allowance is being checked. |
| token | string | yes | ERC-20 or token contract address on Base mainnet. |
No output schema declared.
No examples provided.
base_block ~63
Inspect a Base block by number or tag: retrieve its header and transaction hashes to investigate chain activity. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| block | – | – | Base block selector: block number or tag such as latest, safe, finalized, pending or earliest. |
No output schema declared.
No examples provided.
base_block_number ~44
Check Base chain progress: return the latest mainnet block number for freshness checks and polling. This is not transaction confirmation. Costs $0.005 USDC via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_contract_code ~69
Tell a Base contract address from an externally owned account: return whether code is deployed and its bytecode size. Not a security audit. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 20-byte 0x-prefixed EVM address on Base mainnet. |
No output schema declared.
No examples provided.
base_contract_info ~59
Identify a Base contract before interacting: inspect bytecode size, available token metadata and common interface signals. Not a security audit. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Smart-contract address on Base mainnet. |
No output schema declared.
No examples provided.
base_erc20_balance ~76
Check a wallet’s USDC or ERC-20 balance on Base: return raw token units for a specified token contract and wallet address. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | yes | – |
| token | string | yes | 20-byte 0x-prefixed EVM address on Base mainnet. |
No output schema declared.
No examples provided.
base_erc20_transfers ~135
Find recent ERC-20 Transfer events on Base, optionally filtered by sender or recipient wallet. Results cover only the queried block window. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| from_address | string | – | Optional sender wallet to filter ERC-20 transfers. |
| from_block | integer | – | First Base block to include in the transfer query. |
| to_address | string | – | Optional recipient wallet to filter ERC-20 transfers. |
| to_block | integer | – | Last Base block to include in the transfer query. |
| token | string | yes | ERC-20 or token contract address on Base mainnet. |
No output schema declared.
No examples provided.
base_eth_call ~99
Read Base contract state without broadcasting a transaction: run eth_call with supplied calldata and return the raw response. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| block | – | – | Base block selector: block number or tag such as latest, safe, finalized, pending or earliest. |
| data | string | yes | 0x-prefixed ABI calldata for a read-only eth_call. |
| to | string | yes | Smart-contract address on Base mainnet. |
No output schema declared.
No examples provided.
base_gas_price ~44
Check the current Base gas price in wei before estimating transaction fees. The quote alone is not the total transaction cost. Costs $0.005 USDC via x402.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
base_logs ~112
Find Base smart-contract events in a bounded block range: return onchain logs filtered by contract address and optional topics. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Smart-contract address on Base mainnet. |
| from_block | integer | – | First Base block to include in the log query. |
| to_block | integer | – | Last Base block to include in the log query. |
| topics | array | – | Up to four Ethereum log topics; null keeps a topic position as a wildcard. |
No output schema declared.
No examples provided.
base_nonce ~59
Prepare a Base transaction: get a wallet’s current nonce without signing or broadcasting a transaction. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 20-byte 0x-prefixed EVM address on Base mainnet. |
No output schema declared.
No examples provided.
base_receipt ~70
Check whether a Base transaction was mined and succeeded: return receipt status and confirmations. This does not prove the correct payee, token amount or service delivery. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | 32-byte 0x-prefixed Base transaction hash. |
No output schema declared.
No examples provided.
base_total_supply ~62
Check a Base ERC-20 or ERC-721 contract’s reported total supply. Contract data is not independently audited circulation. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | yes | ERC-20 or token contract address on Base mainnet. |
No output schema declared.
No examples provided.
base_transaction ~66
Inspect a Base transaction by hash: retrieve sender, recipient, value, calldata and transaction fields. Use Transaction Context for receipt and confirmation status. Costs $0.008 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | 32-byte 0x-prefixed Base transaction hash. |
No output schema declared.
No examples provided.
base_transaction_context ~76
Investigate a Base payment timeout or failed transaction with transaction, receipt, gas and fee context. Onchain success is not proof that a specific USDC obligation or service delivery was met. Costs $0.008 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| tx_hash | string | yes | 32-byte 0x-prefixed Base transaction hash. |
No output schema declared.
No examples provided.
base_wallet_balance ~69
Check whether a Base wallet has native ETH available for gas: return its balance in wei. Read-only; no wallet access or signing. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 20-byte 0x-prefixed EVM address on Base mainnet. |
No output schema declared.
No examples provided.
base_wallet_snapshot ~84
Check a Base wallet’s funding context in one read: return native ETH and balances for up to ten specified ERC-20 contracts. No signing or custody. Costs $0.005 USDC via x402.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet or account address on Base mainnet. |
| tokens | array | – | Up to ten token contract addresses whose balances should be included. |
No output schema declared.
No examples provided.
mach_choose ~65
Free decision layer: map an agent goal to the narrowest paid MACH Base capability, exact price, expected result fields and exact next request. Returns no live chain data and has no side effects.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | The job or outcome the agent needs from Base mainnet. |
No output schema declared.
No examples provided.
How do I install the MACH Base MCP server?
MACH Base is a hosted endpoint at https://api.mach.gallery/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.mach.gallery
claude mcp add --transport http thealiphant-mach-base 'https://api.mach.gallery/mcp'
What is the MACH Base MCP server?
MACH Base is an MCP server listed in the public MCP registry as io.github.TheAliphant/mach-base. Investigate Base transactions, check wallet funds and contracts. Read-only MCP. USDC via x402. This page covers its hosted endpoint (https://api.mach.gallery/mcp).
Is the MACH Base MCP server safe to use?
MACH Base scores 26 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 MACH Base MCP server expose?
MACH Base exposes 18 tools: mach_choose, base_block_number, base_gas_price, base_wallet_balance, base_erc20_balance, and 13 more. Their descriptions and schemas cost roughly 1,353 tokens of context every time the server is loaded.
Does the MACH Base MCP server require authentication?
Its publisher declares no required credentials for MACH Base. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the MACH Base MCP server still maintained?
MACH Base is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the MACH Base MCP server?
VerifyMCP ran 5 checks on MACH Base, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about MACH Base: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.