io.github.Stakemate369/yieldsignal MCP server: daily status and tool changes

Did not answer as an MCP server on the last 5 consecutive daily checks (2026-10-31 to 2026-11-04). MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-29; no tool definition change in 1 compared days; no agent-reported interactions.

Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Stakemate369/yieldsignal

Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.Stakemate369/yieldsignal?menu=install-check · other questions: menu

Does it respond?

Latest daily check: 2026-11-04: the server did not answer as an MCP server.

Observed days in the last 30: 7
Answered initialize and tools/list: 2
Required authentication: 0
No response: 0
Remotes differed: 0

Does it require authentication?

It did not return HTTP 401/403 on any of the 7 observed days. Lowdown checks without credentials.

Did its tools change recently?

No change in tool schemas, descriptions or names across 1 compared days.

What tools does it list?

7 tools on 2026-10-30:

get_exit_capacity
get_leadership_persistence
get_rate_sensitivity
get_shared_exposure
get_yield_decision
get_yield_durability
get_yield_signal

MCP Registry declaration

Registry name: io.github.Stakemate369/yieldsignal
Declared version: 1.2.0
Status: active
Declared hosts: yieldsignal.vercel.app