mcp · handle data_observability
DevDrops · job 81%DevRel-Amplifier · job 76%dominion-observatory · job 80%thousand_api · job 76%Query Forge · job 74%planetscale · job 79%pp_terminal · job 77%X-Social Intel · job 75%Auth-Sentinel · job 77%Eco-Optimizer · job 74%Signal Desk by LarryBuildsAI · job 77%cerbos_mcp · job 74%evalgate_mcp · job 81%aptabase_mcp · job 78%taskrail · job 77%calculator_mcp_server · job 75%mcp_mysql_server · job 74%sparks_re_api · job 75%joeroy2027_tqp_site · job 75%permitverdict · job 75%Strale · job 77%deskcrew_support · job 77%mssql_mcp_server · job 75%mcp_x402 · job 81%agentbits · job 79%salt19_agent_utility_grid · job 77%Satori-Aligner · job 78%hermes_plant · job 78%snipget · job 77%lastping · job 77%dxpert MCP · job 75%@cubiczan/chp-mcp · job 75%arithym · job 75%roundHR MCP · job 77%dynatrace_mcp_server · job 77%Neural Graph Mapper · job 76%App-Store-Builder · job 75%ontario_protocol · job 73%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series