Azeth MCP Server

@azeth/mcp-server npm v0.2.24 Source verified

Published by azeth-protocol — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for the Azeth trust infrastructure — smart accounts, payments, reputation, and discovery tools for AI agents

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 36

Each tool and what it can reach — statically extracted from the published source.

  • azeth_send_messagenetwork egress
  • azeth_accountsno sensitive capability
  • azeth_balanceno sensitive capability
  • azeth_cancel_agreementno sensitive capability
  • azeth_check_reachabilityno sensitive capability
  • azeth_create_accountno sensitive capability
  • azeth_create_payment_agreementno sensitive capability
  • azeth_depositno sensitive capability
  • azeth_discover_agent_capabilitiesno sensitive capability
  • azeth_discover_servicesno sensitive capability
Show 26 more tools ↓
  • azeth_execute_agreementno sensitive capability
  • azeth_get_active_opinionno sensitive capability
  • azeth_get_agreementno sensitive capability
  • azeth_get_cross_chain_reputationno sensitive capability
  • azeth_get_due_agreementsno sensitive capability
  • azeth_get_guardrailsno sensitive capability
  • azeth_get_net_paidno sensitive capability
  • azeth_get_registry_entryno sensitive capability
  • azeth_get_weighted_reputationno sensitive capability
  • azeth_guardian_approveno sensitive capability
  • azeth_guardian_statusno sensitive capability
  • azeth_historyno sensitive capability
  • azeth_list_agreementsno sensitive capability
  • azeth_list_conversationsno sensitive capability
  • azeth_payno sensitive capability
  • azeth_prove_reputationno sensitive capability
  • azeth_publish_serviceno sensitive capability
  • azeth_receive_messagesno sensitive capability
  • azeth_smart_payno sensitive capability
  • azeth_submit_opinionno sensitive capability
  • azeth_subscribe_serviceno sensitive capability
  • azeth_transferno sensitive capability
  • azeth_update_serviceno sensitive capability
  • azeth_update_service_batchno sensitive capability
  • azeth_whitelist_protocolno sensitive capability
  • azeth_whitelist_tokenno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.24 latest A 97/100 0 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/azeth-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/azeth-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/azeth-mcp-server"><img src="https://mcptrustchecker.com/registry/azeth-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/azeth-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @azeth/mcp-server --online

Use the free API → How scoring works

More in Finance & Commerce