Finance Toolkit
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
제작자가 쓴 설명(영어 원문)
Spectra Finance MCP server: yield discovery, PT/YT, looping, Morpho, 10 chains
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"spectra": {
"command": "npx",
"args": [
"-y",
"spectra-mcp-server"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add spectra -- npx -y spectra-mcp-server프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"spectra": {
"command": "npx",
"args": [
"-y",
"spectra-mcp-server"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"spectra": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"spectra-mcp-server"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 Finanzgoblin 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.0.0)은 9개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Finance Toolkit, SolidInvoice, Korea Tax Calculator
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
500+ transparent financial methods calculated from raw statements, not third-party endpoints.
Create and send invoices and quotes, manage clients, and track payments in SolidInvoice.
Korean tax calculation and tax-audit judgment MCP: 96 tools with statutory citations.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Multi-protocol yield intelligence for AI agents — covering Spectra Finance, Pendle, and Morpho via the Model Context Protocol.
55 tools · 3 protocols · 10+ chains · read-only · open emergence architecture · calibration intelligence · on-chain Curve quoting · Pendle logit AMM modeling · ERC-4626 health checks · yield curve term structure · historical eth_getLogs · full Pendle protocol parity (15 tools) · cross-protocol position map · cross-protocol Spectra↔Pendle comparison · veSPECTRA + vePENDLE governance · Pendle historical time-series · Morpho supply-side visibility with supplier cascade modeling · Morpho user positions & historical rates · Merkl campaign APR + expiry integration · entry path awareness · prescriptive observation boundaries · curator risk monitoring · withdrawal stress testing · rollover planning · multi-vault portfolio aggregation · pool expiry monitoring · zero web3 library dependencies
Any AI agent (Claude, GPT, open-source) that supports MCP can query Spectra, Pendle, and Morpho in a unified interface to:
get_dy() for exact output, falling back to math estimateseth_getLogs when API data has aged out — with dynamic RPC URL support for any chainmv_get_protocol_context (PT/YT identity, Router batching, deposit paths, glossary, fees & costs, workflow routing, externalPositions registry)The agent doesn't need to understand PT/YT mechanics -- it just calls spectra_scan_opportunities or pendle_scan_opportunities with its capital size and gets ranked, actionable data. For cross-protocol comparison, mv_scan_curator_opportunities ranks both protocols together. If it needs to understand *why* something works that way, it calls mv_get_protocol_context.
The server is designed so that AI agents can discover novel strategies without being taught specific strategies. Instead of hard-coding strategy identification logic, the system teaches protocol mechanics at three layers — and lets the agent compose building blocks into its own analysis.
Layer 1: Protocol Context (mv_get_protocol_context tool + resources)
→ Teaches the "physics" of the protocol: PT/YT identity, Router batching, minting → Available as a callable tool (on-demand) and as MCP resources → Static knowledge — what CAN happen, not what IS happening
Layer 2: Tool Descriptions (every tool's description string) → Teaches domain-specific mechanics relevant to that tool's data → Cross-reference nudges: "use spectra_get_portfolio to check actual holdings" → Uses "could be" language, not "is" — preserves ambiguity where it exists → Calls out hidden mechanics that could mislead (e.g., AMM_ADD_LIQUIDITY can mint YT)
Layer 3: Structured Output Hints (computed at runtime in tool output) → Position Shape analysis in portfolio: balance ratios (e.g., "YT/PT 4:1") → Portfolio Signals: concentration, maturity alerts, strategy shape across positions → Volume Signals: volume/liquidity ratio, buy/sell skew, trend detection → Morpho Market Hints: capacity warnings, utilization alerts, spread analysis, reward incentives → Morpho Supply-Side Analysis: supplier identification (vault/EOA/looper), concentration metrics, supply gap warnings — surfaces where lending liquidity comes from and whether it's sufficient → Competing Interpretation Branches (A/B/C) in activity analysis per-address: multiple explanations for the same observable pattern, presented with equal weight. The agent must bring external evidence to collapse branches — the tension IS the info. → Statistical confidence boundaries: small-N cycle repetitions (≤5) flagged as insufficient for extrapolation, preventing false pattern-matching → Flow Accounting with competing hypotheses: YT-only, PT-only, fully exited positions each get multiple explanations that predict different future behavior → Address isolation mode: cycle detection, flow accounting, contract/EOA detection, pool impact warnings, gas estimates, pool context → Capital-aware warnings: short maturity, low liquidity, negative effective APY → Yield Dimensions in scan output: fixed, variable, LP, looping side-by-side → Strategy Tension: competing PT looping vs YT accumulation on same pool → On-chain quote source indicators: "(on-chain Curve get_dy)" vs "(estimated)" → Yield composition: IBT APR breakdown (organic base vs external incentives) in scans and quotes → Incentive sustainability: flags when >50% of IBT APR or LP APY comes from incentives, shows "organic only" APY so agents can assess yield durability without incentive assumptions → Pool reserves: IBT/PT amounts with ratio for AMM imbalance analysis → Merkl campaign APR: external incentive programs (e.g., KAT rewards) shown per-pool/market with double-counting avoidance (skips campaigns whose reward tokens are already displayed) → Merkl campaign eligibility: action type (POOL/HOLD) always shown, with explicit "[LP only — not for YT/PT holders]" flag on POOL campaigns to prevent misattribution → Protocol YT fees: Spectra 3% and Pendle 5% shown in every pool/market detail output so agents apply them to yield calculations without needing external lookups → Points multipliers: external programs (Drops, InfiniFi, Firelight) with amounts → "Could be" / "at current rates" language: preserves ambiguity in ranked output → Makes key signals SALIENT without prescribing interpretation
Layer 4: Observation Coverage (quantifies blind spots in tool output) → Value coverage: what % of an address's position is explained by observable activity. Low coverage means most behavior is invisible (direct mints, transfers, cross-chain). → Temporal coverage: active days vs dark periods with no observable events. Longest gap duration surfaced so the agent can reason about invisible activity. → Data source coverage: which of 5 available sources were consulted vs not. Explicitly lists what is invisible to the current analysis. → Activity diversity: single-type activity flagged as highest-ambiguity pattern. → Boundary marker: "Position sizing should assume this analysis is incomplete, not comprehensive." — a structural admission of domain-of-validity limits. → Coverage metrics bound ALL interpretations above them. High-confidence strategy assessment + low observation coverage = false confidence. The coverage section forces the agent to size its conviction to what it actually observed.
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요