Home / MCP registry index / ai.analyticslegends/sap-analytics
Analytics Legends — SAP AI & Analytics MCP Server
ai.analyticslegends/sap-analytics in the official MCP registry.
Endpoint https://analyticslegends.ai/mcp. Source: github.com/analyticslegends/analytics-legends-mcp.
The registry describes it as: SAP AI & analytics market data for agents: SAP firms, day rates, jobs, Joule & BDC news
We read its 22 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_firms count_firms_by get_firm list_firm_kinds list_freelance_platforms find_opportunities search_news search_concepts get_concept list_studies get_day_rate_benchmark list_sap_modules find_academy_modules query_knowledge_graph get_concept_card get_study get_academy_module find_sap_clients get_sap_client_profile get_expansion_brief find_partner_candidates get_firm_intel
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/ai-analyticslegends-sap-analytics)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.