Is com.aioproductos/mcp up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://platform.aioproductos.com/api/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://platform.aioproductos.com/api/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://platform.aioproductos.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 71 tools: add_note, analyze_funnel, analyze_nps, analyze_nrr, analyze_paths, cancel_booking, capture_insight, comment_on_task, create_decision, create_experiment, create_feature, create_idea, create_initiative, create_objective, create_page, create_release, create_sprint, create_task, delete_task, get_codebase_map, get_conversation, get_customer_360, get_device_candidates, get_page, get_pm_playbook, get_product_brain, get_retention, get_roadmap_drift, get_task, get_weekly_signal_memo, list_artifact_versions, list_bookings, list_channels, list_conversations, list_decisions, list_experiments, list_features, list_ideas, list_identity_merges, list_initiatives, list_insights, list_objectives, list_pages, list_releases, list_sprints, list_tasks, merge_end_users, pm_meta, post_to_channel, promote_idea, read_channel, reply_in_channel, reply_to_conversation, reschedule_booking, resolve_conversation, revert_to_version, review_artifact, unmerge_end_users, update_decision, update_experiment, update_feature, update_idea, update_initiative, update_key_result, update_objective, update_page, update_release, update_sprint, update_task, vote_idea, whoami.

No change to its tools between 2026-09 and 2026-10.

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry namecom.aioproductos/mcp
Endpointhttps://platform.aioproductos.com/api/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy