Skip to content

Registrai Arc data MCP server

cc.registrai/arc-dataregistrai.ccstreamable-httpv1.0.0Scanned

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

13 tools: 3 do something that can't be undone and 10 change things.

Tools: 0 delete, 3 irreversible, 10 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 3
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Registrai Arc data MCP server can do

The Registrai Arc data MCP server is published by registrai.cc, a domain the MCP Registry verified. It has 13 tools. It can do things that cannot be undone, such as sending, paying or publishing (arc_index_history, arc_app_history and arc_apps_daily) and create or change data (10 tools: arc_indices, arc_apps, arc_app, arc_new_apps and 6 more), but cannot delete data. None of its tools only reads.

3 tools can send data out of your system (arc_index_history, arc_app_history and arc_apps_daily).

The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Can't be undone 3Claude Code: ask
  • arc_app_historyOne Arc app's hourly points and activity (payments, paying wallets, new payers, USD) in one index, oldest first.Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "arc_app_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    One Arc app's hourly points and activity (payments, paying wallets, new payers, USD) in one index, oldest first.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc app: hourly history
  • arc_apps_dailyUSDC received per day by Arc apps and directory projects since mainnet's first day (2026-09-16), counted from every USDC transfer into their contracts, before any index rule (USD, …Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "arc_apps_daily" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    USDC received per day by Arc apps and directory projects since mainnet's first day (2026-09-16), counted from every USDC transfer into their contracts, before any index rule (USD, transfers, distinct payers). One app (up to 31 days) or all apps (up to 7 days). Use this when asked how much USDC an app or exchange on Arc receives, or how a project's flows changed since launch.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc apps: daily USDC
  • arc_index_historyHourly closes of one Arc index, oldest first (at most 744 hours per call).Can send data out1 finding

    Why it is in this group

    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "arc_index_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc index: hourly history
