RWA Leads MCP server
com.rwaleads/rwa-leadsrwaleads.comstreamable-httpv2.4.0Scanned
Scored RWA, tokenization and family-office intent signals with source URLs. x402 pay-per-call.
2 tools: 2 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- 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 RWA Leads MCP server can do
The RWA Leads MCP server is published by rwaleads.com, a domain the MCP Registry verified. It has 2 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (get_signal_brief).
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 11, 2026, version 2.4.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.
2 tools
Only reads 2Show 2 read-only tools
get_signal_briefOne signal in full: the factor-by-factor score breakdown, fit rationale, entity and source URL.Reads text others writeNo findings
Why it is in this group
- The name "get_signal_brief" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
Description, as the server wrote it One signal in full: the factor-by-factor score breakdown, fit rationale, entity and source URL. Pass the `id` from search_signals.
Annotations the server declares
- title: Get signal brief
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
search_signalsSearch the scored RWA / tokenization / family-office signal feed.No findings
Why it is in this group
- The name "search_signals" says "search": a word for reading.
Description, as the server wrote it Search the scored RWA / tokenization / family-office signal feed. All filters are optional and combine with AND. Returns signals with intent score (0–100), tier, region, entity, summary and source URL, plus total_matching.
Annotations the server declares
- title: Search signals
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
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 outbound.
- 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 out0
- 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 21, 2026, 19:22 UTC, unchanged since Nov 14, 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
- 0
- 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
Posture changes
- Nov 14, 2026
- HTTP status of an anonymous initialize: 402 to 200
- tools/list served without credentials: no to yes
- Protocol version: none to 2025-06-18
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.
PostureRemote posture changed. HTTP status of an anonymous initialize: 402 -> 200; tools/list served without credentials: no -> yes; Protocol version: none -> 2025-06-18.View diff
- HTTP status of an anonymous initialize: 402 to 200
- tools/list served without credentials: no to yes
- Protocol version: none to 2025-06-18
Install
Pinned to version 2.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http rwa-leads https://rwaleads.com/api/mcpclaude mcp add --transport http rwa-leads https://rwaleads.com/api/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__rwa-leads__search_signals",
"mcp__rwa-leads__get_signal_brief"
],
"ask": [],
"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 rwa-leads. Review it before you use it.
Capability tags behind 1 rule
- mcp__rwa-leads__get_signal_brief 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/com.rwaleads/rwa-leads/verify?hash=b50952505da932e242f8c11021e538d7a08cd62f641398bdd552f17eee110ea2" | jq -e '.changed == false'Pinned hash b50952505da9, from Nov 11, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.rwaleads/rwa-leads/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.rwaleads/rwa-leads)Source: MCP Registry. Synced Nov 11, 2026, 22:17 UTC.
RWA Leads MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RWA Leads MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the RWA Leads MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RWA Leads 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 RWA Leads MCP server have?
- 2 tools: 2 read. search_signals and get_signal_brief.
Does the RWA Leads MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RWA Leads MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the RWA Leads MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.