BNB Smart Chain Testnet
← All skills
Audit inconclusivecurated example, not installable

RPC Proxy (example, audit inconclusive)

MCP server · v0.5.0 · published by HelloFugu example author · free

Installing this gives the agent tools the agent can call, described in text the agent trusts.

Curated examples. The registry answered, and it holds nothing that matches.

These records are curated examples shipped with the backend to exercise every audit status. They are not real skills, authors, or auditors, and nothing here is installable. Every example carries example: true and an id prefixed with 'example-'.

Who the auditors are
How it got here
  1. 1the skill registry, answered, but empty, 0 itemsskill example-rpc-proxy is not in the registry
  2. 2bundled examples, answered, 1 itemThese records are curated examples shipped with the backend to exercise every audit status. They are not real skills, authors, or auditors, and nothing here is installable. Every example carries example: true and an id prefixed with 'example-'.

Audit inconclusive

Not known. An audit ran with no verdict, or its evidence is not held. Nothing is cleared.

audit example-audit-rpc-1 ran against this build and could not reach a verdict: the shipped artefact is a stripped binary the sandbox could not instrument, so its actual behaviour was never observed

Same bytes, both sides

audited
633d56858dfb8e6db2fb…
serving
633d56858dfb8e6db2fb…
Audits on record
1 · full history below
Verdict completed
2026-09-06
Auditor
example-auditor-reef
Evidence held
on record, but not openable from here: the .invalid domain is reserved by RFC 2606 and never resolves, this is an example, and there is nothing behind it

What the author claims

Quoted word for word, and treated as untrusted.

Proxies JSON-RPC calls to a configured node. The audit ran but could not observe the binary's behaviour, so it reached no verdict, which is reported as INCONCLUSIVE rather than rounded to either safe or dangerous.

  • claims: forwards JSON-RPC requests

Builds

A verdict covers only the exact bytes it examined.

  • v0.5.0633d56858dfb8e6d…2026-09-06examined by example-audit-rpc-1served now

Audit history: 1 on record

automated audit of v0.5.0

example-audit-rpc-1

State
complete · verdict inconclusive · risk medium
Auditor
example-auditor-reef
Build examined
633d56858dfb…
Dates
requested 2026-09-06 · completed 2026-09-06
Fee
$1.00 paid if the verdict stands
Bond
$2,500.00 lost if the verdict is overturned

the shipped artefact is a stripped binary the sandbox could not instrument, so its actual behaviour was never observed

Scope: description-injection · network egress · wallet. Nothing else was examined.

Pipeline

  1. scanner · passedno hidden directives in the manifest
  2. sandbox · inconclusivebinary could not be instrumented; behaviour unobserved
  3. fork · inconclusiveno transactions were produced, but none could be ruled out either
  4. synthesizer · inconclusiveinsufficient evidence to conclude either way

Findings

  • mediumbehaviour could not be observed

    The sandbox could not instrument the shipped binary. Nothing malicious was seen, and nothing was ruled out, this is reported as inconclusive, not as clean.

Evidence

The report is not openable from here: the .invalid domain is reserved by RFC 2606 and never resolves, this is an example, and there is nothing behind it.its digest is on record: sha256 cc793ac4d473ef413716893e…

Escrow

This audit has not been settled on chain: the backend reports NOT_WIRED.Escrow contract: 0x0354d2a4…ec8a52 ↗

Identity

Registry id
example-rpc-proxy
Source
https://example.invalid/skills/rpc-proxy: the .invalid domain is reserved by RFC 2606 and never resolves, this is an example, and there is nothing behind it
Author address
0x00000000…00dEaD ↗
Listed
2026-09-06 09:00 UTC

Digest of the build being served

633d56858dfb8e6db2fbb98743c9fa69912427e4a43169d514580f3dad7a30fe

What makes a verdict cost something

Fee and stake sit in FuguAuditEscrow ↗, verified on testnet. This cycle ran on it end to end.

  1. 01

    An audit job was created, with the developer, the auditor and the exact build named

    0xa522fcb0…267c22 ↗
  2. 02

    The developer funded the fee: 5 mUSD paid in and held

    0x11488b8b…62534b ↗
  3. 03

    The auditor put 2 mUSD at stake, the money it loses if the verdict is wrong

    0x2a867ede…108862 ↗
  4. 04

    The verdict stood, so the fee and the stake were released: 7 mUSD to the auditor

    0x338030ed…520c53 ↗