ai.mcpanalytics/analytics
REMOTE · API.MCPANALYTICS.AI · 2 COMPONENTS · SCANNED AUG 3
The statistical analyst in your AI chat — validated, citable, re-runnable analysis of your data.
Available components
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. How we score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1278 tokens (~85/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.mcpanalytics.ai
claude mcp add --transport http ai-mcpanalytics-analytics https://api.mcpanalytics.ai/mcp/api-key
[mcp_servers.ai-mcpanalytics-analytics] url = "https://api.mcpanalytics.ai/mcp/api-key"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-mcpanalytics-analytics": {
"type": "remote",
"url": "https://api.mcpanalytics.ai/mcp/api-key",
"enabled": true
}
}
} openclaw mcp add ai-mcpanalytics-analytics --url https://api.mcpanalytics.ai/mcp/api-key --transport streamable-http
mcp_servers:
ai-mcpanalytics-analytics:
url: "https://api.mcpanalytics.ai/mcp/api-key" {
"mcpServers": {
"ai-mcpanalytics-analytics": {
"type": "http",
"url": "https://api.mcpanalytics.ai/mcp/api-key"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 3 Aug 2026 · Probed https://api.mcpanalytics.ai/mcp/api-key
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpanalytics.ai | CN=WE1,O=Google Trust Services,C=US | 13 Jun 2026 | 11 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 5872c0f6488fa1bd135aada9c929ae06 |
| SANs: mcpanalytics.ai, *.mcpanalytics.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.mcpanalytics.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| mcpanalytics.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge API-Key realm="https://api.mcpanalytics.ai"
API-Key realm="https://api.mcpanalytics.ai" | Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcpanalytics.ai/mcp/api-key | Verified | 200 | |
| http (plaintext) | http://api.mcpanalytics.ai/mcp/api-key | HTTPS enforced | 301 | https://api.mcpanalytics.ai/mcp/api-key |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
about ~39
Platform documentation and info — how it works, tiers, usage.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Topic: platform, manual, connectors, or a docs section |
No output schema declared.
No examples provided.
account_link ~51
Direct link to the right account page for anything not doable in chat — billing, browser upload, report management. Hand the user the link and guide them.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | — | Where to send the user |
No output schema declared.
No examples provided.
agent_advisor ~39
AI help desk — which analysis fits your question, interpreting results, fixing errors. Multi-turn.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | Your question or request |
No output schema declared.
No examples provided.
ask_library ~42
Ask a question across all your delivered analyses — synthesized answer with citations back to specific reports.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | Plain-language question to answer from your report library |
No output schema declared.
No examples provided.
build_status ~65
Check a commissioned build in-chat: stage progress, queue position, rejection reason if the data didn't match the objective, honest ETA, report link when delivered.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_id | integer | — | pipeline_id from create_analysis |
| track_token | string | — | Token from the tracking URL |
No output schema declared.
No examples provided.
create_analysis ~282
Commission a NEW analysis built for your question. tier is REQUIRED — the user picks. Easiest: fuzzy_request (plain language) + dataset_ref + tier. Snapshot = instant automated report (~2-10 min). JSON = a fast computed answer, numbers + method, re-runnable tool you own (~5 min). Brief = the computed answer on a one-page report — chart, numbers, method (~7 min). Deck = commissioned deep analysis, a durable re-runnable module you own (30-45 min). Failed builds are never billed.
| Name | Type | Req | Description |
|---|---|---|---|
| column_mapping | object | — | Optional semantic-to-real column map (hint only) |
| dataset_ref | string | — | Single-dataset URI: 'uuid://UUID:KEY' |
| datasets_refs | object | — | Multi-dataset URIs keyed by role |
| fuzzy_request | string | — | Plain-language description of the analysis you want |
| notes | string | — | Optional context for the build — constraints, definitions, or preferences the analyst agents should honor |
| specification | object | — | Full 11-field spec (legacy path — prefer fuzzy_request) |
| tier | string | — | snapshot = instant report (~2-10 min); json = fast computed answer (~5 min, default); brief = one-page report of the answer (~7 min); deck = commissioned re-runnable module (30-45 min) |
No output schema declared.
No examples provided.
datasets_list ~65
List and search your uploaded datasets — fuzzy matching on name, description, and tags. Returns each dataset's uuid:// reference for use in create_analysis and run_analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max results |
| search | string | — | Search by name, description, or tags |
No output schema declared.
No examples provided.
datasets_upload ~87
Get your data in. Pass `data` as an array of row objects to create the dataset immediately and get a dataset_ref ready for create_analysis; omit it to get an upload link for a file only the user can reach.
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | — | Rows as an array of flat objects — creates the dataset in one call |
| expires_in | integer | — | Token expiration in seconds |
No output schema declared.
No examples provided.
discover_tools ~85
Browse the analyses you can run — the ones you commissioned plus the platform Standard Library (prebuilt tools; each result tagged source:'own' or 'standard_library'). Plain-language match; no query lists everything, your own first. Nothing fits? Commission it with create_analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | — | Plain-language search over your library + the Standard Library; omit to list everything |
No output schema declared.
No examples provided.
modify_analysis ~156
Modify an EXISTING analysis into a new version — reword the question, swap the method, or add a variable. Pass tool_name + changes (plain language). Rebuilds on the analysis's own dataset by default; the original stays put. Returns pipeline tracking — follow with build_status.
| Name | Type | Req | Description |
|---|---|---|---|
| changes | string | yes | What to change, in plain language, e.g. 'also break it down by region' or 'use a random forest instead' |
| dataset_ref | string | — | Optional — rebuild against a different dataset ('uuid://UUID:KEY') |
| tier | string | — | Optional — change the depth of the new version |
| tool_name | string | yes | The analysis to modify (from discover_tools or your library) |
No output schema declared.
No examples provided.
report_cards ~47
Browse a delivered report's individual cards (charts, tables, insights) inline in chat.
| Name | Type | Req | Description |
|---|---|---|---|
| processing_id | string | yes | The report's processing id, returned by run_analysis or build_status |
No output schema declared.
No examples provided.
reports_list ~57
Your report library — every analysis delivered, with status and links. Pass semantic_query to search report content in plain language.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | — | Max results |
| semantic_query | string | — | Natural-language search over your reports' content |
No output schema declared.
No examples provided.
reports_view ~39
Get a shareable browser link for a report — viewable without authentication.
| Name | Type | Req | Description |
|---|---|---|---|
| processing_id | string | yes | Processing ID from run_analysis / reports_list |
No output schema declared.
No examples provided.
run_analysis ~69
Run an analysis on your data. Returns a shareable interactive report URL — validated statistics you can cite, re-run, and share.
| Name | Type | Req | Description |
|---|---|---|---|
| taskList | object | yes | Execution inputs. Call tools_schema first for the analysis-specific fields. |
| tool_name | string | yes | Name of the analysis to run |
No output schema declared.
No examples provided.
tools_schema ~33
Get an analysis's parameter schema — ALWAYS call before run_analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| tool_name | string | yes | Name of the analysis |
No output schema declared.
No examples provided.