RelayDataAI MCP server
io.github.monzncarlos-droid/relaydataaimonzncarlos-droidstreamable-httpv1.0.0Scanned
Discover structured products and services, or publish and maintain your own free listings.
7 tools: 1 do something that can't be undone, 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- 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 RelayDataAI MCP server can do
The RelayDataAI MCP server is published by the GitHub account monzncarlos-droid. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (publish_listing) and create or change data (1 tool: update_listing), but cannot delete data. 5 tools only read.
1 tool can send data out of your system (publish_listing).
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 16, 2026, version 1.0.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.
7 tools
Can't be undone 1Claude Code: ask
publish_listingPublish an offer on behalf of its owner.Can send data outNo findings
Why it is in this group
- The name "publish_listing" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "publish_listing" says "publish": it sends or publishes something to other people.
Description, as the server wrote it Publish an offer on behalf of its owner. Requires owner-authorised write API key and attestRights=true. Obtain the category schema first. Publication is free.
Changes things 1Claude Code: ask
update_listingReplace your listing using its current expectedVersion.No findings
Why it is in this group
- The name "update_listing" says "update": a word for a change.
Description, as the server wrote it Replace your listing using its current expectedVersion. Reconfirm only after checking the actual information. Do not refresh dates without an actual check.
Only reads 5Show 5 read-only tools
get_category_schemaGet category-specific fields before publishing or filtering.No findings
Why it is in this group
- The name "get_category_schema" says "get": a word for reading.
Description, as the server wrote it Get category-specific fields before publishing or filtering. Missing facts must remain unknown.
get_listingRead one public listing by stable ID.No findings
Why it is in this group
- The name "get_listing" says "get": a word for reading.
Description, as the server wrote it Read one public listing by stable ID.
list_categoriesList all admitted sectors.No findings
Why it is in this group
- The name "list_categories" says "list": a word for reading.
Description, as the server wrote it List all admitted sectors. Generic sectors are fully publishable and discoverable.
my_listingsRead your listings including drafts and withdrawn entries.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it Read your listings including drafts and withdrawn entries. Requires an owner-authorised write API key.
search_listingsSearch public owner-declared and source-attributed imported products, services and providers.No findings
Why it is in this group
- The name "search_listings" says "search": a word for reading.
Description, as the server wrote it Search public owner-declared and source-attributed imported products, services and providers. Results include provenance and confirmation dates; owner assertions are not independent verification.
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 or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- 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.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 4, 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
- 2
- 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 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://relaydataai.com/mcp: tools/list returned 7 tools to an anonymous client, including publish_listing (irreversible), update_listing (write)
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 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http relaydataai https://relaydataai.com/mcpclaude mcp add --transport http relaydataai https://relaydataai.com/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__relaydataai__list_categories",
"mcp__relaydataai__get_category_schema",
"mcp__relaydataai__search_listings",
"mcp__relaydataai__get_listing",
"mcp__relaydataai__my_listings"
],
"ask": [
"mcp__relaydataai__publish_listing",
"mcp__relaydataai__update_listing"
],
"deny": []
}
}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 relaydataai. Review it before you use it.
Capability tags behind 1 rule
- mcp__relaydataai__publish_listing 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.monzncarlos-droid/relaydataai/verify?hash=83a075029b94ee8a306c7190956f81e0b7c56228941857461f2f26a4b4e5ea77" | jq -e '.changed == false'Pinned hash 83a075029b94, from Nov 16, 2026, 20: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.monzncarlos-droid/relaydataai/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.monzncarlos-droid/relaydataai)Source: MCP Registry. Synced Nov 3, 2026, 09:17 UTC.
RelayDataAI MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RelayDataAI MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 2 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 RelayDataAI MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RelayDataAI MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: publish_listing.
What tools does the RelayDataAI MCP server have?
- 7 tools: 1 irreversible, 1 write, 5 read. publish_listing, update_listing, list_categories, get_category_schema, search_listings, get_listing and my_listings.
Does the RelayDataAI MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RelayDataAI MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): publish_listing.
Has the RelayDataAI MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 16, 2026.