
Agiscorecard Web3 Route
io.github.f-tigerv1.7.0更新於 Oct 10, 2026
Plan LLM fallback sequences from supplied cost, quality and latency assumptions; no live execution.
概覽
讓助理依提供的成本、品質與延遲假設規劃有界的 LLM 備援順序,不進行即時執行。
- 功能
- 這個遠端 MCP 端點提供十個確定性計算器以及 search 和 fetch。路由計算器 Route Lab 依提供的成本、品質與延遲假設規劃有界備援順序。結果保留既有演算法、精確金額、發行修訂、方法引用、日期與限制,resources/list 會公開方法參考、能力說明與虛構輸入。工具標註為唯讀、非破壞性、冪等且封閉世界。
- 適用情境
- 當你希望助理依你提供的假設比較或規劃模型備援順序,或透過單一端點執行其他確定性計算器時使用。它不用於即時模型呼叫、錢包或鏈上操作、轉帳、訂閱或證明驗證,也不執行任何動作。若只需要一個計算器,每個工具主機也提供各自限定的端點。
- 執行需求
- 遠端 streamable HTTP 端點,不需要安裝套件。README 說明 MCP 端點為 /mcp,僅作用於自己的計算器。未宣告金鑰或身分驗證。GET 與 DELETE 會回傳 405,不提供持續訂閱。嚴格的 Origin 驗證會拒絕未知的瀏覽器來源,而不帶 Origin 的伺服器端用戶端仍受支援。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Agiscorecard Web3 Route,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"mcpServers": {
"agiscorecard-web3-route": {
"type": "http",
"url": "https://route.agiscorecard.com/mcp"
}
}
}README
Web3 Workbench
Ten independent, usable free-beta tools and one hub. Source and generated fixtures are shared; every host serves only its own pages. Existing Agent Delivery Lab remains a separate deployment.
Hub: https://web3.agiscorecard.com/
Development and release
Node.js 22+ and Python 3 with Pillow and DejaVu Sans fonts are required. Browser/offline calculation engines have no npm dependencies; the remote MCP server uses the pinned official SDK.
npm test builds 55 HTML pages, 30 worked scenarios, per-host metadata and share images, and the offline bundle, then runs 71 tests. WEB3_BUILD_REVISION pins the actual checked-out commit. Generated dist/, release module and credential-free generated Wrangler config are not committed.
The path-scoped GitHub workflow validates, checks all hostname ownership, binds the existing database, deploys the Worker, and checks every production host and asset against the build. A collision stops before publication. Existing credentials remain in GitHub Secrets. Branch runs validate only; main may deploy. Do not substitute the trigger SHA for the checkout SHA after the stale-main guard.
Only web3_studio_feedback is created/read/updated. No other database table is modified. Optional feedback is constrained enums; IP is used only as the transient rate-limit key. QA samples are explicitly flagged and excluded from demand. Grouped submission counts never represent verified individuals. TTL cleanup occurs on feedback/stats requests and may be delayed during inactivity.
Product limits
Browser inputs are local. No model provider, wallet, live-chain simulation, transfer, subscription or proof verification is connected. Documentation states each tool's own limits. Protocol records are editorial summaries, not complete schemas or compatibility certification. New algorithms mean reproducible combinations of known methods here, not a novel cryptographic or economic theorem.
Research and falsification conditions: portfolio research. Every tool's catalog includes alternatives, scope, commercial hypothesis and a concrete validation condition. Public downloads are limited to the explicit offline bundle and its license; no repository archive is served.
Experience, discovery and sharing (1.1)
Each tool has three runnable scenarios, per-record-group CSV paste, same-tab result comparison, Markdown reports and print/PDF output. Public share links allow only known scenario IDs; private inputs never appear in generated URLs. Clearing/reloading the tab removes in-memory records and comparisons.
Search titles describe actual tasks. Human-readable methods and examples back the structured WebApplication, FAQ and breadcrumb data. No fabricated ratings, usage statistics or rich-result promises. guide.md, tool.json, input.schema.json, llms.txt and llms-full.txt are navigation/integration aids, not special eligibility requirements for AI search. The schema is structural; the engine enforces its additional constraints.
/publish.html on the hub provides ten share cards and optional branded links. Distributed HTML card links use rel="nofollow". No automatic outreach, paid links or third-party endorsements are claimed.
The existing weekly/manual IndexNow workflow validates the key and the canonical page set on each of the 11 hosts before submitting. It never submits on push. node scripts/indexnow.mjs --check validates without submitting. A 200/202 submission response is not evidence of indexing or ranking.
Release smoke verification uses asset-manifest.generated.json to hash-check the exact assets for each host; generated files are excluded from git. See growth implementation record.
MCP (1.2)
Unified endpoint: https://web3.agiscorecard.com/mcp. Each tool host also exposes /mcp, scoped to its own calculator. Streamable HTTP, no key; official SDK 2.0.0 handles 2026-07-28 per-request negotiation and stateless 2025-era compatibility. GET/DELETE return 405; persistent subscriptions are not offered. The existing AGI Scorecard main-domain MCP remains separate.
The hub exposes ten deterministic calculators plus search and fetch. All results preserve the existing algorithms, exact amounts, release revision, methodology citation, date and limits. resources/list exposes public method references, capabilities and fictional inputs. No arbitrary resource fetching or private report publication is implemented. Annotations declare read-only, non-destructive, idempotent, closed-world tools.
Remote MCP arguments are sent to the server, unlike browser/offline inputs. Application code neither persists them nor logs their contents or sends them to a model/source URL. Hosting and the connecting client's own policies still apply. No D1 writes occur in MCP. A separate 120/minute/IP binding limits calls across the 11 hosts; body size is at most 128 KiB including the protocol envelope. Missing rate-limit binding fails closed. Exact Origin validation rejects unknown browser origins; server-side clients without Origin remain supported.
/for-agents.html is the human setup/citation/privacy guide. /.well-known/mcp.json is explicitly a descriptive metadata file, not a standard auto-install mechanism or official registry listing. MCP availability is not evidence of AI search citations.
Tests use the official 2.0 client pinned to 2026-07-28 and the official 1.30 client for 2025-era compatibility. scripts/mcp-smoke.mjs repeats negotiation, tool discovery, resources, all 30 scenarios, citations and host scoping against the deployed endpoint. CI installs the lockfile, retains the stale-main guard and uses existing Cloudflare credentials. No new scheduled workflow is introduced.
Market context and conversion measurement (1.3)
The hub now serves source-stamped /market.html, /briefs.html, three task guides,
/api/market, /api/briefs and /updates.xml. Price snapshots refresh on request
after five minutes; official metadata after one hour. Stale/unavailable data is
explicit and data older than a day is hidden. These are venue references, not
executable quotes or verified payments. Public source polling does not change
any browser or MCP calculation contract.
Optional, off-by-default fixed-category usage measurement writes only the isolated
web3_studio_events table. /api/growth excludes QA unless ?qa=1; reports count
opt-in events, not people, linked sessions, verified backlinks or revenue. A
separate MEASURE_LIMIT binding caps submissions. /api/stats feedback is separate.
Run node scripts/market-smoke.mjs after deploying and
node scripts/growth-audit.mjs --check for source/discovery/measurement health.
The existing daily fleet-autopilot retains 30 daily diagnostic records.
Research board (1.4)
/market.html now combines eight curated assets, daily history comparisons, source-linked research questions and a local evidence notebook. /api/research is a separate read-only feed; the original four-asset /api/market contract and deterministic MCP tools remain available. status describes snapshot retrieval; every quote has its own freshness status. Changes use daily samples within two hours of the intended interval, never synthetic candles. Missing history does not erase usable current prices.
Watchlist baselines and notes are written to browser storage only on explicit Save, expire after 30 days and have separate Delete actions. They are never uploaded. Export is a user-authored Markdown file, not automatic publication or an AI verdict. Four optional fixed-category events support evaluating the experiment without collecting notes, saved prices or asset selections. scripts/research-smoke.mjs verifies actual source/history connectivity after deployment; the existing daily audit covers this feed too.
來源:sites/web3-studio/README.md,提交 2e748c7
工具
0版本歷史
1- v1.7.0最新Oct 10, 2026
