relayted API MCP server
de.relayted/apirelayted.destreamable-httpv1.0.0Scanned
Screenshots in real browsers, web page to Markdown or PDF, Nostr relay tests. Prepaid per request.
5 tools: 5 change things.
- Reads private data · 0
- Reads text others write · 4
- Can send data out · 3
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. 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 relayted API MCP server can do
The relayted API MCP server is published by relayted.de, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: shot, markdown, pdf, relay_check and 1 more), but cannot delete data. None of its tools only reads.
4 tools bring in text other people can write (shot, markdown, pdf and 1 more); 3 tools can send data out of your system (shot, markdown and pdf).
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 9, 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.
5 tools
Changes things 5Claude Code: ask
balanceCurrent balance of the wallet behind the API key (Payloads and EUR) and where to top up.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.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Current balance of the wallet behind the API key (Payloads and EUR) and where to top up. Free.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
markdownFetch a public web page and return its main content as Markdown (inline text).Reads text others writeCan send data out1 finding
Why it is in this group
- The description's first verb is "fetch": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- untrusted-inputThe description's first sentence says "fetch" and "web": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Findings
- Warn
The server marks "markdown" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "fetch": a word for reading.
Description, as the server wrote it Fetch a public web page and return its main content as Markdown (inline text). Costs 45 Payloads (0.0045 EUR) per page.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
pdfRender a public web page to PDF (Chromium).Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Render a public web page to PDF (Chromium). Returns the PDF inline (base64, up to 4 MB) and a download link. Costs 150 Payloads (0.015 EUR) per page.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
relay_checkTest a public Nostr relay.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Test a public Nostr relay. mode "quick" (default, 200 Payloads = 0.02 EUR): DNS, TLS, WebSocket, NIP-11, publish/query, latency, stability. mode "conformance" (800 Payloads = 0.08 EUR): NIP-01, filters, event semantics, limits. Returns the JSON report inline (per check: pass, fail, warn, skip, info). A relay can be tested only a few times per hour.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
shotTake screenshots of a public web page in real browser engines (default: newest Chrome, 1920x1080, light scheme).Reads text others writeCan send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Take screenshots of a public web page in real browser engines (default: newest Chrome, 1920x1080, light scheme). Returns the images inline (PNG) plus download links. Costs 65 Payloads (0.0065 EUR) per screenshot = browser version x viewport x colour scheme, 40 from the 13th screenshot of one job. Browser ids and viewport presets: GET https://api.relayted.de/v1/services/shots.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
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 write4
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
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 17, 2026, 15:21 UTC, unchanged since Nov 10, 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
- 5
- 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.relayted.de/mcp: tools/list returned 5 tools to an anonymous client, including shot (write), markdown (write), pdf (write), relay_check (write), balance (write)
Findings
Matches of fixed checks, with the text they matched.
- Warnmarkdown
The server marks "markdown" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "fetch": a word for reading.
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 api https://api.relayted.de/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http api https://api.relayted.de/mcp --header 'Authorization: <your-authorization>'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.
{
"permissions": {
"allow": [],
"ask": [
"mcp__api__shot",
"mcp__api__markdown",
"mcp__api__pdf",
"mcp__api__relay_check",
"mcp__api__balance"
],
"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 api. Review it before you use it.
Capability tags behind 4 rules
- mcp__api__shot untrusted-input, outbound
- mcp__api__markdown untrusted-input, outbound
- mcp__api__pdf untrusted-input, outbound
- mcp__api__relay_check untrusted-input
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/de.relayted/api/verify?hash=a0bdbacd0c9ceeee9bda260d41c7e9e6086f8316e7a747546311ac05da59de02" | jq -e '.changed == false'Pinned hash a0bdbacd0c9c, from Nov 9, 2026, 13:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/de.relayted/api/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/de.relayted/api)Source: MCP Registry. Synced Nov 9, 2026, 13:17 UTC.
relayted API MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the relayted API MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the relayted API MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the relayted API MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the relayted API MCP server have?
- 5 tools: 5 write. shot, markdown, pdf, relay_check and balance.
Does the relayted API MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the relayted API 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): shot, markdown and pdf.
Has the relayted API MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.