Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

Syenite

REMOTE · SYENITE.AI · 2 COMPONENTS · SCANNED AUG 3

DeFi interface for AI agents: swap, bridge, yield, lending. Live at syenite.ai.

+4 this week 67 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 10579 tokens (~229/item across 46 items; 46 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 Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 98% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · syenite.ai

# add to Claude Code
claude mcp add --transport http syenite-ai-syenite https://syenite.ai/mcp
# ~/.codex/config.toml
[mcp_servers.syenite-ai-syenite]
url = "https://syenite.ai/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "syenite-ai-syenite": {
      "type": "remote",
      "url": "https://syenite.ai/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add syenite-ai-syenite --url https://syenite.ai/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  syenite-ai-syenite:
    url: "https://syenite.ai/mcp"
// mcp.json
{
  "mcpServers": {
    "syenite-ai-syenite": {
      "type": "http",
      "url": "https://syenite.ai/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 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
  • 29 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 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 Jul 26 63

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://syenite.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=syenite.ai CN=WE1,O=Google Trust Services,C=US 12 Jul 2026 10 Oct 2026 ECDSA 256 ECDSA-SHA256 8d2299d13d1d6ce131afd045f47a0d1
SANs: syenite.ai
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
DNSSEC insecure

Validation of syenite.ai. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 3799 8 Verified
syenite.ai. 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
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://syenite.ai/mcp Verified 200
http (plaintext) http://syenite.ai/mcp HTTPS enforced 301 https://syenite.ai/mcp
MCP tools — 46 exposed · ~10,579 tokens

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.

Tool Tokens
token.price ~223

Returns the current USD price for one or more tokens by reading Chainlink on-chain price feed contracts directly — the same oracles that Aave, Morpho, Spark, and Compound use to trigger liquidations. Use this for portfolio valuation, P&L calculation, health-factor estimation, and policy enforcement where prices must match what lending protocols see. Pass symbol for a single token or symbols (array, max 20) for a batch lookup; results are cached for 60 seconds. Supported tokens: wBTC, tBTC, cbBTC, WETH, wstETH, rETH, cbETH, weETH, USDC, USDT, DAI, GHO, sDAI. Returns priceUSD and the feed contract address per token; unsupported symbols return an error entry without aborting the batch.

NameTypeReqDescription
symbolstringToken symbol (e.g. wBTC, WETH, USDC). Ignored when symbols is provided.
symbolsarrayBatch: array of token symbols to price in one call (up to 20)
NameTypeReqDescription
errorsarrayPresent when some symbols failed to resolve
pricesarrayyes
sourcestringyes
supportedTokensarrayyesAll token symbols with Chainlink feeds
timestampstringyes

No examples provided.

tx.guard ~210

Evaluates a proposed transaction against a caller-supplied set of risk rules before signing, returning a per-rule pass/fail/skip breakdown and an overall approved verdict. Rules are caller-defined — Syenite does not impose or modify them. Supported rules: maxValueNative (cap native token value), allowedContracts (allowlist of target addresses), blockedContracts (denylist), allowedFunctions (function selector filter), requireVerifiedContract (flag if contract is unverified — requires prior tx.verify call), requireAllowlisted (flag if contract is not in Syenite's curated protocol registry), and maxGasLimit. Pass transaction (to, data, value, gasLimit, chainId) and rules (any subset of the above); at least one rule is required. Use as a programmable safety gate before any autonomous on-chain action. Does not submit or sign the transaction.

NameTypeReqDescription
chainstringChain name (defaults to ethereum)
rulesobjectyes
transactionobjectyes
NameTypeReqDescription
approvedbooleanyes
chainstringyes
checksarrayyes
failedCountnumberyes
notestringyes
passedCountnumberyes
skippedCountnumberyes
summarystringyes
timestampstringyes

No examples provided.

tx.receipt ~199

Fetches and decodes an on-chain transaction receipt from any supported EVM chain, returning confirmation status (confirmed or reverted), gas used and effective gas price, cost in both native token and USD, block number, all contracts interacted with, decoded event logs (Transfer, Approval, Swap, Aave Supply/Borrow/Repay, and others), and a direct block explorer URL. Use after submitting any transaction — swap, supply, borrow, repay, bridge, or approval — to confirm execution and close the strategy loop. Requires txHash and optionally chain (ethereum, arbitrum, base, or bsc; defaults to ethereum). Throws if the transaction is not found, which may indicate it is still pending or was submitted to a different chain. Does not modify state.

NameTypeReqDescription
chainstringChain: ethereum, arbitrum, base, bsc (or chain ID)
txHashstringyesTransaction hash to look up
NameTypeReqDescription
blockNumbernumberyes
chainstringyes
contractsInteractedarrayyes
explorerUrlstringyes
fromstringyes
gasobjectyes
logsobjectyes
nonceyes
notestringyes
statusstringyes
successbooleanyes
timestampstringyes
tostringyes
tokenTransfersarrayERC-20 Transfer events decoded from logs
txHashstringyes
valuestringyes

No examples provided.

tx.simulate ~186

Simulates an unsigned EVM transaction against live chain state using eth_call and eth_estimateGas, returning whether the call would succeed or revert (with revert reason), estimated gas units, approximate gas cost in USD, and native token balance changes from the transaction value. Use this to independently verify what a transaction will do before signing — particularly useful when the transaction was constructed by a third party. Requires transaction.to, transaction.from, transaction.data, and optionally transaction.value and transaction.chainId; pass chain or chainId to target a specific network (ethereum, arbitrum, base, bsc supported). Does not submit the transaction; ERC-20 balance diffs require trace-level simulation (not available on public RPCs) and are noted but not fully computed.

NameTypeReqDescription
chainstringChain name or ID (defaults to tx chainId or ethereum)
transactionobjectyes
NameTypeReqDescription
balanceChangesarrayyes
chainstringyes
contractsCalledarrayyes
detailstring
gasEstimateUSDstringyes
gasUsednumberyes
notestring
revertReasonPresent when simulation reverts
simulatedAtBlocknumberyes
successbooleanyes
timestampstringyes
verificationstringyesHow the simulation was performed — verifiable by any RPC node

No examples provided.

tx.verify ~251

Cross-references a transaction target address against Etherscan (source code verification), Sourcify (independent verification), and Syenite's curated protocol registry to confirm the contract's identity and surface risk flags before signing. Use this to verify any EVM transaction target — not just Syenite-generated ones — as a mandatory pre-signing check in autonomous agent workflows. Requires to (the contract address, 0x-prefixed) and chain (ethereum, arbitrum, base, or bsc); optionally pass data (transaction calldata) to decode and name the function selector via 4byte.directory. Returns verification status from both sources, protocol identification (name, type, risk rating), function name if decoded, risk flags (unverified_contract, unknown_protocol, proxy_contract, eoa_target), and a human-readable summary. Network calls to Etherscan and Sourcify have 10-second timeouts; failures are noted but do not abort the call.

NameTypeReqDescription
chainstringyesChain name: ethereum, arbitrum, base, bsc
datastringCalldata — if provided, decodes the function being called
tostringyesContract address to verify
NameTypeReqDescription
addressstringyes
chainstringyes
functionCalledyes
isContractbooleanyes
notestringyes
protocolobjectyes
riskFlagCountnumberyes
riskFlagsarrayyes
summarystringyes
timestampstringyes
verificationobjectyes

No examples provided.

wallet.balances ~195

Returns native gas token and major stablecoin balances for any EVM or Solana address across supported chains, reading directly from on-chain RPC with no third-party indexer dependency. Accepts an EVM 0x-address (queries Ethereum, Arbitrum, Base, BNB Chain, and Optimism) or a Solana base58 pubkey (queries native SOL and all non-zero SPL token accounts) — address format is detected automatically. Optionally pass chains to restrict the query to specific chains and reduce latency. Use this before executing swaps, bridges, or lending operations to confirm the wallet holds sufficient funds. Returns balances per chain with raw and human-readable amounts; chains with RPC errors are included with an error marker rather than silently dropped.

NameTypeReqDescription
addressstringyesEVM address to check
chainsarrayChains to query (defaults to all: ethereum, arbitrum, base, bsc)
NameTypeReqDescription
addressstringyes
balancesarrayyes
chainsQueriedarrayyes
hasAnyBalancebooleanyesTrue if any chain has a non-zero balance
notestringyes
timestampstringyes

No examples provided.

yield.assess ~271

Provides a structured risk assessment for a specific DeFi yield opportunity before committing capital — covering smart contract risk, oracle configuration, governance model, liquidity and exit risk, depeg/peg risk, and position sizing relative to TVL. Call this after `yield.opportunities` when an agent or user wants to evaluate a specific protocol and product in depth rather than just comparing APYs. Provide `protocol` (e.g. "Aave v3", "Morpho", "Lido") and optionally `product` to disambiguate vaults, `amount` in USD to get position-sizing warnings, and `asset` to narrow matches. Returns a numeric risk score (1–10), per-dimension risk notes, projected annual and monthly yield for the supplied amount, and up to five comparable alternatives ranked by APY; does not execute any transaction.

NameTypeReqDescription
amountnumberAmount in USD to deposit (optional, enables position sizing analysis)
assetstringAsset context for finding alternatives
productstringSpecific product name (optional, helps match the right source)
protocolstringyesProtocol to assess: "Aave", "Lido", "Morpho", "Ethena", "Yearn", "Maker", "Rocket Pool", "Coinbase"
NameTypeReqDescription
alternativesarrayyes
projectedReturnobjectPresent when an amount was provided
queryobjectyes
riskAssessmentobjectyes
sourceobjectyes
timestampstringyes

No examples provided.

yield.opportunities ~405

Aggregates and ranks live DeFi yield opportunities for any asset across lending supply (Aave, Morpho Blue, Spark), liquid staking (Lido, Rocket Pool, Coinbase), savings rates (Maker DSR/sDAI), curated vaults (MetaMorpho, Yearn), fixed-yield Pendle PTs, and basis capture (Ethena sUSDe) on EVM chains, plus Kamino, MarginFi, Jito, Marinade, and Drift on Solana. Call this to discover where to deploy capital before deciding on a protocol; follow up with `yield.assess` to evaluate the risk of a specific opportunity. Pass `asset` (e.g. "USDC", "ETH", "stables") and `chains` (["ethereum"], ["solana"], or both) to scope results; optionally filter by `riskTolerance` ("low", "medium", "high") or `tags` (["fixed-yield"] for Pendle PTs, ["yt"] to surface Pendle YT markets which are hidden by default). Returns opportunities sorted by APY with risk level, TVL, lockup period, APY type (variable/fixed/estimated), and category counts; does not execute any transaction.

NameTypeReqDescription
assetstringAsset to find yield for: "ETH", "USDC", "DAI", "WETH", "USDe", "stables", or "all"
categorystringYield category filter: "lending-supply", "liquid-staking", "vault", "savings-rate", "basis-capture", or "all"
riskTolerancestringMaximum risk level to show: "low", "medium", or "high" (default, shows all)
tagsarrayTag filters: ["fixed-yield"] isolates Pendle PT; ["yt","leveraged-variable"] surfaces Pendle YT (hidden by default)
NameTypeReqDescription
notestringyes
opportunitiesarrayyes
queryobjectyes
summaryobjectyes
timestampstringyes

No examples provided.