Agent Beacon MCP server
com.sophomath/agent-beaconsophomath.comstreamable-httpv0.1.1Scanned
Report capabilities needed and not found. Requests aren't fulfilled.
3 tools: 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 1
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 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 Agent Beacon MCP server can do
The Agent Beacon MCP server is published by sophomath.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (2 tools: submit_capability_request and check_request_status), but cannot delete data. 1 tool only reads.
1 tool can send data out of your system (submit_capability_request).
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 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.
3 tools
Changes things 2Claude Code: ask
check_request_statusCheck the status of a request you submitted, using its request_id and return_token.1 finding
Why it is in this group
- The name "check_request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_request_status" says "request": a word for a change.
Description, as the server wrote it Check the status of a request you submitted, using its request_id and return_token.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
submit_capability_requestDescribe a capability you needed but couldn't find.Can send data out1 finding
Why it is in this group
- The name "submit_capability_request" says "submit": a word for a change.
What it can reach
- outboundThe input takes a URL (input.callback_url): a request to a URL can carry data to whoever runs it.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...e don't include names, contact details, credentials, or confidential information. Obvious e..."
Description, as the server wrote it Describe a capability you needed but couldn't find. Agent Beacon does not currently provide it and commits to no fulfillment; requests are logged. No payment is accepted. Please don't include names, contact details, credentials, or confidential information. Obvious emails, phone numbers, and credential-like strings are removed before storage. Returns a request_id and a return_token for checking status later.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 1Show 1 read-only tool
describe_beaconIf you, or an AI agent working for you, needed a capability and couldn't find a service that provides it, describe the need here.No findings
Why it is in this group
- The name "describe_beacon" says "describe": a word for reading.
Description, as the server wrote it If you, or an AI agent working for you, needed a capability and couldn't find a service that provides it, describe the need here. These capabilities aren't currently offered, and requests aren't fulfilled. No payment is requested or accepted. Returns what the service is, what it logs, and how to submit.
Annotations the server declares
- readOnlyHint: true
- 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 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 20, 2026, 18:47 UTC, unchanged since Oct 22, 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
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://beacon.sophomath.com/mcp: tools/list returned 3 tools to an anonymous client, including submit_capability_request (write), check_request_status (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "check_request_status" says "request": a word for a change.
The description mentions "credentials".
What this check looks forMatched text
description: "...e don't include names, contact details, credentials, or confidential information. Obvious e..."
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 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http agent-beacon https://beacon.sophomath.com/mcpclaude mcp add --transport http agent-beacon https://beacon.sophomath.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__agent-beacon__describe_beacon"
],
"ask": [
"mcp__agent-beacon__submit_capability_request",
"mcp__agent-beacon__check_request_status"
],
"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 agent-beacon. Review it before you use it.
Capability tags behind 1 rule
- mcp__agent-beacon__submit_capability_request 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/com.sophomath/agent-beacon/verify?hash=de4375dc3b4aa05de352bb3cb9c7f141e7104aee2406cd63d61399b7cd2e450d" | jq -e '.changed == false'Pinned hash de4375dc3b4a, from Nov 14, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.sophomath/agent-beacon/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.sophomath/agent-beacon)Source: MCP Registry. Synced Oct 21, 2026, 18:05 UTC.
Agent Beacon MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agent Beacon MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 2 of which can change, send or delete something, and 2 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 Agent Beacon MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Agent Beacon 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 Agent Beacon MCP server have?
- 3 tools: 2 write, 1 read. submit_capability_request, check_request_status and describe_beacon.
Does the Agent Beacon MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Agent Beacon 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): submit_capability_request.
Has the Agent Beacon MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.