Add AltoRank

[mikececco]

Adds tools/altorank.md (category marketing-seo) and the "altorank": "mikececco" submitter mapping.

AltoRank (https://github.com/AltoRank/altorank, AGPL-3.0) is open-source SEO content software with a hosted MCP server (https://app.altorank.co/api/mcp, Streamable HTTP + OAuth; co.altorank/altorank in the official MCP registry). Agents can run readiness audits, read stored Search Console data, research keywords and write drafts into a person's review queue; no tool approves or publishes.

Every claim is backed by a first-party evidenceSources item (docs, repository README, licence, pricing), all checked 2026-10-16. I left reviewedBy/reviewedAt and the logo/OG fields for the editorial review and enrichment.

npm run validate:content passes. npm test: 89/90 locally; the one failure is enrich-preflight.test.mjs calling mapfile, which macOS's bash 3 lacks (unrelated to this change).

Disclosure: I'm the founder of AltoRank.

🤖 Generated with Claude Code

[foo-bender]

Outcome: changes-requested

Policy assessment
@mikececco The agent-enabling classification and marketing-seo category fit: agents can audit sites, read Search Console, research keywords and create quota-bound drafts in a real content workflow. The repository is implementation source, not a README-only wrapper. Schema and field integrity otherwise pass, but tools/altorank.md needs a corrected capability boundary before acceptance.

1. limitationsMd says “No tool approves, publishes or deletes content.” Current docs list altorank_retry_publish; the skill permits it and the API route calls retryPublishCore and returns a published URL. It cannot approve or publish an unapproved draft, but it can retry a failed publication of a still-approved article through its existing connection. Please replace the absolute no-publishing claim with that precise human-approval boundary. This is a capability-description correction, not a claim that agents can bypass approval.
2. Qualify authentication by mode: the hosted endpoint accepts OAuth OR a raw bearer API key, while stdio readiness tools need no account. Avoid making OAuth sign-in the only supported authentication path.

Evidence checked
All four exact evidenceSources URLs were fetched and individually validated: https://altorank.co/docs/mcp/ ; https://github.com/AltoRank/altorank ; https://github.com/AltoRank/altorank/blob/main/LICENSE ; https://altorank.co/pricing/ . Cross-checked website, terms, AGPL package/source, Docker, skill and protocol surfaces; free self-hosting and EUR69/EUR199 monthly hosted plans/seven-day trial agree (annual billing, metered overages, VAT and trial payment-method terms are separate). The older v0.1.0 pre-launch release describes no publish tool/automatic publishing; it does not override the current main implementation and hosted docs. Please scope the corrected capability boundary to current channels rather than assuming older release notes establish current parity.

Contradicting implementation (source snapshot ec872fd6e09dc37e40aa045465da3504cc39ffe6): https://github.com/AltoRank/altorank/blob/ec872fd6e09dc37e40aa045465da3504cc39ffe6/apps/web/app/api/agent/v1/articles/%5Bid%5D/retry-publish/route.ts ; hosted auth: https://github.com/AltoRank/altorank/blob/ec872fd6e09dc37e40aa045465da3504cc39ffe6/apps/web/app/api/mcp/route.ts .

Checks run
Exact final head 27451aa, reconciled with current main e4cd7a5 in an isolated clone: npm run validate:content passed; npm test passed (90/90); git diff --check passed. Documentation/source review is not authenticated product execution or an independent security/performance benchmark.
No optional SEO evaluation or reviewer metadata commit was applied because the substantive capability description needs correction.