Baton (augmnt-sh) MCP Server

@augmnt-sh/baton npm v0.1.7

Published by @augmnt-sh — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/src/cli/index.js)MTC-SRC-002

In the server's implementation (`dist/src/cli/index.js:47`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawn } = await import('child_process'); // Resolve absolute path to mcp-server.js using import.meta.url

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/src/cli/index.js

high Shell/command execution in server code (src/cli/index.ts)MTC-SRC-002

In the server's implementation (`src/cli/index.ts:63`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawn } = await import('child_process') // Resolve absolute path to mcp-server.js using import.meta.url //

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/cli/index.ts

Tools 120

Each tool and what it can reach — statically extracted from the published source.

  • tempo_getAllowancereads sensitive data
  • tempo_getTokenRolesreads sensitive data
  • tempo_applySlippageno sensitive capability
  • tempo_approveno sensitive capability
  • tempo_authorizeAccessKeyno sensitive capability
  • tempo_authorizeFullAccessKeyno sensitive capability
  • tempo_authorizeTransferOnlyKeyno sensitive capability
  • tempo_batchTransferno sensitive capability
  • tempo_burnno sensitive capability
  • tempo_burnFeeLiquidityno sensitive capability
Show 110 more tools ↓
  • tempo_calculateSwapWithSlippageno sensitive capability
  • tempo_cancelOrderno sensitive capability
  • tempo_canITransferno sensitive capability
  • tempo_canTransferno sensitive capability
  • tempo_checksumAddressno sensitive capability
  • tempo_claimRewardsno sensitive capability
  • tempo_claimRewardsMultino sensitive capability
  • tempo_createPolicyno sensitive capability
  • tempo_createTimeLockPolicyno sensitive capability
  • tempo_createTransferLimitPolicyno sensitive capability
  • tempo_deriveAddressno sensitive capability
  • tempo_deriveFromMnemonicno sensitive capability
  • tempo_distributeRewardno sensitive capability
  • tempo_doIHaveClaimableRewardsno sensitive capability
  • tempo_encodeFunctionDatano sensitive capability
  • tempo_encodeMemono sensitive capability
  • tempo_estimateContractGasno sensitive capability
  • tempo_estimateFeeno sensitive capability
  • tempo_formatAmountno sensitive capability
  • tempo_fundAddressno sensitive capability
  • tempo_fundMeno sensitive capability
  • tempo_generateWalletno sensitive capability
  • tempo_getAccessKeyno sensitive capability
  • tempo_getAccessKeysno sensitive capability
  • tempo_getAccessKeysWithInfono sensitive capability
  • tempo_getAccountInfono sensitive capability
  • tempo_getAllFeeTokensInfono sensitive capability
  • tempo_getBalanceno sensitive capability
  • tempo_getBalancesno sensitive capability
  • tempo_getBlockno sensitive capability
  • tempo_getBlockNumberno sensitive capability
  • tempo_getChainInfono sensitive capability
  • tempo_getClaimableRewardsno sensitive capability
  • tempo_getClaimableRewardsMultino sensitive capability
  • tempo_getContractAddressesno sensitive capability
  • tempo_getContractCodeno sensitive capability
  • tempo_getFeeLiquidityno sensitive capability
  • tempo_getFeeRateno sensitive capability
  • tempo_getFeeTokenno sensitive capability
  • tempo_getFeeTokenInfono sensitive capability
  • tempo_getGasPriceno sensitive capability
  • tempo_getIncomingTransfersno sensitive capability
  • tempo_getKnownTokensno sensitive capability
  • tempo_getLiquidityShareno sensitive capability
  • tempo_getLogsno sensitive capability
  • tempo_getMyAccessKeyno sensitive capability
  • tempo_getMyAccessKeysno sensitive capability
  • tempo_getMyAccessKeysWithInfono sensitive capability
  • tempo_getMyAccountInfono sensitive capability
  • tempo_getMyAddressno sensitive capability
  • tempo_getMyAllowanceno sensitive capability
  • tempo_getMyBalanceno sensitive capability
  • tempo_getMyBalancesno sensitive capability
  • tempo_getMyClaimableRewardsno sensitive capability
  • tempo_getMyClaimableRewardsMultino sensitive capability
  • tempo_getMyFeeLiquidityno sensitive capability
  • tempo_getMyFeeTokenno sensitive capability
  • tempo_getMyIncomingTransfersno sensitive capability
  • tempo_getMyLiquidityShareno sensitive capability
  • tempo_getMyNonceno sensitive capability
  • tempo_getMyNonZeroBalancesno sensitive capability
  • tempo_getMyOutgoingTransfersno sensitive capability
  • tempo_getMyTokenRolesno sensitive capability
  • tempo_getMyTransferHistoryno sensitive capability
  • tempo_getNonceno sensitive capability
  • tempo_getNonZeroBalancesno sensitive capability
  • tempo_getOrderno sensitive capability
  • tempo_getOutgoingTransfersno sensitive capability
  • tempo_getPolicyno sensitive capability
  • tempo_getPriceno sensitive capability
  • tempo_getStorageAtno sensitive capability
  • tempo_getSupportedFeeTokensno sensitive capability
  • tempo_getSwapQuoteno sensitive capability
  • tempo_getTickno sensitive capability
  • tempo_getTokenBalancesno sensitive capability
  • tempo_getTokenMetadatano sensitive capability
  • tempo_getTotalFeeLiquidityno sensitive capability
  • tempo_getTransactionno sensitive capability
  • tempo_getTransferHistoryno sensitive capability
  • tempo_getTransferPolicyno sensitive capability
  • tempo_getUserFeeTokenno sensitive capability
  • tempo_grantRoleno sensitive capability
  • tempo_hasClaimableRewardsno sensitive capability
  • tempo_hasPermissionno sensitive capability
  • tempo_hasTransferPolicyno sensitive capability
  • tempo_isContractno sensitive capability
  • tempo_isSupportedFeeTokenno sensitive capability
  • tempo_mintno sensitive capability
  • tempo_mintFeeLiquidityno sensitive capability
  • tempo_parseAmountno sensitive capability
  • tempo_placeFlipno sensitive capability
  • tempo_placeOrderno sensitive capability
  • tempo_priceToTickno sensitive capability
  • tempo_readContractno sensitive capability
  • tempo_removeTransferPolicyno sensitive capability
  • tempo_revokeAccessKeyno sensitive capability
  • tempo_revokeRoleno sensitive capability
  • tempo_setFeeTokenno sensitive capability
  • tempo_setRewardRecipientno sensitive capability
  • tempo_setTransferPolicyno sensitive capability
  • tempo_simulateContractno sensitive capability
  • tempo_swapno sensitive capability
  • tempo_tickToPriceno sensitive capability
  • tempo_transferno sensitive capability
  • tempo_truncateAddressno sensitive capability
  • tempo_validateAddressno sensitive capability
  • tempo_validateMnemonicno sensitive capability
  • tempo_validatePrivateKeyno sensitive capability
  • tempo_withdrawOrderno sensitive capability
  • tempo_writeContractno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.7 latest A 93/100 2 1.9.0 2026-07-23

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/augmnt-sh-baton/badge.svg)](https://mcptrustchecker.com/registry/augmnt-sh-baton)
HTML
<a href="https://mcptrustchecker.com/registry/augmnt-sh-baton"><img src="https://mcptrustchecker.com/registry/augmnt-sh-baton/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/augmnt-sh-baton/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @augmnt-sh/baton --online

Use the free API → How scoring works

Other implementations of Baton 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Developer Tools