RelayDataAI
REMOTE · RELAYDATAAI.COM
Discover structured products and services, or publish and maintain your own free listings.
Available components
Last scanned (22 hours ago)
Scores higher than 43% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 483 tokens (~69/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "publish_listing" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://relaydataai.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=relaydataai.com | CN=YR2,O=Let's Encrypt,C=US | 30 Oct 2026 | 28 Jan 2027 | RSA 2048 | SHA256-RSA | 5204b5cd7a94d5a91e41272c864b725f661 |
| SANs: relaydataai.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of relaydataai.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| relaydataai.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://relaydataai.com/mcp | Verified | 200 | |
| http (plaintext) | http://relaydataai.com/mcp | HTTPS enforced | 308 | https://relaydataai.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_category_schema ~31
Get category-specific fields before publishing or filtering. Missing facts must remain unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
No output schema declared.
No examples provided.
get_listing ~23
Read one public listing by stable ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_categories ~23
List all admitted sectors. Generic sectors are fully publishable and discoverable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_listings ~27
Read your listings including drafts and withdrawn entries. Requires an owner-authorised write API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
publish_listing ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attestRights | – | yes | – |
| attributes | object | – | – |
| category | string | yes | – |
| country | string | – | – |
| description | string | yes | – |
| languages | array | – | – |
| name | string | yes | – |
| status | – | – | – |
| summary | string | yes | – |
| tags | array | – | – |
| website | string | yes | – |
No output schema declared.
No examples provided.
search_listings ~81
Search public owner-declared and source-attributed imported products, services and providers. Results include provenance and confirmation dates; owner assertions are not independent verification.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | – | – |
| filters | object | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| q | string | – | – |
No output schema declared.
No examples provided.
update_listing ~124
Replace your listing using its current expectedVersion. Reconfirm only after checking the actual information. Do not refresh dates without an actual check.
| Name | Type | Req | Description |
|---|---|---|---|
| attestRights | – | yes | – |
| attributes | object | – | – |
| category | string | yes | – |
| country | string | – | – |
| description | string | yes | – |
| expectedVersion | integer | yes | – |
| id | string | yes | – |
| languages | array | – | – |
| name | string | yes | – |
| status | – | – | – |
| summary | string | yes | – |
| tags | array | – | – |
| website | string | yes | – |
No output schema declared.
No examples provided.
How do I install the RelayDataAI MCP server?
RelayDataAI is a hosted endpoint at https://relaydataai.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · relaydataai.com
claude mcp add --transport http monzncarlos-droid-relaydataai 'https://relaydataai.com/mcp'
What is the RelayDataAI MCP server?
RelayDataAI is an MCP server listed in the public MCP registry as io.github.monzncarlos-droid/relaydataai. Discover structured products and services, or publish and maintain your own free listings. This page covers its hosted endpoint (https://relaydataai.com/mcp).
Is the RelayDataAI MCP server safe to use?
RelayDataAI scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the RelayDataAI MCP server expose?
RelayDataAI exposes 7 tools: list_categories, get_category_schema, search_listings, get_listing, my_listings, and 2 more. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.
Does the RelayDataAI MCP server require authentication?
No. We connected to RelayDataAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the RelayDataAI MCP server still maintained?
RelayDataAI is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.