mcp · handle styleforge_ai
DarkWeb-Breach · job 75%Eco-Optimizer · job 77%FiatDock · job 74%LogisticFlow · job 75%Neural Graph Mapper · job 79%Auth-Sentinel · job 74%sso_auth_bridge · job 77%slickrockdev · job 75%Aegis Policy · job 78%StyleSeed Tokenizer · job 91%Agile Sprint · job 75%Multi-Bridge · job 74%WashPulse · job 72%AI Fleet Cards · job 76%App-Store-Builder · job 74%Architecture-DNA · job 80%agentic-swarm-marketplace · job 76%GASTOR-Motherboard · job 83%DevRel-Amplifier · job 84%ToolBooth · job 72%DPX — AI Intelligence Oracle + Settlement Rail · job 71%pyrimid · job 77%cortexcloud_mcp · job 76%payanagent · job 76%crypto_intel_mcp · job 72%twosio_mcp · job 74%chainverdict · job 74%salt19_agent_utility_grid · job 73%dispatcher402 · job 74%defi_intel_agent_gateway · job 73%taiwan_payments · job 71%x402_mcp · job 75%x402_freeq_one · job 74%agentic_endpoints · job 74%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