ArcHive MCP server
xyz.arc-hive/archivearc-hive.xyzstreamable-httpv0.0.5Scanned
Pay-per-use USDC marketplace of Intel TDX enclaves verified on Arc testnet: read, check, prepare
16 tools: 9 change things and 7 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
9 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
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 ArcHive MCP server can do
The ArcHive MCP server is published by arc-hive.xyz, a domain the MCP Registry verified. It has 16 tools. It can create or change data (9 tools: arc_activity, arc_pricing, arc_verify_receipt, arc_bounty_prepare_create and 5 more), but cannot delete data. 7 tools only read.
1 tool brings in text other people can write (arc_machines_list).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 0.0.5.
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.
16 tools
Changes things 9Claude Code: ask
arc_activityRecent on-chain activity of the network's contracts (enclave registrations, sessions, settlements, bounties, verdicts), newest first.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.
Description, as the server wrote it Recent on-chain activity of the network's contracts (enclave registrations, sessions, settlements, bounties, verdicts), newest first. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).
arc_bounty_prepare_createCreates a sealed bounty, with a predicate helper ("the USDC balance of the target contract drops by at least minDrop" → ERC20_DROP clause), tiers, fees read on-chain, createBounty …No findings
Why it is in this group
- The name "arc_bounty_prepare_create" says "create": a word for a change.
Description, as the server wrote it Creates a sealed bounty, with a predicate helper ("the USDC balance of the target contract drops by at least minDrop" → ERC20_DROP clause), tiers, fees read on-chain, createBounty parameters and an EIP-3009 authorization. PREPARES only: signs and sends nothing, returns the data the user signs in their wallet.
arc_machine_diagnosticsDiagnostics of an operator's machine (ArcHive API): failed checks with the fix to apply, normal failures for the mode, recent log, attestation, on-chain registration.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.
Description, as the server wrote it Diagnostics of an operator's machine (ArcHive API): failed checks with the fix to apply, normal failures for the mode, recent log, attestation, on-chain registration. Read only.
arc_operator_planStep-by-step plan to become an operator: Intel TDX VM (Phala), app-compose, /attest, bond, registerEnclave, renewal; the bond rules with the figures read on-chain.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.
Description, as the server wrote it Step-by-step plan to become an operator: Intel TDX VM (Phala), app-compose, /attest, bond, registerEnclave, renewal; the bond rules with the figures read on-chain.
arc_operator_prepare_bondOperator bond deposit: EIP-3009 authorization for bond(), or encoded approve + bondFrom; checks balance, ban and minimum bond.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.
Description, as the server wrote it Operator bond deposit: EIP-3009 authorization for bond(), or encoded approve + bondFrom; checks balance, ban and minimum bond. PREPARES only: signs and sends nothing, returns the data the user signs in their wallet.
arc_operator_prepare_registerEnclave registration: anchor block, reading the VM's /attest (if enclaveUrl and operator are given), encoded registerEnclave transaction.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.
Description, as the server wrote it Enclave registration: anchor block, reading the VM's /attest (if enclaveUrl and operator are given), encoded registerEnclave transaction. PREPARES only: signs and sends nothing, returns the data the user signs in their wallet.
arc_pricingCost of a use: units × the product's price, with a readable line giving the unit (per token for a prepaid session, per call for x402, free, or paid by a bounty's pool).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.
Description, as the server wrote it Cost of a use: units × the product's price, with a readable line giving the unit (per token for a prepaid session, per call for x402, free, or paid by a bounty's pool).
arc_product_scaffoldSkeleton of a third-party product: container + enclave kit, app-compose, manifest, propose() parameters, then timelock and activate (bpsOperator + bpsAuthor + bpsNetwork = 10,000).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.
Description, as the server wrote it Skeleton of a third-party product: container + enclave kit, app-compose, manifest, propose() parameters, then timelock and activate (bpsOperator + bpsAuthor + bpsNetwork = 10,000).
arc_verify_receiptChecks an inference receipt the way SessionPay.settle does: the session's locked enclave, active at the anchor block under its operator, locked model, growing cumulative total; and…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.
Description, as the server wrote it Checks an inference receipt the way SessionPay.settle does: the session's locked enclave, active at the anchor block under its operator, locked model, growing cumulative total; and what the settlement would pay.
Only reads 7Show 7 read-only tools
arc_bountiesLists the sealed bounties of BOTH levels (open: SealedBounty, products 2 and 5; verified: SealedBountyVerified, product 7): level, contract, protocol, product, balance, deadline, p…No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it Lists the sealed bounties of BOTH levels (open: SealedBounty, products 2 and 5; verified: SealedBountyVerified, product 7): level, contract, protocol, product, balance, deadline, pause, open or not. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).
arc_enclave_statusState of ONE enclave by its signer: operator, product, TCB, expiry, active or not, the operator's bond (total, available, 24 h exposure on this product).No findings
Why it is in this group
- The name "arc_enclave_status" says "status": a word for reading.
Description, as the server wrote it State of ONE enclave by its signer: operator, product, TCB, expiry, active or not, the operator's bond (total, available, 24 h exposure on this product).
arc_enclavesLists the enclaves (the hive): operator, product, TCB, active or not at the head block, validity window in blocks, registered X25519 key.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it Lists the enclaves (the hive): operator, product, TCB, active or not at the head block, validity window in blocks, registered X25519 key. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).
arc_machines_listAn operator's machines (nodes) from the ArcHive API: mode (tdx, dstack, demo), online, last heartbeat, product, enclave URL and signer, diagnostics OK, registered.Reads text others writeNo findings
Why it is in this group
- The name "arc_machines_list" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it An operator's machines (nodes) from the ArcHive API: mode (tdx, dstack, demo), online, last heartbeat, product, enclave URL and signer, diagnostics OK, registered. Read only.
arc_productsLists the products of Arc's enclave network (price with its unit, shares, settlement, minimum bond, state).No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it Lists the products of Arc's enclave network (price with its unit, shares, settlement, minimum bond, state). Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).
arc_session_statusState of a SessionPay session: owner, product, operator, deposit, already paid, remainder, expiry, closed.No findings
Why it is in this group
- The name "arc_session_status" says "status": a word for reading.
Description, as the server wrote it State of a SessionPay session: owner, product, operator, deposit, already paid, remainder, expiry, closed.
arc_sessionsLists the SessionPay sessions opened by an account: product, deposit, already settled, remainder, closed, expiry.No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it Lists the SessionPay sessions opened by an account: product, deposit, already settled, remainder, closed, expiry. Read from the ArcHive API index; if the list is briefly unavailable, the tool says so (never a partial list).
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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- 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.
Looked at Nov 20, 2026, 18:20 UTC, unchanged since Nov 20, 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
- 9
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://arc-hive.xyz/mcp: tools/list returned 16 tools to an anonymous client, including arc_activity (write), arc_pricing (write), arc_verify_receipt (write), arc_bounty_prepare_create (write), arc_operator_plan (write) and 4 more
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.0.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http archive https://arc-hive.xyz/mcpclaude mcp add --transport http archive https://arc-hive.xyz/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__archive__arc_products",
"mcp__archive__arc_enclaves",
"mcp__archive__arc_bounties",
"mcp__archive__arc_sessions",
"mcp__archive__arc_enclave_status",
"mcp__archive__arc_session_status",
"mcp__archive__arc_machines_list"
],
"ask": [
"mcp__archive__arc_activity",
"mcp__archive__arc_pricing",
"mcp__archive__arc_verify_receipt",
"mcp__archive__arc_bounty_prepare_create",
"mcp__archive__arc_operator_plan",
"mcp__archive__arc_operator_prepare_bond",
"mcp__archive__arc_operator_prepare_register",
"mcp__archive__arc_product_scaffold",
"mcp__archive__arc_machine_diagnostics"
],
"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 archive. Review it before you use it.
Capability tags behind 1 rule
- mcp__archive__arc_machines_list untrusted-input
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/xyz.arc-hive/archive/verify?hash=0b043f3d25940b348271b355e9dde97f4e2f3cf01e27093eb4d329efcc02adbb" | jq -e '.changed == false'Pinned hash 0b043f3d2594, from Nov 20, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/xyz.arc-hive/archive/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/xyz.arc-hive/archive)Source: MCP Registry · repository. Synced Nov 20, 2026, 10:18 UTC.
ArcHive MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ArcHive MCP server safe?
- No scan can promise that. What its definitions show: 16 tools, 9 of which can change, send or delete something, and 0 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 ArcHive MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the ArcHive MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ArcHive MCP server have?
- 16 tools: 9 write, 7 read. arc_activity, arc_pricing, arc_verify_receipt, arc_bounty_prepare_create, arc_operator_plan, arc_operator_prepare_bond, arc_operator_prepare_register, arc_product_scaffold and 8 more.
Does the ArcHive MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ArcHive MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the ArcHive MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.