Skip to main content
Glama
AshutoshVatsg

ProofYield MCP

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tasks
{
  "list": {},
  "cancel": {},
  "requests": {
    "tools": {
      "call": {}
    }
  }
}
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "subscribe": true,
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
system_getStatusA

Open the ProofYield treasury dashboard and report public configuration. The connected MCP host LLM is the reasoning brain; deterministic ProofYield code authorizes every financial action.

portfolio_getSnapshotA

Read live native and configured test-USDC balances for a validated wallet on supported testnets. Returns per-chain failures without fabricating balances.

opportunities_scanB

Query only configured allowlisted adapters for test-USDC opportunities. Live Aave rates are read on-chain; controlled vault rates are explicitly labeled simulated; DO_NOTHING is always included.

strategy_createPlanA

Validate a server-produced wallet snapshot and opportunity set, apply deterministic hard gates before ranking, include the liquid baseline, and create a short-lived typed plan. Caller-provided addresses never become trusted execution targets.

plan_simulateB

Revalidate a stored plan and trusted adapter against live chain state. If allowance is insufficient, safely simulate and return only an exact approval transaction; otherwise simulate the protocol action and expected postconditions.

execution_prepareA

Return only the exact unsigned transaction produced by the latest non-expired simulation. The server does not sign or submit it and never accepts caller-provided targets or calldata.

execution_verifyB

Read the live transaction and receipt, prove that sender, target, calldata, value, chain, and postconditions match the prepared plan, and never report success without on-chain evidence.

receipt_getA

Retrieve the complete validated Decision Receipt by receipt ID or plan hash. Receipts persist across restarts only when the optional local hackathon store is configured.

monitor_checkA

Compare a stored executed/planned decision with a fresh validated opportunity scan. It can recommend a new proposal but never moves funds automatically.

Prompts

Interactive templates invoked by user choice

NameDescription
proofyield_treasury_helpSafely research and plan a testnet USDC yield allocation using ProofYield’s deterministic policy and verification workflow.

Resources

Contextual data attached and managed by the client

NameDescription
ProofYield capabilities and safety contractSupported chains, configured adapters, MCP workflow, trust boundary, and testnet-only safety guarantees.
Health ChecksCurrent health status of all registered health checks
Proofyield DashboardUI component for Proofyield Dashboard
Widget ExamplesProvides metadata and examples for all registered UI widgets

TDQS

A4/5.0

Scored across 9 tools

Disambiguation5/5

Each tool targets a distinct financial action: plan creation, system status, receipt retrieval, portfolio snapshot, opportunity scanning, plan simulation, unsigned transaction preparation, execution verification, and post-execution monitoring. No two tools overlap in purpose.

Naming Consistency5/5

All tools follow a consistent noun_verb pattern (e.g., strategy_createPlan, portfolio_getSnapshot, execution_prepare). The verb portion is uniformly a verb or verb phrase, and the noun prefix clearly identifies the domain area.

Tool Count5/5

With 9 tools, the server covers the entire lifecycle of a yield strategy—from opportunity scanning and planning to simulation, preparation, verification, and monitoring—without unnecessary redundancy.

Completeness5/5

The tool set provides a complete workflow for testnet yield management: scanning opportunities, creating plans, simulating, preparing unsigned transactions, verifying on-chain execution, and monitoring outcomes. No obvious gaps exist for the intended domain.

Maintenance

ActivityStale
ResponsivenessNo issues