Mcp MCP Server

https://platform.aioproductos.com/api/mcp Remote v0.1.0

Published by platform.aioproductos.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

AIOProductOS spine over MCP — customers, revenue, feedback, work, analytics on one typed record.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([list_pages, get_page]) co-exist with external-action tools ([capture_insight]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [list_pages, get_page] → sinks [capture_insight]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow list_pages → capture_insight

Tools 71

Each tool and what it can reach — enumerated from the running server.

  • capture_insightnetwork egress
  • get_pageingests untrusted input
  • list_pagesingests untrusted input
  • add_noteno sensitive capability
  • analyze_funnelno sensitive capability
  • analyze_npsno sensitive capability
  • analyze_nrrno sensitive capability
  • analyze_pathsno sensitive capability
  • cancel_bookingno sensitive capability
  • comment_on_taskno sensitive capability
Show 61 more tools ↓
  • create_decisionno sensitive capability
  • create_experimentno sensitive capability
  • create_featureno sensitive capability
  • create_ideano sensitive capability
  • create_initiativeno sensitive capability
  • create_objectiveno sensitive capability
  • create_pageno sensitive capability
  • create_releaseno sensitive capability
  • create_sprintno sensitive capability
  • create_taskno sensitive capability
  • delete_taskno sensitive capability
  • get_codebase_mapno sensitive capability
  • get_conversationno sensitive capability
  • get_customer_360no sensitive capability
  • get_device_candidatesno sensitive capability
  • get_pm_playbookno sensitive capability
  • get_product_brainno sensitive capability
  • get_retentionno sensitive capability
  • get_roadmap_driftno sensitive capability
  • get_taskno sensitive capability
  • get_weekly_signal_memono sensitive capability
  • list_artifact_versionsno sensitive capability
  • list_bookingsno sensitive capability
  • list_channelsno sensitive capability
  • list_conversationsno sensitive capability
  • list_decisionsno sensitive capability
  • list_experimentsno sensitive capability
  • list_featuresno sensitive capability
  • list_ideasno sensitive capability
  • list_identity_mergesno sensitive capability
  • list_initiativesno sensitive capability
  • list_insightsno sensitive capability
  • list_objectivesno sensitive capability
  • list_releasesno sensitive capability
  • list_sprintsno sensitive capability
  • list_tasksno sensitive capability
  • merge_end_usersno sensitive capability
  • pm_metano sensitive capability
  • post_to_channelno sensitive capability
  • promote_ideano sensitive capability
  • read_channelno sensitive capability
  • reply_in_channelno sensitive capability
  • reply_to_conversationno sensitive capability
  • reschedule_bookingno sensitive capability
  • resolve_conversationno sensitive capability
  • revert_to_versionno sensitive capability
  • review_artifactno sensitive capability
  • unmerge_end_usersno sensitive capability
  • update_decisionno sensitive capability
  • update_experimentno sensitive capability
  • update_featureno sensitive capability
  • update_ideano sensitive capability
  • update_initiativeno sensitive capability
  • update_key_resultno sensitive capability
  • update_objectiveno sensitive capability
  • update_pageno sensitive capability
  • update_releaseno sensitive capability
  • update_sprintno sensitive capability
  • update_taskno sensitive capability
  • vote_ideano sensitive capability
  • whoamino sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.0 latest A 97/100 1 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/platform-aioproductos-com-api/badge.svg)](https://mcptrustchecker.com/registry/platform-aioproductos-com-api)
HTML
<a href="https://mcptrustchecker.com/registry/platform-aioproductos-com-api"><img src="https://mcptrustchecker.com/registry/platform-aioproductos-com-api/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/platform-aioproductos-com-api/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://platform.aioproductos.com/api/mcp --online

Use the free API → How scoring works

More in Analytics & Monitoring