Search papers, format citations in 60 styles, and verify bibliographies against scholarly sources.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://citeme.app/api/mcp3 tools · 391mssearch_citationsSearch scholarly sources by topic, title, author, DOI, or ISBN and return matching works as formatted citations. Resolved works may be merged into CiteMe's shared scholarly catalog and operational caches; the tool does not publish content or modify a user account.Search scholarly sources by topic, title, author, DOI, or ISBN and return matching works as formatted citations. Resolved works may be merged into CiteMe's shared scholarly catalog and operational caches; the tool does not publish content or modify a user account.
| Parameter | Type | Description |
|---|---|---|
| query* | string | Search query: topic, title, author name, DOI, or ISBN |
| style | string | Citation style (e.g., apa, abnt, mla, vancouver, chicago-author-date, ieee) |
| limit | number | Number of citations to return |
| source_type | string | Type of source to search for |
format_citationFormat citation data (title, authors, year, etc.) into a specific citation style. The formatted result may be stored in an operational cache; the tool does not publish content or modify a user account.Format citation data (title, authors, year, etc.) into a specific citation style. The formatted result may be stored in an operational cache; the tool does not publish content or modify a user account.
| Parameter | Type | Description |
|---|---|---|
| title* | string | Paper/book title |
| authors* | array | Author names (e.g., ["John Smith", "Jane Doe"]) |
| year* | — | Publication year |
| style | string | Citation style |
| doi | string | DOI identifier |
| venue | string | Journal or venue name |
| volume | string | Volume number |
| page | string | Page range (e.g., "123-456") |
| publisher | string | Publisher name |
| url | string | URL of the source |
check_referencesVerify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues. Results may be cached for up to six hours and usage may be logged; the bibliography is not published or added to an account.Verify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues. Results may be cached for up to six hours and usage may be logged; the bibliography is not published or added to an account.
| Parameter | Type | Description |
|---|---|---|
| text* | string | Raw bibliography text (one reference per line, or a full references section) |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Search papers, format citations in 60 styles, and verify bibliographies against scholarly sources.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.