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.

io.github.RealSpap/authority-risk-mcp

PYPI · AUTHORITY-RISK-MCP · 2 COMPONENTS

Read-only tools for AI agents: who can change a smart contract, how fast. Signed data, testnet.

77 Trust /100

Last scanned (17 hours ago)

Scores higher than 75% of PyPI servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to RealSpap/authority-risk-oracle-showcase). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 436 tokens (~109/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 9% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 15 Oct 26 +27
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: fair functional
    • First check of Destructive annotations: pass functional
    • First check of Tool coverage: 9 functional
    • First check of Schema quality: pass functional
  • 14 Oct 26 50

    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 17 Oct 2026 · Analysed pypi/authority-risk-mcp@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo RealSpap/authority-risk-oracle-showcase
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/RealSpap/authority-risk-oracle-showcase/.github/workflows/publish-mcp.yml@refs/tags/mcp-v0.1.0
Rekor log index 3250837598
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:229640fe2acf172eb04485e5b551c4badbdf16e9c4bc39a9e5ec724527e9095e

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~361 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
checkProtocol ~74

A protocol on every chain it is tracked on, as JSON: its weakest contract, how many were read, stale or alerting contracts, and a verdict: ok / fail / unread_part (some contracts not read: not a pass) / unread.

NameTypeReqDescription
min_scoreinteger––
protocolstringyes–

No output schema declared.

No examples provided.

getScore ~110

The score of one contract as JSON: composite and sub-scores, whether it is stale, when it was pushed and read, the oracle and block it was read at, and a `cast call` to replay the reading. A value not read is null and named in `not_read`, never 0.

NameTypeReqDescription
addressstringyes–
chainstringyesrobinhood, ethereum-l1, arbitrum, base, tempo, plasma, monad, hyperliquid or solana

No output schema declared.

No examples provided.

listTargets ~89

The tracked contracts that match a score filter, weakest first, as JSON. `score_not_read_so_not_filtered` counts the rows whose score was not read: they are not in the answer and they are not zero.

NameTypeReqDescription
chainstring––
limitinteger––
max_scoreinteger––
min_scoreinteger––
staleboolean––

No output schema declared.

No examples provided.

whoControls ~88

Who can change one contract and how fast, as JSON: admin kind (EOA, Safe, timelock, ...), threshold and owners, keys needed to act, the delay, modules, a pending admin change, and what moving the money would take. status `not_read` when the admin could not be classified.

NameTypeReqDescription
addressstringyes–
chainstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.RealSpap/authority-risk-mcp server?

io.github.RealSpap/authority-risk-mcp runs locally as a PyPI package, launched with uvx authority-risk-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · authority-risk-mcp

# add to Claude Code
claude mcp add realspap-authority-risk-mcp -- uvx authority-risk-mcp
Common questions

What is the io.github.RealSpap/authority-risk-mcp server?

io.github.RealSpap/authority-risk-mcp is listed in the public MCP registry as io.github.RealSpap/authority-risk-mcp. Read-only tools for AI agents: who can change a smart contract, how fast. Signed data, testnet. This page covers its PyPI package (authority-risk-mcp).

Is the io.github.RealSpap/authority-risk-mcp server safe to use?

io.github.RealSpap/authority-risk-mcp scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. 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 io.github.RealSpap/authority-risk-mcp server expose?

io.github.RealSpap/authority-risk-mcp exposes 4 tools: getScore, listTargets, whoControls, checkProtocol. Their descriptions and schemas cost roughly 361 tokens of context every time the server is loaded.

Is the io.github.RealSpap/authority-risk-mcp server still maintained?

io.github.RealSpap/authority-risk-mcp is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.RealSpap/authority-risk-mcp server under?

io.github.RealSpap/authority-risk-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.