Is io.github.wilmendezofficial/postari 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.
| Endpoint | https://postari.io/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 card | Published, does not validate: an A2A 0.3 card: no `supportedInterfaces`, which 1.0 requires in place of `url` and `protocolVersion`. A2A 0.3 shape; 41 skills; JSONRPC./.well-known/agent-card.json |
|---|---|
| MCP server card (SEP-2127) | Not published (HTTP 404).https://postari.io/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 directory | Not published (HTTP 404)./.well-known/http-message-signatures-directory |
Read at https://postari.io 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 41 tools: account_stats, activate_flow, add_subscriber_to_list, arm_flow, clean_bounced_subscribers, create_flow, create_form, create_landing, create_launch, create_list, create_segment, create_subscriber, create_tag, create_template, diagnose_deliverability, get_agent_activity, get_campaign_audience, get_campaign_stats, get_form, get_launch, get_subscriber, launch_campaign, link_campaign_to_launch_stage, list_campaigns, list_flow_emails, list_forms, list_landings, list_launches, list_lists, list_subscribers, reactivate_bounced_subscriber, send_transactional_email, set_campaign_audience, tag_subscribers, test_flow, trigger_flow, update_flow, update_flow_email, update_form, update_landing, update_subscriber.
Its tools changed between 2026-09 and 2026-10:
- Added (4):
get_form,list_forms,list_subscribers,reactivate_bounced_subscriber account_stats: description changedclean_bounced_subscribers: description changeddiagnose_deliverability: description changedget_campaign_audience: description changedget_campaign_stats: description changedget_launch: description changedget_subscriber: description changedlaunch_campaign: input schema changedlist_campaigns: description changedlist_landings: description changedlist_lists: description changedsend_transactional_email: input schema changedupdate_subscriber: description changed
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 name | io.github.wilmendezofficial/postari |
|---|---|
| Endpoint | https://postari.io/api/mcp |
| Publisher repository | not 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