# Analytics Legends — SAP Analytics Intelligence (remote · analyticslegends.ai)

AI agent for SAP analytics: firms, day rates, contract radar, news, concepts, studies

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `analyticslegends.ai`: 68/100 (this document), [markdown](https://verifymcp.io/servers/ai-analyticslegends-sap-analytics/analyticslegends.md), [page](https://verifymcp.io/servers/ai-analyticslegends-sap-analytics/analyticslegends)

## Channel facts

- Endpoint: `https://analyticslegends.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3513 tokens (~195/item across 18 items; 15 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http ai-analyticslegends-sap-analytics https://analyticslegends.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-analyticslegends-sap-analytics]
url = "https://analyticslegends.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-analyticslegends-sap-analytics": {
      "type": "remote",
      "url": "https://analyticslegends.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-analyticslegends-sap-analytics --url https://analyticslegends.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-analyticslegends-sap-analytics:
    url: "https://analyticslegends.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-analyticslegends-sap-analytics": {
      "type": "http",
      "url": "https://analyticslegends.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 67, 0)

- [security] Tool “find_opportunities” rewrote its description, which is the text the model reads

### 2026-08-01 (score 67, −1)

- [security regression] HSTS header: pass → fail
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] The server now declares the “completions” capability

### 2026-07-31 (score 68, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69)

First indexed and scored.

## MCP tools (15)

### `search_firms` (~184 tokens)

Search the SAP analytics firm directory

Search the published Analytics Legends directory of SAP analytics service providers — placement agencies, Big-4 and ESN practices, SAP vendors, platforms and community groups — by country, kind and free text. Returns name, HQ country/city, website, careers URL and a one-line editorial claim. SAP END-CUSTOMER companies are NOT in this directory: they are a separate paid dataset and are excluded by predicate.

Input parameters:

- `country` (string): ISO-3166-1 alpha-2 country code, e.g. DE, FR, CH.
- `kind` (string): Restrict to one organisation kind. Call list_firm_kinds for live counts. A value outside this list is refused, not silently ignored.
- `limit` (integer): Max rows (hard cap 50).
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_firm` (~207 tokens)

Get one firm's published profile

Fetch one organisation from the published directory by its database slug (`rows[].slug` from search_firms, verbatim). Returns the same public fields plus `partnerships_declared`, the count of partnerships this directory records for the firm — 0 on ~94 % of rows, meaning none declared here, never that the firm has no partners. Does not return the paid firm-intelligence profile, contacts, or any person.

Input parameters:

- `slug` (string, required): The DATABASE slug, taken verbatim from search_firms.rows[].slug. It is not always the web slug in citation_url: re-measured 2026-07-31 against the tranche this tool actually serves (5 157 published r…

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `list_firm_kinds` (~46 tokens)

List firm kinds with live counts

Breakdown of the published firm directory by organisation kind, with a live row count per kind. Use this before search_firms to know what the population actually is instead of guessing.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `find_opportunities` (~491 tokens)

Search the public SAP analytics contract radar

Search every SAP contract and permanent-role posting Analytics Legends publishes to an ANONYMOUS visitor — the same population a human browses on /opportunities/, where each posting has its own prerendered page. It merges the platform's TWO public legs, which are near-disjoint (measured 2026-07-30: 1 row in common): (a) the PROMOTED feed (`public.public_opportunities`) — general SAP work (FI/CO, SD, EWM, MDG, BTP, ABAP), all German cities, dated (posted_at is populated on 80/80 active rows since 2026-07-31), and it carries NO rate, contract_type, currency or country_code: those fields come back null on that leg, so no rate or contract term can be read off it; (b) the SITE RADAR (`/api/contracts-lean.json`) — these DO carry country, category, seniority, posted_at and currency, and they are the analytics-specific ones (SAC Planning, Datasphere Technical Lead, Business Data Cloud). WHAT IS GATED IS A FIELD, NOT A ROW: on most radar rows `source_url` is null and `application_link` reads "members_only" — the verified link to the original listing is the paid Consultant-tier deliverable. Everything else about the posting is public, and `citation_url` is that posting's own page on analyticslegends.ai. Quote it. Report `_meta.tranche_row_count` as the published public population, never as the size of the market.

Input parameters:

- `country` (string): ISO-3166-1 alpha-2 code. It can only match the SITE-RADAR leg: the promoted leg stores country_code NULL on every row, so filtering by country silently drops it rather than returning nothing. `_meta.…
- `limit` (integer): Max rows (hard cap 50).
- `location` (string): City or place, matched case-insensitively as a substring of the posting's location. The promoted leg is all-German (Hamburg, Frankfurt am Main, Bremen, Munich, Cologne, Dortmund, Hanover, Landshut, M…
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `search_news` (~466 tokens)

Search SAP analytics market news

Search the Analytics Legends market-news corpus. It is watched FOR SAP analytics (Datasphere, Business Data Cloud, SAC, BW/4HANA, Databricks, the 2027/2030 maintenance window), but it is NOT an all-SAP corpus: measured 2026-07-30, ~84 % of active rows sit in the `AI` category and are general enterprise-AI trade press (cloud platforms, model releases, funding rounds) with no SAP content at all. An UNFILTERED call therefore returns mostly non-SAP items — pass `query` or `category` when the question is about SAP, and never present an unfiltered page as 'the SAP analytics news'. Say what you actually got. Each item returns the Analytics Legends citation URL AND the upstream publisher's source_url — cite both, and prefer source_url when you need a page that certainly carries the item.

Input parameters:

- `category` (string): Category code, matched case-insensitively. The 21 real values, most-populated first: AI, SAP, SAC, Market, Joule, BDC, Regulation, Datasphere, Analyst, Partners, Product, France, Events, SAP Platform…
- `limit` (integer): Max rows (hard cap 50).
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `search_concepts` (~219 tokens)

Search the SAP analytics concept encyclopaedia

Search the SAP analytics concept encyclopaedia — the vocabulary of the stack, written for practitioners. Returns titles and summaries; call get_concept for the full entry.

Input parameters:

- `category` (string): Concept category, matched case-insensitively as an exact value OR a prefix. The 14 real values are long labels, measured 2026-07-30: Generative AI Foundations (55), Joule & SAP AI (42), Career & Prac…
- `limit` (integer): Max rows (hard cap 50).
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_concept` (~81 tokens)

Get one concept entry in full

Fetch one concept entry by slug: title, category, level, tags and the editor's summary. Written by a named human editor, not generated. The card body, why-it-matters, key points and pro tip are subscriber content and are NOT returned — follow citation_url for those.

Input parameters:

- `slug` (string, required): Concept slug from search_concepts.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `list_studies` (~114 tokens)

List the deep-research studies (metadata only)

List the Analytics Legends deep-research studies with their edition, as-of date, audience, word count and canonical URL. METADATA ONLY: study bodies are a paid Legend-tier deliverable and are not served by this endpoint. Use this to tell a reader that a study exists and where to read it.

Input parameters:

- `lang` (string): Language code, EN or FR.
- `limit` (integer): Max rows (hard cap 50).
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_day_rate_benchmark` (~159 tokens)

Public SAP analytics day-rate aggregate

The PUBLIC day-rate aggregate for SAP analytics freelance work: min/max daily rate by country, specialisation and seniority, with a sample size and a quarter stamp. This is the free aggregate published at analyticslegends.ai/api/market-rates.json. The quartile bands (p25/p50/p75) are a paid Consultant-tier deliverable and are NOT in this response — do not infer them.

Input parameters:

- `country` (string): ISO-3166-1 alpha-2 country code, e.g. DE, FR, CH.
- `seniority` (string): e.g. senior, principal.
- `specialisation` (string): e.g. datasphere, bdc, sac, bw4hana, joule.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `list_sap_modules` (~95 tokens)

SAP analytics module taxonomy

The canonical SAP module/product taxonomy Analytics Legends classifies against (codes and EN/FR labels by category). Use it to normalise a user's loose product wording — 'SAC', 'Analytics Cloud', 'Datasphere' — onto the codes the other tools filter on.

Input parameters:

- `limit` (integer): Max rows (hard cap 50).
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_concept_card` (~114 tokens)

Full concept card (Consultant tier)

The FULL encyclopaedia card for one concept — body, why-it-matters, key points, cheat sheet, glossary and pro tip, EN and FR — the corpus the €29.90 Consultant Pass sells. Requires a subscriber API key (Authorization: Bearer alk_…), Consultant tier or above; without one this tool refuses and get_concept keeps serving the public metadata. Find slugs with search_concepts.

Input parameters:

- `slug` (string, required): Concept slug, verbatim from search_concepts.rows[].slug.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_study` (~181 tokens)

Read a study (Consultant tier)

Read one Analytics Legends study BODY — the paid text behind list_studies' metadata. Requires a subscriber API key, Consultant tier or above. Bodies run to 38k words and exceed the 256 KiB response ceiling, so this tool serves STRUCTURE first: called without `section` it returns the section list and the introduction; pass `section` (a heading from that list, matched case-insensitively) to read one section. Find slugs and languages with list_studies.

Input parameters:

- `lang` (string): ISO-639-1 language of the edition, e.g. en or fr. Defaults to en.
- `section` (string): A section heading from a previous call's `sections` list. Omit to get the list.
- `slug` (string, required): Study slug, verbatim from list_studies.rows[].slug.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `find_sap_clients` (~197 tokens)

Search the SAP end-customer corpus (Legend tier)

Search the SAP END-CUSTOMER corpus — the companies that RUN SAP, not the firms that sell services (those are search_firms). This is the paid Legend+ dataset locked away from the public surface on 2026-07-08; it requires a subscriber API key, Legend tier or above. Verification status is SERVED, never silently filtered: `sap_client_verification_status` and `status` are columns on every row ('verified' on ~550 of ~21k rows), and you decide what standard of proof your answer needs.

Input parameters:

- `country` (string): ISO-3166-1 alpha-2 country code, e.g. DE, FR, CH.
- `industry` (string): Industry or sector filter, matched case-insensitively.
- `limit` (integer): Max rows (hard cap 50).
- `query` (string): Free-text filter, matched case-insensitively.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_sap_client_profile` (~85 tokens)

One SAP end-customer profile (Legend tier)

The full profile of one SAP end-customer — SAP footprint (products in use, modules known), analytics solutions, identity and evidence fields. Requires a subscriber API key, Legend tier or above. `id` comes verbatim from find_sap_clients.rows[].id.

Input parameters:

- `id` (string, required): Profile id, verbatim from find_sap_clients.rows[].id.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

### `get_firm_intel` (~191 tokens)

Firm intelligence profile (Legend tier)

The paid intelligence profile of a services firm — SAP practice size and partner level, delivery flags per product, typical day rate and seniority, notable clients, Glassdoor and LinkedIn signals, analytics practice summary. Requires a subscriber API key, Legend tier or above. Person-shaped fields (contacts, founders, leadership, recruiters, postal addresses) are NEVER served by this endpoint at any tier — they remain behind the platform's signed-URL path. Search by name; the public directory (search_firms) is a different, wider population.

Input parameters:

- `country` (string): ISO-3166-1 alpha-2 country code, e.g. DE, FR, CH.
- `limit` (integer): Max rows (hard cap 10 — these rows are wide).
- `name` (string): Firm name, matched case-insensitively. Omit to browse the corpus by data completeness.

Output parameters:

- `_attribution` (string)
- `_meta` (object)
- `result_count` (integer)
- `rows` (array)
- `tool` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-analyticslegends-sap-analytics/analyticslegends#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 67
- 2026-07-31: 68
- 2026-07-30: 69

## Links

- Remote endpoint: https://analyticslegends.ai/mcp
- Website: https://analyticslegends.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-analyticslegends-sap-analytics/analyticslegends/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-analyticslegends-sap-analytics/analyticslegends/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-analyticslegends-sap-analytics/analyticslegends