A2amarket MCP Server

@hz-abyssal-heart/a2amarket-mcp-server npm v0.4.0

Published by @hz-abyssal-heart — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

A2A Market MCP Server — Connect AI agents to A2A Market via Model Context Protocol. 51 MCP Tools covering sourcing, negotiation, settlement, and notification.

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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
High
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 = 93/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 − 7 = 93. 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
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 6

high Read-and-egress in one tool: "register_agent"MTC-FLOW-003

Tool "register_agent" can both read sensitive data and send data to an external destination. Even without an explicit untrusted-input leg, this is a single-call data-exfiltration path if the model is ever manipulated.

Fix: Separate reading from sending; require explicit user confirmation before egress of file/secret contents.

Location: flow register_agent

high Read-and-egress in one tool: "update_agent"MTC-FLOW-003

Tool "update_agent" can both read sensitive data and send data to an external destination. Even without an explicit untrusted-input leg, this is a single-call data-exfiltration path if the model is ever manipulated.

Fix: Separate reading from sending; require explicit user confirmation before egress of file/secret contents.

Location: flow update_agent

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([register_agent, update_agent]) and tools that can send data out ([register_agent, send_message, update_agent]) are exposed together. An agent can move private data to the sink.

Evidence: sources [register_agent, update_agent] → sinks [register_agent, send_message, update_agent]

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow register_agent → send_message

medium Unconstrained URL/host parameter "endpoint_url" on "register_agent"MTC-CAP-007

Tool "register_agent" takes a URL/host parameter "endpoint_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool register_agent · inputSchema.properties.endpoint_url

medium Unconstrained URL/host parameter "webhook_url" on "register_agent"MTC-CAP-007

Tool "register_agent" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool register_agent · inputSchema.properties.webhook_url

medium Unconstrained URL/host parameter "webhook_url" on "update_agent"MTC-CAP-007

Tool "update_agent" takes a URL/host parameter "webhook_url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool update_agent · inputSchema.properties.webhook_url

Tools 51

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

  • register_agentnetwork egressreads sensitive data
  • update_agentnetwork egressreads sensitive data
  • send_messagenetwork egress
  • accept_dealno sensitive capability
  • authorize_dealno sensitive capability
  • cancel_intentno sensitive capability
  • check_handleno sensitive capability
  • check_reputationno sensitive capability
  • create_settlementno sensitive capability
  • declare_supplyno sensitive capability
Show 41 more tools ↓
  • delete_hosted_strategyno sensitive capability
  • delete_supply_productno sensitive capability
  • get_balanceno sensitive capability
  • get_conversationno sensitive capability
  • get_incoming_intentsno sensitive capability
  • get_intent_statusno sensitive capability
  • get_messagesno sensitive capability
  • get_my_agentsno sensitive capability
  • get_negotiation_roundsno sensitive capability
  • get_negotiation_statusno sensitive capability
  • get_notificationsno sensitive capability
  • get_order_statusno sensitive capability
  • get_preferencesno sensitive capability
  • get_profileno sensitive capability
  • get_reputationno sensitive capability
  • get_sourcing_statusno sensitive capability
  • get_supply_productno sensitive capability
  • get_usageno sensitive capability
  • list_api_keysno sensitive capability
  • list_conversationsno sensitive capability
  • list_hosted_strategiesno sensitive capability
  • list_matchesno sensitive capability
  • list_responsesno sensitive capability
  • list_subscriptionsno sensitive capability
  • list_supply_productsno sensitive capability
  • mark_all_notifications_readno sensitive capability
  • mark_notification_readno sensitive capability
  • publish_intentno sensitive capability
  • reject_dealno sensitive capability
  • respond_to_intentno sensitive capability
  • rotate_api_keyno sensitive capability
  • search_agentsno sensitive capability
  • select_and_negotiateno sensitive capability
  • set_hosted_strategyno sensitive capability
  • set_preferencesno sensitive capability
  • submit_offerno sensitive capability
  • subscribe_intentno sensitive capability
  • unsubscribe_intentno sensitive capability
  • update_profileno sensitive capability
  • update_supplyno sensitive capability
  • verify_emailno sensitive capability

Toxic flows 3

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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.4.0 latest A 93/100 6 1.13.0 2026-09-07

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 · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/hz-abyssal-heart-a2amarket-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/hz-abyssal-heart-a2amarket-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/hz-abyssal-heart-a2amarket-mcp-server"><img src="https://mcptrustchecker.com/registry/hz-abyssal-heart-a2amarket-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/hz-abyssal-heart-a2amarket-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 @hz-abyssal-heart/a2amarket-mcp-server --online

Use the free API → How scoring works

More in Other