Machine Demand Radar Finder MCP server
io.github.gdangalov/machine-demand-radar-findergdangalovstreamable-httpv0.1.1Scanned
Find page-extraction tools. Free experiment with aggregate search counts and opt-in telemetry.
2 tools: 1 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
1 tool here changes things. 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 Machine Demand Radar Finder MCP server can do
The Machine Demand Radar Finder MCP server is published by the GitHub account gdangalov. It has 2 tools. It can create or change data (1 tool: record_finder_outcome), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in.
Last scanned Nov 9, 2026, version 0.1.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.
2 tools
Changes things 1Claude Code: ask
record_finder_outcomeReport selected_service, caller_declared_completion/failure or not_useful with a consented search_id; structured rejection_reason only.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 Report selected_service, caller_declared_completion/failure or not_useful with a consented search_id; structured rejection_reason only.
Only reads 1Show 1 read-only tool
find_agent_servicesFind page_extraction alternatives; structured format, JavaScript, auth and price constraints only.No findings
Why it is in this group
- The name "find_agent_services" says "find": a word for reading.
Description, as the server wrote it Find page_extraction alternatives; structured format, JavaScript, auth and price constraints only. No URL/task prompt. Consent defaults off.
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 or outbound.
- 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 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 19, 2026, 17:23 UTC, unchanged since Nov 19, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 403
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- no
- 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 asks for credentials (HTTP 403) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.
What this check looks forMatched text
https://eg7uwxidclcky7mtvo5mofuscy0cldzt.lambda-url.eu-central-1.on.aws/mcp: initialize answered HTTP 403, without a WWW-Authenticate header
Posture changes
- Nov 19, 2026
- HTTP status of an anonymous initialize: 200 to 403
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to no
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: 200 -> 403; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 2 more).View diff
- HTTP status of an anonymous initialize: 200 to 403
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to no
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http machine-demand-radar-finder https://eg7uwxidclcky7mtvo5mofuscy0cldzt.lambda-url.eu-central-1.on.aws/mcpclaude mcp add --transport http machine-demand-radar-finder https://eg7uwxidclcky7mtvo5mofuscy0cldzt.lambda-url.eu-central-1.on.aws/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__machine-demand-radar-finder__find_agent_services"
],
"ask": [
"mcp__machine-demand-radar-finder__record_finder_outcome"
],
"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 machine-demand-radar-finder. Review it before you use it.
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.gdangalov/machine-demand-radar-finder/verify?hash=022e81e8a5babab3c6c29be6aa43c973d33426ea6423ea2d69a127609df02e64" | jq -e '.changed == false'Pinned hash 022e81e8a5ba, from Nov 9, 2026, 21: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.gdangalov/machine-demand-radar-finder/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.gdangalov/machine-demand-radar-finder)Source: MCP Registry. Synced Nov 9, 2026, 21:18 UTC.
Machine Demand Radar Finder MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Machine Demand Radar Finder MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 1 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 Machine Demand Radar Finder MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Machine Demand Radar Finder 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 Machine Demand Radar Finder MCP server have?
- 2 tools: 1 write, 1 read. record_finder_outcome and find_agent_services.
Does the Machine Demand Radar Finder MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 403 without credentials, and no OAuth protected resource metadata was found.
Does the Machine Demand Radar Finder MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Machine Demand Radar Finder MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 9, 2026.