Signal Desk by LarryBuildsAI
https://signal-desk-larrybuildsai.vercel.app/mcp ↗
Description
Signal Desk by LarryBuildsAI is a buyer-side routing preflight for x402 and MCP agent toolchains. It helps agents compare market tools, choose the next paid call, skip unnecessary spend, and generate public lead or risk briefs with claim-bounded outputs.
What our measurements say
Signal Desk by LarryBuildsAI is a remote MCP server published at signal-desk-larrybuildsai.vercel.app. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 895 ms, a delay an agent will notice. It offers a narrow, focused set of 6 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names use deterministic/action-based verbs (e.g., 'probe', 'generate', 'check') for clear intent.
- Descriptions emphasize auditability, readiness checks, and trust receipts for compliance.
- Most tools include optional parameters for flexibility without overcomplicating core functions.
Weaknesses
- Some tool descriptions (e.g., 'generate_x402_launch_pack') lack explicit use-case triggers for agent decision-making.
- Parameter definitions like 'expected_resources' and 'tier' are vague about required formats or constraints.
- Overlap between 'scan_x402_resource' and 'check_agent_tool_readiness' may confuse agents about distinct responsibilities.
generate_x402_launch_pack— Unclear when to use for launch-stage vs. ongoing compliancecheck_agent_tool_readiness— Ambiguous 'tier' parameter without defined enum valuesscan_x402_resource— Readiness scoring lacks explicit thresholds for actionabilityprobe_x402_paid_path— Payment metadata verification scope not clearly bounded
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from 'auth-gated' to 'legacy' · transition to legacy mode enabled compliance scoring
- 2026-09-11T09:28:19.138Z — complianceScore changed from null to 100 · system achieved full compliance validation
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 172ms → warm 155ms (penalty 17ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.1.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/larrybuildsai-signal-desk)<a href="https://mcpmetrics.io/servers/larrybuildsai-signal-desk"><img src="https://mcpmetrics.io/badge/larrybuildsai/signal-desk/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see