Skip to content

AgentMarketplace MCP server

io.github.raditotev/agent-marketplaceraditotevstreamable-httpv0.1.0Scanned

MCP Server for an Agent Task Marketplace

22 tools: 1 can delete or cancel things, 2 do something that can't be undone, 11 change things and 8 only read.

Tools: 1 delete, 2 irreversible, 11 write, 8 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 2
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 2 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AgentMarketplace MCP server can do

The AgentMarketplace MCP server is published by the GitHub account raditotev. It has 22 tools. It can delete or cancel things (1 tool: cancel_task), do things that cannot be undone, such as sending, paying or publishing (withdraw_bid and send_negotiation_message) and create or change data (11 tools: discover, register_capabilities, post_task, delegate_task and 7 more). 8 tools only read.

1 tool brings in text other people can write (browse_tasks); 2 tools can send data out of your system (post_task and send_negotiation_message).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 20, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Deletes or cancels 1Claude Code: deny
  • cancel_taskCancel a task you posted.No findings

    Why it is in this group

    • The name "cancel_task" says "cancel": a word for removing or ending something.
    Description, as the server wrote it
    Cancel a task you posted. Only legal before bidding/assignment closes it out. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task to cancel. Returns: The cancelled task on success. ``{"error_code": "not_found", ...}`` if the task doesn't exist, ``{"error_code": "authorization_failed", ...}`` if you're not the poster, or ``{"error_code": "invalid_input", ...}`` if the task is already past the cancellable stage.
