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.

Registrai Arc data

REMOTE · BUILDER.REGISTRAI.CC

Read-only hourly data on stablecoin apps on Arc: payments, volume, indices, verified builders.

68 Trust /100

Last scanned (10 hours ago)

Scores higher than 58% of remote servers

Reachable. Last reached 18 Oct 2026.

Category Crypto and Web3

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 Security74
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1350 tokens (~103/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 45% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 18 Oct 26 +1
    • Tool “arc_app” rewrote its description, which is the text the model reads security
    • Tool “arc_app_history” rewrote its description, which is the text the model reads security
    • Tool “arc_apps” rewrote its description, which is the text the model reads security
    • Tool “arc_index_history” rewrote its description, which is the text the model reads security
    • Tool “arc_indices” rewrote its description, which is the text the model reads security
    • Tool “arc_new_apps” rewrote its description, which is the text the model reads security
    • Tool “arc_verified” rewrote its description, which is the text the model reads security
    • Tool “arc_app” changed its title: Arc app: detail cosmetic
    • Tool “arc_app_history” changed its title: Arc app: hourly history cosmetic
    • Tool “arc_app_history_deep” changed its title: Arc app: full history cosmetic
    • Tool “arc_apps” changed its title: Arc stablecoin apps cosmetic
    • Tool “arc_contract” changed its title: Arc contract facts cosmetic
    • Tool “arc_events” changed its title: Arc watch-feed events cosmetic
    • Tool “arc_index_history” changed its title: Arc index: hourly history cosmetic
    • Tool “arc_index_history_deep” changed its title: Arc index: full history cosmetic
    • Tool “arc_indices” changed its title: Arc indices: latest cosmetic
    • Tool “arc_members_day” changed its title: Arc apps: one day cosmetic
    • Tool “arc_new_apps” changed its title: Arc apps: newly seen cosmetic
    • Tool “arc_project_scope” changed its title: Arc project contracts cosmetic
    • Tool “arc_verified” changed its title: Arc builders: verified cosmetic
  • 17 Oct 26 0
    • Schema quality: 75 → 97 ▼ functional
    • Tool coverage: 73% → 45% ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • New tool “arc_app_history_deep” functional
    • New tool “arc_contract” functional
    • New tool “arc_events” functional
    • New tool “arc_index_history_deep” functional
    • New tool “arc_members_day” functional
    • New tool “arc_project_scope” functional
  • 16 Oct 26 67

    First indexed and scored.

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 18 Oct 2026 · Probed https://builder.registrai.cc/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=builder.registrai.cc CN=WE1,O=Google Trust Services,C=US 24 Sept 2026 23 Dec 2026 ECDSA 256 ECDSA-SHA256 ab113e210eb4be8133eac1520262ade
SANs: builder.registrai.cc
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of builder.registrai.cc. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
cc. present 12593 13 Verified
registrai.cc. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://builder.registrai.cc/api/mcp Verified 200
http (plaintext) http://builder.registrai.cc/api/mcp HTTPS enforced 301 https://builder.registrai.cc/api/mcp
MCP tools · 13 exposed · ~1,325 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
arc_app ~62

One Arc app by id (e.g. domain:archery.wtf, integration:uniswap; ids come from arc_apps): last 24 h, contracts count, verified status and the last 7 days of hourly rows.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

arc_app_history ~137

One Arc app's hourly points and activity (payments, paying wallets, new payers, USD) in one index, oldest first.

NameTypeReqDescription
fromstring–First hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.
idstringyes–
indexstringyesabi = builder apps, aii = integrations, aei = both plus the Arc base layer
tostring–Last hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.

No output schema declared.

No examples provided.

arc_app_history_deep ~167

One app's hourly points and activity for any window. Paid via x402 (USDC on Arc): $0.002 via Circle Gateway or $0.01 standard. Call once to get the payment requirements, then retry with params._meta["x402/payment"].

NameTypeReqDescription
fromstring–First hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.
idstringyes–
indexstringyesabi = builder apps, aii = integrations, aei = both plus the Arc base layer
tostring–Last hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.

No output schema declared.

No examples provided.

arc_apps ~86

Every stablecoin app on Arc in the indices with its last 24 h of stablecoin payments (USDC, EURC) and USD volume, verified status and first-seen hour. Use this when asked which apps use USDC on Arc, or which are most used. Not for token prices, DeFi TVL or chains other than Arc.

NameTypeReqDescription
sortstring––

No output schema declared.

No examples provided.

arc_contract ~77

Facts for one contract on Arc: label, project, recent events and USDC balance. Paid via x402 (USDC on Arc): $0.005 via Circle Gateway or $0.01 standard. Call once to get the payment requirements, then retry with params._meta["x402/payment"].

NameTypeReqDescription
addressstringyes–

No output schema declared.

No examples provided.

arc_events ~156

Watch-feed events on Arc: deploys, upgrades, control changes, pauses and large outflows, labelled to projects. Paid via x402 (USDC on Arc): $0.002 via Circle Gateway or $0.01 standard. Call once to get the payment requirements, then retry with params._meta["x402/payment"].

NameTypeReqDescription
contractstring––
kindstring––
labelledstring––
limitstring––
min_balancestring––
min_project_usdc_24hstring––
projectstring––
since_blockstring––
since_tsstring––
until_blockstring––

No output schema declared.

No examples provided.

arc_index_history ~138

Hourly closes of one Arc index, oldest first (at most 744 hours per call). Use this for charts or changes over a window of up to 31 days.

NameTypeReqDescription
fromstring–First hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.
indexstringyesabi = builder apps, aii = integrations, aei = both plus the Arc base layer
tostring–Last hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.

No output schema declared.

No examples provided.

arc_index_history_deep ~168

Hourly closes of one Arc index for any window (beyond the free 744 h). Paid via x402 (USDC on Arc): $0.002 via Circle Gateway or $0.01 standard. Call once to get the payment requirements, then retry with params._meta["x402/payment"].

NameTypeReqDescription
fromstring–First hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.
indexstringyesabi = builder apps, aii = integrations, aei = both plus the Arc base layer
tostring–Last hour (inclusive). An ISO hour close, e.g. 2026-10-14T19:00:00Z.

No output schema declared.

No examples provided.

arc_indices ~53

Latest hourly close of the Arc Builders, Integrations and Ecosystem indices (ABI, AII, AEI), their 24 h change base and decay parameters. Use this when asked how Arc app activity is trending overall.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

arc_members_day ~85

Every member's hourly rows and the ABI, AII and AEI closes for one UTC day. Paid via x402 (USDC on Arc): $0.03 via Circle Gateway or $0.05 standard. Call once to get the payment requirements, then retry with params._meta["x402/payment"].

NameTypeReqDescription
datestringyesYYYY-MM-DD (UTC).

No output schema declared.

No examples provided.

arc_new_apps ~93

Arc apps first seen in an index after a given hour. Use this when asked what is new on Arc.

NameTypeReqDescription
indexstringyesabi = builder apps, aii = integrations, aei = both plus the Arc base layer
sincestringyesMembers first seen after this hour. An ISO hour close, e.g. 2026-10-14T19:00:00Z.

No output schema declared.

No examples provided.

arc_project_scope ~81

Every contract attributed to one project. Paid via x402 (USDC on Arc): $0.01 via Circle Gateway or $0.02 standard. Call once to get the payment requirements, then retry with params._meta["x402/payment"].

NameTypeReqDescription
limitstring––
offsetstring––
sourcestringyes–

No output schema declared.

No examples provided.

arc_verified ~22

Arc projects whose builder proof validates against the Arc mainnet builder registry.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Registrai Arc data MCP server?

Registrai Arc data is a hosted endpoint at https://builder.registrai.cc/api/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 · builder.registrai.cc

# add to Claude Code
claude mcp add --transport http cc-registrai-arc-data 'https://builder.registrai.cc/api/mcp'
Common questions

What is the Registrai Arc data MCP server?

Registrai Arc data is an MCP server listed in the public MCP registry as cc.registrai/arc-data. Read-only hourly data on stablecoin apps on Arc: payments, volume, indices, verified builders. This page covers its hosted endpoint (https://builder.registrai.cc/api/mcp).

Is the Registrai Arc data MCP server safe to use?

Registrai Arc data scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Registrai Arc data MCP server expose?

Registrai Arc data exposes 13 tools: arc_indices, arc_index_history, arc_apps, arc_app, arc_app_history, and 8 more. Their descriptions and schemas cost roughly 1,325 tokens of context every time the server is loaded.

Does the Registrai Arc data MCP server require authentication?

No. We connected to Registrai Arc data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Registrai Arc data MCP server still maintained?

Registrai Arc data is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.