Data · Remote MCP server
Cite42
AI visibility and SEO data for AI agents: citations, keywords, trends, and scheduled trackers.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.cite42/mcp- Version
- 0.7.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-09-30
- Updated
- 2026-09-30
- Publisher
- dev.cite42
- Namespace
- Namespace verified by the MCP Registry via the domain cite42.dev · how
- Website
- www.cite42.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.cite42.dev | None |
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
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @cite42/mcp | 0.7.0 | stdio |
How to connect Cite42
Cite42 is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.cite42.dev, 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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @cite42/mcp version 0.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @cite42/mcp@0.7.0. It reads these environment variables: CITE42_API_KEY (required, secret) and CITE42_API_BASE; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@cite42/mcp@0.7.0"
],
"env": {
"CITE42_API_KEY": "<secret>",
"CITE42_API_BASE": "<value>"
}
}
}
}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 IntelligenceCheck what Perplexity, Claude, ChatGPT, Gemini, and Google AI Overviews cite for any query. | Local · stdio |
| Citation Network MCPCitation-network analysis on Scopus or OpenAlex: coupling, co-citation, lineages, bibliometrics. | Local · stdio |
| Citation Safe VerifierVerifies legal citations vs primary sources: existence, quote match, proposition support. | Remote · HTTPLive check: ✓ handshake |
| Citation VerificationReal-time fact-check, citation verification, and source-freshness for AI agents. | Remote · HTTPLive check: ✗ no handshake |
| 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 |
| Citedy SEO AgentAI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets. | Remote · HTTPLive check: sign-in required |
| CiteguardVerify citations in AI text: fetches each cited source, returns verdicts with evidence quotes. | Remote & Local · HTTP, stdioLive check: ✓ handshake |