Data · Remote MCP server
Citedy SEO Agent
AI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.nttylock/citedy-seo-agent- Version
- 2.2.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP
- Published
- 2026-03-03
- Updated
- 2026-03-03
- Publisher
- nttylock (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/nttylock) · how
- Website
- www.citedy.com/tools/mcp
- Repository
- github.com/Citedy/citedy-seo-agent
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.citedy.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Citedy SEO Agent
Citedy SEO Agent is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.citedy.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Citation VerificationReal-time fact-check, citation verification, and source-freshness for AI agents. | Remote · HTTPLive check: ✗ no handshake |
| Cite42AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Citead GEO ScoreFree GEO score of a web page or text: how easily AI assistants can quote it, with fixes. No key. | Remote · HTTPLive check: ✓ handshake |
| Citecite MCPInject, parse, and strip [N] citation markers in RAG outputs. | Local · stdio |
| CiteguardVerify citations in AI text: fetches each cited source, returns verdicts with evidence quotes. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| CiteGuardOpen watchdog for retracted & problematic citations: Retraction Watch, OpenAlex, Crossref. | Local · stdio |
| CiteguardFalsification-first citation auditor: existence, metadata, and claim-support checks via MCP. | Local · stdio |
| CiteHawkAI-search visibility (GEO) analytics: brand scores, competitor rankings, recommendations, evidence. | Remote · HTTPLive check: sign-in required |