Agiscorecard Web3 Protocol MCP server
online · 100% uptimeRead dated x402, ERC-8004 and token-interface profiles with official sources and freshness limits.
0 stars
Reviews
Write oneNobody has reviewed Agiscorecard Web3 Protocol yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Agiscorecard Web3 Protocol tools (3)
write = sends, deletes, buys or postsfetchFreeRetrieve a public tool reference by the ID returned from search. Contains methodology, limits, official source links and fictional worked examples; no user records. Cite the returned canonical URL.
read_protocol_profilesFreeProtocol Ledger is a free, dated reference for five payment, agent-identity and token interfaces. Each record preserves its official specification, review date and interpretation limits. Filter the same snapshot in the browser or retrieve it through the JSON API. Five initial profiles; no market prices, exhaustive schema coverage, real-time protocol monitoring or paid endpoint. Retrieve protocol with fetch or read its example resource to obtain exact inputs. Parameters are processed remotely without application persistence.
searchFreeSearch this server’s public AI/Web3 tools and citation pages. English and Chinese names supported. Empty query lists the available worksheets.
Public scan report
scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1558ms20/20
- Tool poisoning3 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Agiscorecard Web3 Protocol compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 91/100
- higher than 85% of 48,255 servers
- Tools
- 3
- the typical server has 7
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 24 ms
- faster than 96% of 30,031 servers
What its tools let an agent do: 3 read
Install Agiscorecard Web3 Protocol in Claude Code, Cursor or VS Code
claude mcp add --transport http agiscorecard-web3-protocol https://protocol.agiscorecard.com/mcp
What the publisher says
From the Agiscorecard Web3 Protocol repository's README, as published. We do not edit it. Read it on GitHub
agi-site — one public monorepo, N sites
Public monorepo for the site fleet (owner decision 2026-08-19). Public repos get free GitHub Actions minutes, which ends the account-wide 2,000 min/month problem that froze every private-repo schedule on 2026-08-18.
Each site keeps its own CLAUDE.md, tooling and conventions inside its directory. Root workflows are path-filtered: a commit only deploys the site it touches. History note: each site was imported as a fresh snapshot; pre-import history lives in the original private repos (f-tiger/agiscorecard, f-tiger/aitools, f-tiger/rearchfuture, f-tiger/sexweb), which are archives now — do not push site content there.
Privacy rule for this PUBLIC repo: no owner personal archive (owner-identity/owner-trajectory), no subscriber addresses, no tokens/keys. See CLAUDE.md.
One practical workflow check
帧选：AI 漫剧与短剧找片 is a free Chinese-language discovery catalogue with dated official sources and clearly labelled viewing destinations. It does not host episodes.
For creators, the video publishing assessment tool compares preparation for six Chinese platforms using local video metadata and self-reported checks. Try the worked examples, or cite its public methodology and structured rules. Files and reports stay in the browser; suggestions are test hypotheses, not viral predictions.
Compare coding assistants on a small CRM workflow: a free local exercise covering duplicate events, retries, credential errors and ambiguous timeouts. Synthetic data only; no account or API key required. For a task that remains stuck, use the linked public workflow-question form with a sanitized example. This is a technical help entry, not a checkout.
Owner TODO (one-time, optional but recommended)
integration to f-tiger/agiscorecard (that repo is archived; a stray push there would roll the site back). Until then: simply never push there.
- Cloudflare dashboard → Workers agiscorecard → disconnect the old git
tds-crawl-log schedules are live. Still open, optional (owner deferred GA4 on 2026-08-19; D1 is the primary channel):
- CLOUDFLAREAPITOKEN_ZONE configured 2026-08-19 — tds-traffic and
GA4SERVICEACCOUNT_JSON (they no-op gracefully until then)
- bpj-growth-loop.yml: GA4PROPERTYIDBPJ, GA4SERVICEACCOUNTJSON
- GA4 steps inside tds-traffic.yml: GA4PROPERTYID_TDS,
RESENDAPIKEY/SUPABASESERVICEKEY (eco heat-alert real sends), MCPREGISTRYPRIVATE_KEY (tds registry proof) Copy the values from the old private repos' Settings → Secrets (names unchanged).
- optional senders: TELEGRAMBOTTOKEN/TELEGRAMCHATID (tds grow notify),
Nothing above is checked by us. What we check is on the safety report.
Agiscorecard Web3 Protocol: common questions
- Is Agiscorecard Web3 Protocol MCP server safe?
- Yes, by our scan: it is graded A (91/100). Read the Agiscorecard Web3 Protocol safety report
- How do I install Agiscorecard Web3 Protocol?
- It runs remotely at protocol.agiscorecard.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Agiscorecard Web3 Protocol need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Agiscorecard Web3 Protocol maintained?
- The last commit was 22 days ago (2026-10-13). The latest release is v1.7.0.
- Is Agiscorecard Web3 Protocol up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Agiscorecard Web3 Protocol compare with other MCP servers?
- safety score 91/100 (higher than 85% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.