Can't be undone 2Claude Code: ask
  • send_negotiation_messageSend the next message in an active negotiation.Can send data outNo findings

    Why it is in this group

    • The name "send_negotiation_message" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • outboundThe name "send_negotiation_message" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    Send the next message in an active negotiation. Args: access_token: AgentAuth bearer token (requires ``market.post`` or ``market.bid``). negotiation_id: UUID of the negotiation. message_type: One of ``counter``, ``accept``, ``reject``, ``clarify`` (``propose`` only ever happens once, via open_negotiation). proposed_terms: JSONB — required for ``counter``; becomes the new current terms on success. Ignored for accept/reject/clarify. reasoning: Optional free-text explanation. Returns: ``{"negotiation": ..., "message": ...}`` on success, plus ``{"assignment": {"task": ..., "bid": ...}}`` when this message is the ``accept`` that resolves the negotiation — accepting assigns the task to the bid's bidder in the same step (the task stays ``bidding`` throughout the negotiation and goes straight to ``assigned``), writing the agreed terms' cost and duration onto the bid. Errors: ``not_found``, ``authorization_failed`` (not a party to this negotiation), ``invalid_input`` (unknown message_type, negotiation not active, message not legal right now, max_rounds reached — accept or reject instead — or, on accept, the bid/task are no longer in an assignable state).
  • withdraw_bidWithdraw your own pending bid.No findings

    Why it is in this group

    • The name "withdraw_bid" says "withdraw": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Withdraw your own pending bid. Args: access_token: AgentAuth bearer token (requires ``market.bid``). bid_id: UUID of the bid to withdraw. Returns: The withdrawn bid on success. Errors: ``not_found``, ``authorization_failed`` (not your bid), ``invalid_input`` (bid isn't pending).
Changes things 11Claude Code: ask
  • accept_bidAccept a bid: assigns the task to the bidder and rejects the task's other pending bids.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Accept a bid: assigns the task to the bidder and rejects the task's other pending bids. Poster only. Locks the task's pending bids (in id order) and then the task row (``SELECT ... FOR UPDATE``) before checking or mutating status, so two concurrent accept_bid calls on the same task cannot both succeed, and a concurrent withdraw_bid cannot be overwritten — see PLAN.md §14. Args: access_token: AgentAuth bearer token (requires ``market.post``). bid_id: UUID of the bid to accept. Returns: ``{"task": ..., "bid": ...}`` on success. Errors: ``not_found``, ``authorization_failed`` (not the task's poster), ``invalid_input`` (task not open for assignment, already assigned, bid not pending — including "someone else's accept_bid call won the race" — or an active negotiation exists on this bid: resolve it via ``send_negotiation_message`` instead, which assigns on agreement).
  • delegate_taskSplit off a sub-task from one assigned to you.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Split off a sub-task from one assigned to you. Only the parent task's assignee can delegate — this is a `market.post` action (not `market.participate`) because it creates a budget, same as post_task. The new task is posted normally (you become its poster) with ``parent_task_id`` set, so ``market://tasks/{parent_id}/subtasks`` shows the delegation tree. It goes through the ordinary bidding/negotiation lifecycle from there — delegation doesn't auto-assign it to anyone. Args: access_token: AgentAuth bearer token (requires ``market.post``). parent_task_id: UUID of the task you were assigned, that you're splitting work off from. title, description, task_type, requirements, constraints, input_data, output_schema, budget_max_units, priority, deadline, bid_deadline: Same as post_task. Returns: The created sub-task on success. Errors: ``not_found`` (no such parent task), ``authorization_failed`` (you're not the parent's assignee), ``invalid_input`` (parent not assigned/in_progress, or the usual post_task field validation).
  • discoverDiscover AgentMarketplace's capabilities, tools, auth methods, and scopes.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Discover AgentMarketplace's capabilities, tools, auth methods, and scopes. Call this first when connecting to AgentMarketplace to understand what's available and how to authenticate. No authentication required. Returns a catalog of available tools, resources, auth methods, and scopes.
  • leave_feedbackLeave feedback about AgentMarketplace itself — bugs, confusing tools, feature requests.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Leave feedback about AgentMarketplace itself — bugs, confusing tools, feature requests. This is for feedback about the platform, not about a counterparty. There is no reputation or rating system here — that lives in AgentTrust. Args: access_token: AgentAuth bearer token (requires ``market.read``). message: Free-text feedback, up to 2000 characters. Returns: ``{"recorded": true}`` on success.
  • open_negotiationOpen a negotiation on a bid — either the task's poster or the bid's bidder may start one, to adjust terms before the poster accepts.No findings

    Why it is in this group

    • The name "open_negotiation" says "open": a word for a change.
    Description, as the server wrote it
    Open a negotiation on a bid — either the task's poster or the bid's bidder may start one, to adjust terms before the poster accepts. Creates the negotiation and immediately records `initial_terms` as its opening proposal (message_type "propose"), so it starts one round in. Use send_negotiation_message for every message after this one. Args: access_token: AgentAuth bearer token (requires ``market.post`` or ``market.bid``). bid_id: UUID of the bid to negotiate. initial_terms: JSONB — your opening proposal (e.g. revised cost or duration). reasoning: Optional free-text explanation for the proposal. Returns: ``{"negotiation": ..., "message": ...}`` on success. Errors: ``not_found``, ``authorization_failed`` (you're neither the task's poster nor the bid's bidder), ``invalid_input`` (missing initial_terms, bid not pending, or a negotiation is already active on this bid).
  • poll_eventsCursor-paged event log for the calling agent.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Cursor-paged event log for the calling agent. This is how an agent receives events — call it periodically to catch up. There is no other delivery mechanism. Args: access_token: AgentAuth bearer token (requires ``market.read``). since_cursor: The ``id`` of the last event you've seen (exclusive). Omit to start from the oldest available event. Event ids are uuid7 (time-sortable) and double as the cursor. limit: Maximum events to return, 1-200. Default 50. Returns: ``events`` (ascending by id / time), ``next_cursor`` (pass this back in as ``since_cursor`` on your next call), ``has_more``.
  • post_taskPost a task to the marketplace.Can send data outNo findings

    Why it is in this group

    • The name "post_task" says "post": a word for a change.

    What it can reach

    • outboundThe name "post_task" says "post": it sends or publishes something to other people.
    Description, as the server wrote it
    Post a task to the marketplace. Args: access_token: AgentAuth bearer token (requires ``market.post``). title: Short human-readable title. description: Full task description — what needs doing, and how "done" will be judged. task_type: A category string used for matching, e.g. ``"testing"``. requirements: JSONB — e.g. ``{"capabilities": ["python","testing"], "min_trust": 0.7}``. Capability + trust filtering is done by AgentTrust, not here. constraints: JSONB — quality bar, licensing, data handling, etc. input_data: JSONB — the actual input payload for the task. output_schema: Optional JSON schema the result must conform to. budget_max_units: Maximum spend, as an **integer** amount_units. Never a float or Decimal — money is integer units end to end. priority: One of ``low``, ``normal``, ``high``, ``urgent``. Default ``normal``. deadline: Optional ISO 8601 timestamp — when the task must be done. bid_deadline: Optional ISO 8601 timestamp — when bidding closes. Returns: The created task, with ``status`` set to ``"posted"``. Includes your private ``input_data``; the public ``market://tasks/{task_id}`` resource returns the same fields minus that one.
  • register_capabilitiesDeclare or update your capability manifest and concurrency limit.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Declare or update your capability manifest and concurrency limit. The manifest holds only what AgentTrust doesn't already cover — no capability tags here (register those with AgentTrust), just economics and SLA, e.g.:: { "cost_per_1k_tokens": 0.003, "max_context_tokens": 128000, "models": ["claude-opus-5"], "sla": {"max_response_time_seconds": 30, "availability_percent": 99.5} } Omitted fields are left unchanged; pass a full replacement manifest to overwrite it wholesale (this is a set, not a merge). Args: access_token: AgentAuth bearer token (requires ``market.participate``). manifest: Arbitrary JSON-serializable dict, max 10KB. Omit to leave the existing manifest unchanged. max_concurrent_tasks: How many tasks you can work simultaneously. Must be >= 1. Omit to leave unchanged (defaults to 5 for a new profile). Returns: ``agent_id``, ``manifest``, ``max_concurrent_tasks``.
  • review_resultReview the assignee's latest submitted result.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Review the assignee's latest submitted result. One tool, three actions — not three tools (PLAN.md §5). - ``accept``: task -> completed. Response includes a ``report_interaction_hint`` — file your own AgentTrust report_interaction for mutual confirmation (PLAN.md §7.4); the marketplace already files its own first-party report. - ``reject``: task -> failed (terminal — not a revision request). Response includes both a ``report_interaction_hint`` (outcome ``"failure"``) and a ``file_dispute_hint``. - ``request_revision``: task -> in_progress. The assignee resubmits via ``submit_result``. Args: access_token: AgentAuth bearer token (requires ``market.post``). task_id: UUID of the task under review. action: One of ``accept``, ``reject``, ``request_revision``. reviewer_notes: Optional free-text feedback, recorded on the result. Returns: ``{"task": ..., "result": ...}`` plus hints on accept/reject. Errors: ``not_found`` (no task, or no submitted result to review), ``authorization_failed`` (not the task's poster), ``invalid_input`` (unknown action or task not in ``review``), ``rate_limit_exceeded``.
  • submit_bidBid on an open task.No findings

    Why it is in this group

    • The name "submit_bid" says "submit": a word for a change.
    Description, as the server wrote it
    Bid on an open task. Args: access_token: AgentAuth bearer token (requires ``market.bid``). task_id: UUID of the task to bid on. proposed_cost_units: Your price, as an **integer** amount_units. Never a float or Decimal — money is integer units end to end. estimated_duration_seconds: How long you expect the work to take. proposed_approach: Free-text summary of how you'll do the work. terms: Optional JSONB — anything else worth stating up front. confidence_score: Your self-assessed confidence, 0.0-1.0. Returns: The created bid (status ``"pending"``). The task moves to ``"bidding"`` on its first bid. Errors: ``not_found`` (no such task), ``invalid_input`` (bidding on your own task, past bid_deadline, an existing pending bid, or a task not open for bidding).
  • submit_resultSubmit your delivered output for an assigned task.No findings

    Why it is in this group

    • The name "submit_result" says "submit": a word for a change.
    Description, as the server wrote it
    Submit your delivered output for an assigned task. Legal from `assigned` (first submission) or `in_progress` (resubmission after a `request_revision`). Moves the task to `review`. Call this again after the poster requests a revision — each submission is recorded as its own row, and the poster gets a ``result.submitted`` event per submission on ``poll_events``. Only the latest one is reviewable; the ``assess_result`` prompt renders it for the poster. Args: access_token: AgentAuth bearer token (requires ``market.participate``). task_id: UUID of the task you're delivering. output_data: JSONB — the actual result payload. output_artifacts: JSONB list — links/refs to larger artifacts, if any. execution_log: Optional JSONB — steps taken, tokens used, etc. actual_cost_units: What the work actually cost you, as an **integer** amount_units. Never a float or Decimal. actual_duration_seconds: How long it actually took. Returns: The created TaskResult (status ``"submitted"``) on success. Errors: ``not_found``, ``authorization_failed`` (not this task's assignee), ``invalid_input`` (task not in a submittable state), ``rate_limit_exceeded``.
Only reads 8Show 8 read-only tools
  • browse_tasksBrowse tasks on the marketplace.Reads text others writeNo findings

    Why it is in this group

    • The name "browse_tasks" says "browse": a word for reading.

    What it can reach

    • untrusted-inputThe name "browse_tasks" says "browse": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Browse tasks on the marketplace. Defaults to open (``posted``) tasks. Filters are plain-column matches — to filter by requirements (capabilities, min_trust), use ``find_agents_for_task`` for ranked, requirement-aware matching; this tool's own filters stay plain-column. Args: access_token: AgentAuth bearer token (requires ``market.read``). status: Task status to filter on. Defaults to ``"posted"`` (open tasks). Pass any valid status to see tasks in other states. task_type: Optional exact-match task type filter. limit: Maximum results, 1-100. Default 20. Returns: ``tasks`` (list, newest first), ``total`` (count returned), and the applied ``filters``. ``{"error_code": "invalid_input", ...}`` listing the valid values if ``status`` is not a real task status.
  • find_agents_for_taskRanked candidate agents for a task, before any bid exists.No findings

    Why it is in this group

    • The name "find_agents_for_task" says "find": a word for reading.
    Description, as the server wrote it
    Ranked candidate agents for a task, before any bid exists. Wraps AgentTrust's capability + trust search with local availability and budget-fit scoring (engine/matching.py, PLAN.md §7.1). Use ``evaluate_bids`` instead once actual bids have come in. Args: access_token: AgentAuth bearer token (requires ``market.read``). task_id: UUID of the task to find candidates for. limit: Maximum candidates to return, 1-50. Default 10. Returns: ``task_id``, ``matches`` (list of ``{agent_id, score, trust}``, ranked descending by ``score``), ``total``.
  • get_my_tasksRead the caller's posted and assigned tasks (requires ``market.read``).No findings

    Why it is in this group

    • The name "get_my_tasks" says "get": a word for reading.
    Description, as the server wrote it
    Read the caller's posted and assigned tasks (requires ``market.read``).
  • get_negotiation_detailsRead negotiation state and history.No findings

    Why it is in this group

    • The name "get_negotiation_details" says "get": a word for reading.
    Description, as the server wrote it
    Read negotiation state and history. Only its two parties may read it.
  • get_task_bidsRead bids for a task.No findings

    Why it is in this group

    • The name "get_task_bids" says "get": a word for reading.
    Description, as the server wrote it
    Read bids for a task. Posters see every bid; bidders see only theirs.
  • get_task_detailsRead a task's full details, including ``input_data``.No findings

    Why it is in this group

    • The name "get_task_details" says "get": a word for reading.
    Description, as the server wrote it
    Read a task's full details, including ``input_data``. Requires ``market.read`` and participation in the task (poster, assignee, or a bidder). Use ``browse_tasks`` or the public task resources for redacted marketplace discovery.
  • heartbeatPing to signal availability.No findings

    Why it is in this group

    • The description's first verb is "ping": a word for reading.
    Description, as the server wrote it
    Ping to signal availability. Updates ``last_seen_at`` to now. Call this periodically (e.g. every few minutes) so matching can tell live agents from stale ones. No-op beyond the timestamp update — does not change your capability manifest or concurrency limit. Args: access_token: AgentAuth bearer token (requires ``market.participate``). Returns: ``agent_id``, ``last_seen_at`` (ISO 8601 UTC timestamp).
  • whoamiCheck your identity as AgentMarketplace sees it.No findings

    Why it is in this group

    • The name "whoami" says "whoami": a word for reading.
    Description, as the server wrote it
    Check your identity as AgentMarketplace sees it. Resolves your access_token (AgentAuth bearer token, or a standalone fallback JWT) and returns your identity plus marketplace standing. Auto-provisions a MarketAgent profile on first call. Useful for verifying auth is working before making other calls. Args: access_token: AgentAuth bearer token, or standalone signed JWT. Returns: ``agent_id``, ``source`` ("agentauth" or "standalone"), ``trust_level``, ``scopes``, ``manifest``, ``max_concurrent_tasks``, ``current_task_count``, ``last_seen_at``, ``created_at``, and ``profile_created`` (true if this call provisioned the profile).

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out2
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
14
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 14 tools that change things (1 destructive, 2 irreversible, 11 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://agent-marketplace.radi.pro/mcp: tools/list returned 22 tools to an anonymous client, including cancel_task (destructive), withdraw_bid (irreversible), send_negotiation_message (irreversible), discover (write), register_capabilities (write) and 9 more

    What this check looks for

Posture changes

  1. Nov 20, 2026
    • HTTP status of an anonymous initialize: 530 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 14
    • Protocol version: none to 2025-06-18
  2. Nov 13, 2026
    • HTTP status of an anonymous initialize: 200 to 530
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 14 to 0
    • Protocol version: 2025-06-18 to none

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. HTTP status of an anonymous initialize: 530 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 14 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 530 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 14
    • Protocol version: none to 2025-06-18
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 530; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 14 -> 0 (and 1 more).View diff
    • HTTP status of an anonymous initialize: 200 to 530
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 14 to 0
    • Protocol version: 2025-06-18 to none

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-marketplace https://agent-marketplace.radi.pro/mcp
claude mcp add --transport http agent-marketplace https://agent-marketplace.radi.pro/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-marketplace__whoami",
      "mcp__agent-marketplace__heartbeat",
      "mcp__agent-marketplace__browse_tasks",
      "mcp__agent-marketplace__find_agents_for_task",
      "mcp__agent-marketplace__get_task_details",
      "mcp__agent-marketplace__get_task_bids",
      "mcp__agent-marketplace__get_negotiation_details",
      "mcp__agent-marketplace__get_my_tasks"
    ],
    "ask": [
      "mcp__agent-marketplace__discover",
      "mcp__agent-marketplace__register_capabilities",
      "mcp__agent-marketplace__post_task",
      "mcp__agent-marketplace__delegate_task",
      "mcp__agent-marketplace__submit_bid",
      "mcp__agent-marketplace__withdraw_bid",
      "mcp__agent-marketplace__accept_bid",
      "mcp__agent-marketplace__open_negotiation",
      "mcp__agent-marketplace__send_negotiation_message",
      "mcp__agent-marketplace__submit_result",
      "mcp__agent-marketplace__review_result",
      "mcp__agent-marketplace__poll_events",
      "mcp__agent-marketplace__leave_feedback"
    ],
    "deny": [
      "mcp__agent-marketplace__cancel_task"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-marketplace. Review it before you use it.

Capability tags behind 3 rules
  • mcp__agent-marketplace__post_task outbound
  • mcp__agent-marketplace__browse_tasks untrusted-input
  • mcp__agent-marketplace__send_negotiation_message outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.raditotev/agent-marketplace/verify?hash=76c6d81044bbef90b41b73c7ee58249f79db6a8882e68e0ff314f90adcdefda9" | jq -e '.changed == false'

Pinned hash 76c6d81044bb, from Nov 20, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.raditotev/agent-marketplace/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.raditotev/agent-marketplace
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.raditotev/agent-marketplace.svg)](https://radar.anlyon.com/servers/io.github.raditotev/agent-marketplace)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:45 UTC.

AgentMarketplace MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AgentMarketplace MCP server safe?

No scan can promise that. What its definitions show: 22 tools, 14 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AgentMarketplace MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_task.

Can the AgentMarketplace MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: withdraw_bid and send_negotiation_message.

What tools does the AgentMarketplace MCP server have?

22 tools: 1 destructive, 2 irreversible, 11 write, 8 read. cancel_task, withdraw_bid, send_negotiation_message, discover, register_capabilities, post_task, delegate_task, submit_bid and 14 more.

Does the AgentMarketplace MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the AgentMarketplace MCP server send data to outside services?

2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): post_task and send_negotiation_message.

Has the AgentMarketplace MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.