Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
Manusights is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Manusights connects citation and manuscript checks to your AI assistant.
Check citation records for DOI or title mismatches and retraction or correction notices. Look up a journal’s recorded AI-use policy with its source and checked date. Connect your Manusights account to start a manuscript readiness preview or read a saved review.
Citation and policy lookups are available without an account, with usage limits. Manuscript previews and saved reviews require a connected Manusights account. The MCPRush listing is free; Manusights account requirements and usage limits still apply.
Citation checks compare bibliographic records and notices. They do not establish whether a source supports a scientific claim.
Start here: https://manusights.com/chatgpt
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http manusights-mcp https://manusights.com/mcp
# 2 — ask your agent for something these tools do
# check_references, get_journal_ai_policy, review_manuscript and 3 more
Manusights costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Its publisher asks you to sign in with OAuth: run /mcp in Claude Code and pick this server, and it opens a browser for that once.
claude mcp add --scope user --transport http manusights-mcp https://manusights.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Use this when the user wants to check references or citations from any source: a manuscript, a bibliography, a literature review, or citations an AI assistant gave earlier in the conversation. It reports whether each one exists, points to the right paper, or has been retracted, corrected or flagged, for questions like "are these references real?", "is this paper retracted?" or "is this DOI right?"
| Parameter | Type | Required | Notes |
|---|---|---|---|
| references | array | no | The references to check, one item each. Leave out when sending reference_list. |
| reference_list | string | no | A whole reference list as written, one reference per line, keeping any numbers: numbered, author-year, BibTeX, RIS or CSL-JSON, for example a paper's whole References section. |
| start_at | integer | no | For reference_list only: the list position to continue from, as the previous result's progress.next_start_at says. |
| expected_reference_count | integer | no | The number of references in the whole original list, when known, not the current part. A differing parsed count stops the check before lookup; resend the complete input rather than lowering this count |
Use this when the user asks what a named journal or publisher allows or requires about AI: AI as an author, disclosure statements and where they go, AI-generated images, uploading manuscripts to AI tools, or reviewers' and editors' AI use. It returns the rules as recorded from the publisher's official policy page, with that page's URL and the date Manusights last checked it. When the record is ove
| Parameter | Type | Required | Notes |
|---|---|---|---|
| journal | string | yes | The journal's exact name or ISSN, e.g. "Nature Communications" or "2041-1723". |
Use this when the user wants Manusights to review, check or assess a scientific manuscript they attached (PDF, Word, ODT, RTF, TXT, Markdown or LaTeX, up to 50 MB). Starts a pre-submission preview and returns a review_id right away. The preview takes a few minutes, so read it afterwards with get_manuscript_review using the same review_id. While processing, report status only; do not add a prelimin
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manuscript | object | yes | The manuscript file the user attached. |
| target_journal | string | no | The journal the author plans to submit to, only if the user named one. |
Use this when the user wants Manusights to review, check or assess a scientific manuscript and you have its full text (for example from a file the user attached or pasted), but cannot pass the file itself. Send the complete manuscript text, not a summary or excerpt: title, abstract, every section, figure legends and references. Figures and images are not reviewed in this mode; say so to the user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manuscript_text | string | yes | The full manuscript text, as written. |
| target_journal | string | no | The journal the author plans to submit to, only if the user named one. |
Use this to read the preview, and the Full Review if the account has one, for a review_id returned by review_manuscript or list_manuscript_reviews. While preview.status is "processing", wait check_again_after_seconds and call again with the same review_id. Report status only while processing; when ready, report only returned findings without inventing critique or recommended fixes. Do not use it f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| review_id | string | yes | The review_id of one of the user's reviews. |
Use this when the user asks about their earlier Manusights reviews. Returns the 20 most recent, newest first.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Manusights or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_references | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_journal_ai_policy | no tags | |
| review_manuscript | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| review_manuscript_text | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_manuscript_review | no tags | |
| list_manuscript_reviews | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Manusights can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.