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

Forge Treasury

REMOTE · MCP.FORGETREASURY.COM · SCANNED AUG 27

Non-custodial USDC yield vaults on Base mainnet with 9 MCP tools for AI agent treasury.

−76 this week 0 Trust /100

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

Recent critical change

TLS certificate (21 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.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.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools.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.

Install

How do I install the Forge Treasury MCP server?

Forge Treasury is a hosted endpoint at https://mcp.forgetreasury.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 · mcp.forgetreasury.com

# add to Claude Code
claude mcp add --transport http com-forgetreasury-treasury 'https://mcp.forgetreasury.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-forgetreasury-treasury": {
      "url": "https://mcp.forgetreasury.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-forgetreasury-treasury": {
      "type": "http",
      "url": "https://mcp.forgetreasury.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-forgetreasury-treasury]
url = "https://mcp.forgetreasury.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-forgetreasury-treasury": {
      "type": "remote",
      "url": "https://mcp.forgetreasury.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-forgetreasury-treasury --url 'https://mcp.forgetreasury.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-forgetreasury-treasury:
    url: "https://mcp.forgetreasury.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-forgetreasury-treasury": {
      "Transport": "http",
      "Url": "https://mcp.forgetreasury.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-forgetreasury-treasury -t streamable-http -u 'https://mcp.forgetreasury.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-forgetreasury-treasury": {
      "type": "http",
      "url": "https://mcp.forgetreasury.com/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.

  • 27 Aug 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 26 Aug 26 −15
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 24 Aug 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 23 Aug 26 −15

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 21 Aug 26 0
    • TLS certificate: pass → fail critical
    • Score status: scored → failed critical
    • Endpoint reachability: reachable → unreachable security
    • HSTS header: fail → unverified security
    • Stability: 0.83 → unverified security
    • Transport: pass → fail security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 20 Aug 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.

  • 18 Aug 26 +1

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

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 27 Aug 2026 · Probed https://mcp.forgetreasury.com/mcp

TLS invalid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Chain error: expired

Subject Issuer Valid from Valid until Key Signature Serial
CN=forgetreasury.com CN=E7,O=Let's Encrypt,C=US 22 May 2026 20 Aug 2026 ECDSA 256 ECDSA-SHA384 5e1235b470edb4dd3a5b68ffab992d74001
SANs: forgetreasury.com, mcp.forgetreasury.com, www.forgetreasury.com
CN=E7,O=Let's Encrypt,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 Mar 2024 12 Mar 2027 ECDSA 384 SHA256-RSA aa75f1e62b8f0a220966d38bbfd4baa1

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.forgetreasury.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
forgetreasury.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.forgetreasury.com/mcp TLS failed
http (plaintext) http://mcp.forgetreasury.com/mcp HTTPS enforced 301 https://mcp.forgetreasury.com/mcp
MCP tools · 9 exposed · ~826 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. 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 →

Tool Tokens
claim_forge ~102

[Advanced] Build calldata to claim weekly $FORGE rewards. Proof is fetched from forgetreasury.com/rewards when omitted.

NameTypeReqDescription
agentAddressstringyesAgent wallet address
amountstringFORGE amount to claim (raw wei string). Optional if manifest has allocation.
epochstringyesReward epoch number
proofarrayMerkle proof array (bytes32 hex strings). Optional — auto-fetched from manifest.

No output schema declared.

No examples provided.

deposit ~183

Deposit USDC into a Forge Treasury vault on Base. Returns calldata for the agent wallet to sign. The agent must approve USDC to the vault contract first. Mints yield-bearing fUSDC shares. Conservative deposits Core only (single leg). Balanced returns two legs (50% Core / 50% Middle). Aggressive is not live. Gas: Core 4M, Middle 6M+ on mainnet.

NameTypeReqDescription
agentAddressstringyesAgent wallet address that will receive vault shares
amountstringyesUSDC amount to deposit (human-readable, e.g. "1000" for 1000 USDC)
profilestringStrategy id (legacy "profile" name). conservative → Core vault. balanced → Core + Middle legs (50/50). aggressive → STRATEGY_NOT_LIVE. Defaults to "conservative".

No output schema declared.

No examples provided.

get_balance ~42

Get an agent's Forge vault balance: shares held and equivalent USDC value. Read-only, no transaction needed.

NameTypeReqDescription
agentAddressstringyesAgent wallet address

No output schema declared.

No examples provided.

get_current_apy ~183

Get the blended target APY for a Forge profile: base USDC yield + FORGE boost. Returns structured JSON with profile metadata, target allocation by adapter, and a disclaimer. Format: "X% USDC + Y% FORGE (blended target)". APY is a blended target across conservative allocation weights; not a guarantee. Sepolia uses MockYieldAdapter until mainnet adapters are live. Conservative deposits Core only (single leg). Balanced returns two legs (50% Core / 50% Middle). Aggressive is not live. Gas: Core 4M, Middle 6M+ on mainnet.

NameTypeReqDescription
agentAddressstringOptional agent address for personalized boost calculation
profilestringRisk profile. MVP: "conservative" only. balanced/aggressive return PROFILE_NOT_LIVE. Defaults to "conservative".

No output schema declared.

No examples provided.

get_forge_rewards ~41

[Advanced] Get claimable $FORGE reward balance for an agent from the weekly emissions distributor.

NameTypeReqDescription
agentAddressstringyesAgent wallet address

No output schema declared.

No examples provided.

get_vault_stats ~28

Get live Forge vault TVL on Base (conservative profile in MVP). Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_profiles ~48

List Forge vaults (Core/Middle/Infra) and agent strategies (Conservative/Balanced/Aggressive). Mainnet: Core and Middle vaults live; conservative and balanced strategies live.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

simulate_deposit ~123

Project expected returns for a USDC deposit over 30, 90, and 365 days using the blended target APY. Use for agent reasoning before depositing. APY is a blended target across conservative allocation weights; not a guarantee. Sepolia uses MockYieldAdapter until mainnet adapters are live.

NameTypeReqDescription
amountstringyesUSDC amount to simulate (e.g. "10000")
profilestringRisk profile to simulate. MVP: "conservative" only. Defaults to "conservative". balanced/aggressive return PROFILE_NOT_LIVE.

No output schema declared.

No examples provided.

withdraw ~76

Withdraw from the Forge Treasury vault by redeeming shares. Returns calldata for the agent wallet. A 15% performance fee may apply on profits above the high water mark.

NameTypeReqDescription
agentAddressstringyesAgent wallet address (owner of shares)
sharesstringyesVault share amount to redeem (raw uint256 string from get_balance)

No output schema declared.

No examples provided.

Common questions

What is the Forge Treasury MCP server?

Forge Treasury is an MCP server listed in the public MCP registry as com.forgetreasury/treasury. Non-custodial USDC yield vaults on Base mainnet with 9 MCP tools for AI agent treasury. This page covers its hosted endpoint (https://mcp.forgetreasury.com/mcp).

What tools does the Forge Treasury MCP server expose?

Forge Treasury exposes 9 tools: deposit, withdraw, get_balance, get_current_apy, simulate_deposit, and 4 more. Their descriptions and schemas cost roughly 826 tokens of context every time the server is loaded.

Does the Forge Treasury MCP server require authentication?

Its publisher declares no required credentials for Forge Treasury. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Forge Treasury MCP server still maintained?

Forge Treasury has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 20 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.