ToolsMCP
Argosor — Unified SEO, SERP, Clean Markdown & GEO (AI Citation Visibility) MCP Server
Listed in the official MCP Registry with a hosted streamable-http endpoint and an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- argosor.com
- Prerequisites
- An MCP client that supports streamable-http. The publisher declares a required credential header. Install argosor-mcp from npm (stdio transport). Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.0.1 · updated
- Official links
Publisher’s description
Unified 15-tool SEO, SERP, clean Markdown & GEO (LLM citation Share-of-Voice) MCP server.
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 1.0.1, registry status active. 2 remote endpoints (streamable-http); 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- argosor.com
- Version observed
- 1.0.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.argosor%2Fmcp/versions/1.0.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Search the web with sources | Publisher description mentions “serp”. | No connection check or task run. Capability is as described by the publisher. | Rule web-search matched: “serp”. Rule web-search. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Remote endpoints
https://mcp.argosor.com/mcp(streamable-http, declares a required credential)https://argosor.com/mcp(streamable-http, declares a required credential)- Packages
argosor-mcp(npm, stdio)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.argosor/mcp
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.