Agent Beacon
REMOTE · BEACON.SOPHOMATH.COM · SCANNED SEP 28
Report capabilities needed and not found. Requests aren't fulfilled.
Available components
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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
- Context-footprint check failed: tool/resource definitions use about 538 tokens (~179/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
How do I install the Agent Beacon MCP server?
Agent Beacon is a hosted endpoint at https://beacon.sophomath.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 · beacon.sophomath.com
claude mcp add --transport http com-sophomath-agent-beacon 'https://beacon.sophomath.com/mcp'
{
"mcpServers": {
"com-sophomath-agent-beacon": {
"url": "https://beacon.sophomath.com/mcp"
}
}
} {
"servers": {
"com-sophomath-agent-beacon": {
"type": "http",
"url": "https://beacon.sophomath.com/mcp"
}
}
} [mcp_servers.com-sophomath-agent-beacon] url = "https://beacon.sophomath.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-sophomath-agent-beacon": {
"type": "remote",
"url": "https://beacon.sophomath.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-sophomath-agent-beacon --url 'https://beacon.sophomath.com/mcp' --transport streamable-http
mcp_servers:
com-sophomath-agent-beacon:
url: "https://beacon.sophomath.com/mcp" {
"McpServers": {
"com-sophomath-agent-beacon": {
"Transport": "http",
"Url": "https://beacon.sophomath.com/mcp"
}
}
} assistant mcp add com-sophomath-agent-beacon -t streamable-http -u 'https://beacon.sophomath.com/mcp'
{
"mcpServers": {
"com-sophomath-agent-beacon": {
"type": "http",
"url": "https://beacon.sophomath.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +8
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Sept 26 56
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 28 Sept 2026 · Probed https://beacon.sophomath.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sophomath.com | CN=WE1,O=Google Trust Services,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | cb169e3324c3e8c70e19f7928fbf6e85 |
| SANs: sophomath.com, beacon.sophomath.com, *.beacon.sophomath.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of beacon.sophomath.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| sophomath.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://beacon.sophomath.com/mcp | Verified | 200 | |
| http (plaintext) | http://beacon.sophomath.com/mcp | Inconclusive | 405 |
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 →
check_request_status Check request status ~42
Check the status of a request you submitted, using its request_id and return_token.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| return_token | string | yes | – |
No output schema declared.
No examples provided.
describe_beacon Describe Agent Beacon ~70
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_capability_request Submit a capability request ~347
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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_type | string | – | Who is submitting. |
| alternatives_considered | array | – | Services, tools, or approaches you considered, and why each was rejected. |
| blocked_by | string | – | Why existing options were not good enough. |
| callback_url | string | – | Optional https URL. Stored only; never called. |
| capability_needed | string | yes | The capability you needed but couldn't find. |
| desired_output | string | – | What a useful result would look like. |
| frequency | string | – | How often this need occurs. |
| how_found | string | – | How you found Agent Beacon. |
| how_found_detail | string | – | Details, such as the search query, directory, or page. |
| inputs | string | – | What inputs you could provide. |
| latency_need | string | – | How quickly a result is needed. |
| max_price_usd | number | – | Most you would pay, in USD. |
| price_unit | string | – | Unit for max_price_usd. |
| runtime | string | – | Agent framework or client, if applicable. |
| spend_authority | string | – | Spending authority for this need, as you understand it. |
| task | string | yes | What you are trying to accomplish. |
| trust_requirements | string | – | Verification, provenance, or accountability the result needs. |
No output schema declared.
No examples provided.
What is the Agent Beacon MCP server?
Agent Beacon is an MCP server listed in the public MCP registry as com.sophomath/agent-beacon. Report capabilities needed and not found. Requests aren't fulfilled. This page covers its hosted endpoint (https://beacon.sophomath.com/mcp).
Is the Agent Beacon MCP server safe to use?
Agent Beacon scores 68 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 Agent Beacon MCP server expose?
Agent Beacon exposes 3 tools: describe_beacon, submit_capability_request, check_request_status. Their descriptions and schemas cost roughly 459 tokens of context every time the server is loaded.
Does the Agent Beacon MCP server require authentication?
No. We connected to Agent Beacon without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Beacon MCP server still maintained?
Agent Beacon is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.