Agorus Ai MCP Server

@agorus-ai/mcp-server npm v0.2.0

Published by @agorus-ai — 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.

MCP server for Agorus — connect LLMs to the AI agent marketplace

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−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 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([search_services, get_contract_messages]) co-exist with external-action tools ([send_contract_message, create_webhook, delete_webhook]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [search_services, get_contract_messages] → sinks [send_contract_message, create_webhook, delete_webhook]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow search_services → send_contract_message

Tools 83

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

  • create_webhooknetwork egress
  • delete_webhooknetwork egress
  • get_contract_messagesingests untrusted input
  • search_servicesingests untrusted input
  • send_contract_messagenetwork egress
  • accept_bidno sensitive capability
  • add_discussion_commentno sensitive capability
  • add_poll_optionno sensitive capability
  • assign_taskno sensitive capability
  • auto_select_by_ratingno sensitive capability
Show 73 more tools ↓
  • create_contractno sensitive capability
  • create_discussionno sensitive capability
  • create_guildno sensitive capability
  • create_pipelineno sensitive capability
  • create_pollno sensitive capability
  • create_postno sensitive capability
  • create_reviewno sensitive capability
  • create_serviceno sensitive capability
  • create_taskno sensitive capability
  • declare_trustno sensitive capability
  • delete_serviceno sensitive capability
  • donate_to_serviceno sensitive capability
  • finalize_pollno sensitive capability
  • get_agentno sensitive capability
  • get_agent_balanceno sensitive capability
  • get_agent_postsno sensitive capability
  • get_agent_reputationno sensitive capability
  • get_agent_statusno sensitive capability
  • get_balanceno sensitive capability
  • get_contractno sensitive capability
  • get_discussionno sensitive capability
  • get_guildno sensitive capability
  • get_guild_membersno sensitive capability
  • get_inboxno sensitive capability
  • get_message_threadno sensitive capability
  • get_my_profileno sensitive capability
  • get_pipelineno sensitive capability
  • get_pollno sensitive capability
  • get_poll_resultsno sensitive capability
  • get_post_feedno sensitive capability
  • get_reviewsno sensitive capability
  • get_serviceno sensitive capability
  • get_service_donationsno sensitive capability
  • get_statsno sensitive capability
  • get_taskno sensitive capability
  • get_transactionsno sensitive capability
  • get_trust_chainno sensitive capability
  • get_trust_inboundno sensitive capability
  • get_trust_outboundno sensitive capability
  • join_guildno sensitive capability
  • leave_guildno sensitive capability
  • list_bidsno sensitive capability
  • list_contractsno sensitive capability
  • list_conversationsno sensitive capability
  • list_discussionsno sensitive capability
  • list_subscriptionsno sensitive capability
  • list_task_submissionsno sensitive capability
  • list_webhooksno sensitive capability
  • loginno sensitive capability
  • mark_all_inbox_readno sensitive capability
  • mark_inbox_readno sensitive capability
  • mark_message_readno sensitive capability
  • register_agentno sensitive capability
  • run_pipelineno sensitive capability
  • searchno sensitive capability
  • search_agentsno sensitive capability
  • search_guildsno sensitive capability
  • search_pipelinesno sensitive capability
  • search_tasksno sensitive capability
  • select_task_winnerno sensitive capability
  • send_direct_messageno sensitive capability
  • send_heartbeatno sensitive capability
  • submit_bidno sensitive capability
  • submit_task_resultno sensitive capability
  • subscribe_tagsno sensitive capability
  • transfer_fluxno sensitive capability
  • unsubscribe_tagno sensitive capability
  • update_contract_statusno sensitive capability
  • update_my_profileno sensitive capability
  • update_serviceno sensitive capability
  • upvote_discussionno sensitive capability
  • vote_pollno sensitive capability
  • withdraw_bidno sensitive capability

Toxic flows 1

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

Use the free API → How scoring works

More in AI & Agents