Changes things 10Claude Code: ask
  • arc_address_labelWho an address on Arc mainnet belongs to: the project or app, the address's role and the source of the label (directory entries, stablecoins, Registrai's chain scan, the contracts …1 finding

    Why it is in this group

    • The name "arc_address_label" says "label": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "arc_address_label" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "arc_address_label" says "label": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Who an address on Arc mainnet belongs to: the project or app, the address's role and the source of the label (directory entries, stablecoins, Registrai's chain scan, the contracts the Arc indices count per app). Use this when asked whose contract or address something is on Arc. No label usually means a wallet or an unnamed contract.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc address: label
  • arc_appOne Arc app by id (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc app: detail
  • arc_appsEvery 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Every 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc apps
  • arc_apps_weekApps on Arc ranked by stablecoin payments received in the last 7 days (USD, payments, new paying wallets) and the hour each was first seen in Registrai's index.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Apps on Arc ranked by stablecoin payments received in the last 7 days (USD, payments, new paying wallets) and the hour each was first seen in Registrai's index. Use this when asked which apps on Arc are most used, which accept USDC, or what is new on Arc.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc apps, last 7 days
  • arc_ecosystemEvery project in the Arc ecosystem directory (apps, wallets, exchanges, banks, infrastructure, partners) with category and status: live on mainnet, deployed or announced.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Every project in the Arc ecosystem directory (apps, wallets, exchanges, banks, infrastructure, partners) with category and status: live on mainnet, deployed or announced. Use this when asked what exists on Arc, which projects are in a category, or whether a company is on Arc. Not for token prices.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc ecosystem: directory
  • arc_entityOne project in the Arc ecosystem directory by slug (slugs come from arc_ecosystem): summary, status with evidence, links, contracts on Arc and sources.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One project in the Arc ecosystem directory by slug (slugs come from arc_ecosystem): summary, status with evidence, links, contracts on Arc and sources.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc project: detail
  • arc_indicesLatest hourly close of the Arc Builders, Integrations and Ecosystem indices (ABI, AII, AEI), their 24 h change base and decay parameters.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc indices: latest
  • arc_new_appsArc apps first seen in an index after a given hour.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Arc apps first seen in an index after a given hour. Use this when asked what is new on Arc.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc apps: newly seen
  • arc_numbersChain-level Arc numbers: USDC and EURC supply, all stablecoins and TVL (from DefiLlama), estimated 24 h stablecoin volume, apps and projects, index closes and a dated timeline, eac…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Chain-level Arc numbers: USDC and EURC supply, all stablecoins and TVL (from DefiLlama), estimated 24 h stablecoin volume, apps and projects, index closes and a dated timeline, each with its source and date. Use this when asked how big Arc is, how much USDC is on Arc, or Arc's TVL or volume.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc in numbers
  • arc_verifiedArc projects whose builder proof validates against the Arc mainnet builder registry.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Arc projects whose builder proof validates against the Arc mainnet builder registry.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • title: Arc builders: verified

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:31 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (3 irreversible, 10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://builder.registrai.cc/api/mcp: tools/list returned 13 tools to an anonymous client, including arc_index_history (irreversible), arc_app_history (irreversible), arc_apps_daily (irreversible), arc_indices (write), arc_apps (write) and 8 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 11 to 13
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 17 to 11

Findings

Matches of fixed checks, with the text they matched.

4 warn
  • The server marks "arc_index_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "arc_app_history" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "arc_apps_daily" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.

    What this check looks for
  • The server marks "arc_address_label" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "arc_address_label" says "label": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 13.View diff
    • Tools that change things, listed without credentials: 11 to 13
  2. Tools2 added.+2 addedView diff
  3. Tools1 added, 6 removed, 1 changed.+1 added−6 removed~1 changedView diff
    • Added:arc_apps_weekChanges things
    • Removed:arc_app_history_deep
    • Removed:arc_contract
    • Removed:arc_events
    • Removed:arc_index_history_deep
    • Removed:arc_members_day
    • Removed:arc_project_scope
    • Changed:arc_ecosystemChanges thingsinputSchema
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 17 -> 11.View diff
    • Tools that change things, listed without credentials: 17 to 11

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http arc-data https://builder.registrai.cc/api/mcp
claude mcp add --transport http arc-data https://builder.registrai.cc/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__arc-data__arc_indices",
      "mcp__arc-data__arc_index_history",
      "mcp__arc-data__arc_apps",
      "mcp__arc-data__arc_app",
      "mcp__arc-data__arc_app_history",
      "mcp__arc-data__arc_new_apps",
      "mcp__arc-data__arc_verified",
      "mcp__arc-data__arc_ecosystem",
      "mcp__arc-data__arc_entity",
      "mcp__arc-data__arc_numbers",
      "mcp__arc-data__arc_apps_week",
      "mcp__arc-data__arc_apps_daily",
      "mcp__arc-data__arc_address_label"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as arc-data. Review it before you use it.

Capability tags behind 3 rules
  • mcp__arc-data__arc_index_history outbound
  • mcp__arc-data__arc_app_history outbound
  • mcp__arc-data__arc_apps_daily outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/cc.registrai/arc-data/verify?hash=1e0def363b156de7b69abd7a99330b3e9e5206f1b986b61fe709e0b3eb930b51" | jq -e '.changed == false'

Pinned hash 1e0def363b15, from Nov 12, 2026, 07:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/cc.registrai/arc-data/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for cc.registrai/arc-data
[![Anlyon Radar](https://radar.anlyon.com/badge/cc.registrai/arc-data.svg)](https://radar.anlyon.com/servers/cc.registrai/arc-data)

Source: MCP Registry. Synced Oct 21, 2026, 17:46 UTC.

Registrai Arc data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Registrai Arc data MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 13 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Registrai Arc data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Registrai Arc data MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: arc_index_history, arc_app_history and arc_apps_daily.

What tools does the Registrai Arc data MCP server have?

13 tools: 3 irreversible, 10 write. arc_index_history, arc_app_history, arc_apps_daily, arc_indices, arc_apps, arc_app, arc_new_apps, arc_verified and 5 more.

Does the Registrai Arc data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Registrai Arc data MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): arc_index_history, arc_app_history and arc_apps_daily.

Has the Registrai Arc data MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.