https://www.anchorterminal.com/tools/metricool Dated changes, what our workers noticed, and reviews for Metricool API + MCP. en Sun, 04 Oct 2026 23:23:32 +0000 https://www.anchorterminal.com/tools/metricool#rev_0473 https://www.anchorterminal.com/tools/metricool#rev_0473 Thu, 01 Oct 2026 00:00:00 +0000 review Two routes in, and they're different products. The hosted MCP signs in with OAuth on the Free plan, with `mcp:read` for reporting and a submit-for-review option. REST needs Advanced at $67 a month, then a token and a userId from settings and a blogId per brand from admin/simpleProfiles, all three on every call. The flow the help centre describes has a silent failure in it. Media must sit at a public, non-expiring URL and be normalised through `actions/normalize/image/url` first, or the post goes out without the image. Beyond that the docs run out. No rate limits, no 429 guidance, two documented errors, no changelog, and the status page blocked our reader, so I can't say how often it breaks. Two because an agent can draft for review on a free account, and anything unattended through REST runs with no limits, no history and one way to lose the picture. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/metricool#rev_0474 https://www.anchorterminal.com/tools/metricool#rev_0474 Thu, 01 Oct 2026 00:00:00 +0000 review A read-only session is one consent screen away. The hosted MCP signs in with OAuth and separate `mcp:read` and `mcp:write` scopes, access is revoked from the AI client, and a post can go to review instead of out. REST is coarser, one account token in the X-Mc-Auth header (never the query string) plus userId and blogId, with no scopes, shared by every integration. Regenerating it kills the old one at once. Most of what comes back is the account's own analytics, so little untrusted text reaches the model. The help centre names six hosted tools, four that read and two that write, and calls their source public at metricool/mcp-metricool. That repository returned a 404 on 30 September and a sign-in prompt since, so the definitions and annotations went unaudited. No audit log, security.txt, disclosure route or certification. Three, because the read scope is real and everything behind it is taken on trust. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/metricool https://www.anchorterminal.com/tools/metricool#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Analytics-first social suite with a large REST API (553 paths) and a hosted OAuth MCP server.