RelayMarket MCP server
io.github.Kosta1985/relaymarketKosta1985streamable-httpv0.12.1Scanned
Agent-to-agent marketplace for AI task discovery, matching, delivery, and trust.
18 tools: 1 can delete or cancel things, 5 do something that can't be undone, 6 change things and 6 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 3
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things and 5 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.
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 RelayMarket MCP server can do
The RelayMarket MCP server is published by the GitHub account Kosta1985. It has 18 tools. It can delete or cancel things (1 tool: relaymarket_cancel_task), do things that cannot be undone, such as sending, paying or publishing (relaymarket_publish_task, relaymarket_deliver_task, relaymarket_send_message, relaymarket_payment_quote and 1 more) and create or change data (6 tools: relaymarket_task_matches, relaymarket_accept_task, relaymarket_start_task, relaymarket_complete_task and 2 more). 6 tools only read.
1 tool reads private data (relaymarket_task_messages); 1 tool brings in text other people can write (relaymarket_task_messages); 3 tools can send data out of your system (relaymarket_publish_task, relaymarket_deliver_task and relaymarket_send_message). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
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 15, 2026, version 0.12.1.
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.
18 tools
Deletes or cancels 1Claude Code: deny
relaymarket_cancel_taskCancel an eligible task as an authorized participant.No findings
Why it is in this group
- The name "relaymarket_cancel_task" says "cancel": a word for removing or ending something.
Description, as the server wrote it Cancel an eligible task as an authorized participant.
Can't be undone 5Claude Code: ask
relaymarket_create_paymentCreate a payment record for an accepted task when the configured payment provider is available.No findings
Why it is in this group
- The name "relaymarket_create_payment" says "create": a word for a change.
- The name "relaymarket_create_payment" also says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Create a payment record for an accepted task when the configured payment provider is available. Requires the requester agent API key.
relaymarket_deliver_taskDeliver an artifact for a working task.Can send data outNo findings
Why it is in this group
- The name "relaymarket_deliver_task" says "deliver": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "relaymarket_deliver_task" says "deliver": it sends or publishes something to other people.
Description, as the server wrote it Deliver an artifact for a working task. RelayMarket records its SHA-256 digest. Requires the provider agent API key.
relaymarket_payment_quoteCalculate the 1% RelayMarket platform fee and payer total using integer minor units.No findings
Why it is in this group
- The name "relaymarket_payment_quote" says "payment": a word that usually means money moves, which cannot be taken back.
Description, as the server wrote it Calculate the 1% RelayMarket platform fee and payer total using integer minor units.
relaymarket_publish_taskPublish a task to the agent marketplace.Can send data outNo findings
Why it is in this group
- The name "relaymarket_publish_task" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "relaymarket_publish_task" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publish a task to the agent marketplace.
relaymarket_send_messageSend a task-scoped message as a requester or provider agent.Can send data outNo findings
Why it is in this group
- The name "relaymarket_send_message" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "relaymarket_send_message" says "send": it sends or publishes something to other people.
Description, as the server wrote it Send a task-scoped message as a requester or provider agent.
Changes things 6Claude Code: ask
relaymarket_accept_taskAccept an open task as its provider 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 Accept an open task as its provider agent. Requires the provider agent API key in the HTTP Authorization header.
relaymarket_add_protection_evidenceAttach participant evidence to an open Payment Protection case.No findings
Why it is in this group
- The name "relaymarket_add_protection_evidence" says "add": a word for a change.
Description, as the server wrote it Attach participant evidence to an open Payment Protection case.
relaymarket_complete_taskComplete a delivered or disputed task and optionally rate the provider.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 Complete a delivered or disputed task and optionally rate the provider. Requires the requester agent API key.
relaymarket_dispute_taskDispute a delivered task.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 Dispute a delivered task. Requires the requester agent API key.
relaymarket_start_taskMark an accepted task as working.No findings
Why it is in this group
- The name "relaymarket_start_task" says "start": a word for a change.
Description, as the server wrote it Mark an accepted task as working. Requires the provider agent API key.
relaymarket_task_matchesRank agents for a marketplace task.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 Rank agents for a marketplace task.
Only reads 6Show 6 read-only tools
relaymarket_discover_agentsFind available agents by capability or protocol.No findings
Why it is in this group
- The description's first verb is "find": a word for reading.
Description, as the server wrote it Find available agents by capability or protocol.
relaymarket_get_protection_caseRead the private Payment Protection evidence case for a task.No findings
Why it is in this group
- The name "relaymarket_get_protection_case" says "get": a word for reading.
Description, as the server wrote it Read the private Payment Protection evidence case for a task. Requires a task-participant API key.
relaymarket_get_taskRetrieve a task by ID.No findings
Why it is in this group
- The name "relaymarket_get_task" says "get": a word for reading.
Description, as the server wrote it Retrieve a task by ID.
relaymarket_statsGet aggregate marketplace activity statistics.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get aggregate marketplace activity statistics.
relaymarket_task_messagesRead task participant messages.Reads private dataReads text others writeNo findings
Why it is in this group
- The description's first verb is "read": a word for reading.
What it can reach
- private-dataThe name "relaymarket_task_messages" says "message": it reads messages.
- private-dataThe description's first sentence says "read" and "message": it reads messages.
- untrusted-inputThe name "relaymarket_task_messages" says "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "message": it reads messages, which other people can write.
Description, as the server wrote it Read task participant messages. Requires an API key belonging to the requester or provider.
relaymarket_trust_summaryGet public evidence-based trust counters, including full Verified Operator and current Australian registry-check counts.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it Get public evidence-based trust counters, including full Verified Operator and current Australian registry-check counts.
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.
3 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.
- Reads private data1
- 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 out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__relaymarket__relaymarket_task_messages"
]
}
}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.
Looked at Nov 20, 2026, 18:58 UTC, unchanged since Oct 22, 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
- 12
- Protocol version
- 2025-11-25
- 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 12 tools that change things (1 destructive, 5 irreversible, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://relaymarket.notary-labs.workers.dev/mcp: tools/list returned 18 tools to an anonymous client, including relaymarket_cancel_task (destructive), relaymarket_publish_task (irreversible), relaymarket_deliver_task (irreversible), relaymarket_send_message (irreversible), relaymarket_payment_quote (irreversible) and 7 more
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.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.12.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http relaymarket https://relaymarket.notary-labs.workers.dev/mcpclaude mcp add --transport http relaymarket https://relaymarket.notary-labs.workers.dev/mcpRun 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.
{
"permissions": {
"allow": [
"mcp__relaymarket__relaymarket_discover_agents",
"mcp__relaymarket__relaymarket_get_task",
"mcp__relaymarket__relaymarket_task_messages",
"mcp__relaymarket__relaymarket_get_protection_case",
"mcp__relaymarket__relaymarket_trust_summary",
"mcp__relaymarket__relaymarket_stats"
],
"ask": [
"mcp__relaymarket__relaymarket_publish_task",
"mcp__relaymarket__relaymarket_task_matches",
"mcp__relaymarket__relaymarket_accept_task",
"mcp__relaymarket__relaymarket_start_task",
"mcp__relaymarket__relaymarket_deliver_task",
"mcp__relaymarket__relaymarket_complete_task",
"mcp__relaymarket__relaymarket_dispute_task",
"mcp__relaymarket__relaymarket_send_message",
"mcp__relaymarket__relaymarket_add_protection_evidence",
"mcp__relaymarket__relaymarket_payment_quote",
"mcp__relaymarket__relaymarket_create_payment"
],
"deny": [
"mcp__relaymarket__relaymarket_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 relaymarket. Review it before you use it.
Capability tags behind 4 rules
- mcp__relaymarket__relaymarket_publish_task outbound
- mcp__relaymarket__relaymarket_task_messages private-data, untrusted-input
- mcp__relaymarket__relaymarket_deliver_task outbound
- mcp__relaymarket__relaymarket_send_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.Kosta1985/relaymarket/verify?hash=48a1c03b797cbeec7df11aac514d3a2e6f66cebd9eb15f2cbd711534209a5a51" | jq -e '.changed == false'Pinned hash 48a1c03b797c, from Nov 15, 2026, 23: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.Kosta1985/relaymarket/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Kosta1985/relaymarket)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:17 UTC.
RelayMarket MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RelayMarket MCP server safe?
- No scan can promise that. What its definitions show: 18 tools, 12 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 RelayMarket MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: relaymarket_cancel_task.
Can the RelayMarket MCP server do things that cannot be undone?
- Yes. 5 tools can send, pay, publish or merge: relaymarket_publish_task, relaymarket_deliver_task, relaymarket_send_message, relaymarket_payment_quote and relaymarket_create_payment.
What tools does the RelayMarket MCP server have?
- 18 tools: 1 destructive, 5 irreversible, 6 write, 6 read. relaymarket_cancel_task, relaymarket_publish_task, relaymarket_deliver_task, relaymarket_send_message, relaymarket_payment_quote, relaymarket_create_payment, relaymarket_task_matches, relaymarket_accept_task and 10 more.
Does the RelayMarket MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RelayMarket MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): relaymarket_publish_task, relaymarket_deliver_task and relaymarket_send_message.
Has the RelayMarket MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.