Learning Resources
citeme.app
Provides tools to search and format scholarly citations and verify bibliographies.
ENDPOINT 1
https://citeme.app/api/mcp
MCP server metadata
- Name
- CiteMe
- Version
- 1.1.0
CiteMe checks citations against scholarly records (CrossRef, OpenAlex, PubMed, Semantic Scholar, Google Books) and returns evidence, not verdicts. Choosing a tool: - search_citations — the user needs to FIND a source. - format_citation — the user already has complete metadata and wants it styled. - check_references — the user already has citations and wants them verified. Use this for any bibliography that was generated, extracted, or pasted, including one you produced yourself. Reporting check_references results. Read these as behaviour, not as calibrated probabilities: - [NOT FOUND] and [FABRICATED?] are different signals; never merge them. Fabricated references do fail to verify, but so does a large share of real ones — works that are not indexed, grey literature, or simply missed. Always report [NOT FOUND] as needing human review, never as a confirmed fake. - [FABRICATED?] is the separate, conservative risk flag. It is tuned to raise few false alarms rather than to catch everything, so it misses some fabrications and will occasionally flag a real source. Report it as likely fabricated — never as proven. - A match does NOT confirm the fields are correct. This tool reports a status, and most field-level corruption does not change that status: a wrong year, journal, volume, or page range on a source that genuinely exists usually still comes back matched. Tell the user to verify those by hand. - [GREY LITERATURE] means the work is plausibly real but not indexed in these databases. [RETRACTED] means the record exists and was withdrawn — surface it, do not treat it as a clean match. Frozen-corpus evidence (369 references, public MCP profile, 2026-08-09): all 80 fabricated references remained unverified; field-level issues were detected in 85% (85/100) of corrupted references, but only 28% changed visible status. The older recall and false-positive figures for [FABRICATED?] were withdrawn after a production coverage audit found a non-independent search-count signal. These are corpus rates, not calibrated probabilities for real traffic.
Known tools 3
search_citationsSearch scholarly sources by topic, title, author, DOI, or ISBN and return matching works as formatted citations.
Inferred read-onlycheck_referencesVerify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.citeme]
url = "https://citeme.app/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"citeme": {
"type": "http",
"url": "https://citeme.app/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: citeme
Remote MCP URL: https://citeme.app/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"citeme": {
"url": "https://citeme.app/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"citeme": {
"type": "http",
"url": "https://citeme.app/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "citeme",
"transport": "streamable-http",
"url": "https://citeme.app/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for citeme.app was fetched 2026-08-24T05:57:35.401Z.
citeme.app is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.