Manusights
com.manusights/manusightsmanusights.comstreamable-httpv1.1.0Scanned
Check if references exist or were retracted, look up journal AI policies, and preview manuscripts.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 5
- Can send data out · 0
- No findings
Anlyon alternative
3 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
check_referencesUse 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 c…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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?". Send citations from earlier in the conversation exactly as given, without correcting them first. Send every reference in the list as its own item, with or without a DOI (one without a DOI is matched by title and first author), with the full text as written, plus its DOI and title when you can read them, and any authors, journal, link, identifier or cite key you can read (the title lets a broken DOI be told apart from a missing work); up to 100 per call. For a whole reference list, such as the References section of an attached paper or a bibliography, send it as written, one reference per line, in reference_list instead of items: every reference in it is checked, in parts when it is long; call again with start_at as the result says until the whole list is done. When the whole original list's count is known, send it as expected_reference_count on every part; do not send a sample or reduce that count to fit a shortened input. Results come from Crossref, the DOI registry and Retraction Watch, and for references without a DOI also Semantic Scholar, PubMed, arXiv and, for books, Open Library; the manuscript itself is not sent. Do not use it to find new sources, to format citations, or to judge whether a source supports a claim. Report as the result's how_to_report says: each status as returned (for example "resolves" or "not found"), explained with the row detail; do not describe results as verified, fabricated or safe to cite. A reference with a DOI is compared by DOI and title only; one without a DOI must match a work by title and author.
Annotations the server declares
- title: Check references
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: true
review_manuscriptUse 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).Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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 preliminary critique. Report only returned findings when ready. Each account can start a limited number of previews per day from connected apps; the result says when the limit is reached. Calling again with the same file and target journal returns the same review instead of starting another. Do not use it to write, rewrite or edit text, for figures or data files, or when no manuscript is attached.
Annotations the server declares
- title: Start a manuscript preview
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
review_manuscript_textUse 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 can…Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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. Accepts up to 600,000 characters. 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 preliminary critique. Report only returned findings when ready. Each account can start a limited number of previews per day from connected apps; the result says when the limit is reached. Calling again with the same text and target journal returns the same review instead of starting another. Do not use it to write, rewrite or edit text.
Annotations the server declares
- title: Start a manuscript preview from its text
- readOnlyHint: false
- destructiveHint: false
- openWorldHint: true
- idempotentHint: true
Only reads 3Show 3 read-only tools
get_journal_ai_policyUse 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 …No findings
Why it is in this group
- The name "get_journal_ai_policy" says "get": a word for reading.
Description, as the server wrote it 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 overdue for a re-check or the page could not be fully read, it says which and gives the URL instead of the rules. It also returns the journal's measured submission-to-acceptance time when Manusights has it. Takes an exact journal name or ISSN. Do not use it for word limits, formatting, fees or impact factors.
Annotations the server declares
- title: Get a journal's AI policy
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
get_manuscript_reviewUse 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.Reads text others writeNo findings
Why it is in this group
- The name "get_manuscript_review" says "get": a word for reading.
What it can reach
- untrusted-inputThe name "get_manuscript_review" says "get" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "read" and "review": it reads comments, which other people can write.
Description, as the server wrote it 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 for review_ids the user has not referred to.
Annotations the server declares
- title: Read a manuscript review
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
list_manuscript_reviewsUse this when the user asks about their earlier Manusights reviews.Reads text others writeNo findings
Why it is in this group
- The name "list_manuscript_reviews" says "list": a word for reading.
What it can reach
- untrusted-inputThe name "list_manuscript_reviews" says "list" and "review": it reads comments, which other people can write.
- untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
Description, as the server wrote it Use this when the user asks about their earlier Manusights reviews. Returns the 20 most recent, newest first.
Annotations the server declares
- title: List manuscript reviews
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write5
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http manusights https://manusights.com/mcpclaude mcp add --transport http manusights https://manusights.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__manusights__get_journal_ai_policy",
"mcp__manusights__get_manuscript_review",
"mcp__manusights__list_manuscript_reviews"
],
"ask": [
"mcp__manusights__check_references",
"mcp__manusights__review_manuscript",
"mcp__manusights__review_manuscript_text"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as manusights. Review it before you use it.
Capability tags behind 5 rules
- mcp__manusights__check_references untrusted-input
- mcp__manusights__review_manuscript untrusted-input
- mcp__manusights__review_manuscript_text untrusted-input
- mcp__manusights__get_manuscript_review untrusted-input
- mcp__manusights__list_manuscript_reviews untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/com.manusights/manusights/verify?hash=3483779dcdfdbfb90708eb3eef43759ad40b6a32542276ea7e4ba15150a21f6c" | jq -e '.changed == false'Pinned hash 3483779dcdfd, from Oct 23, 2026, 03:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/com.manusights/manusights/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/com.manusights/manusights)Source: MCP Registry · repository. Synced Oct 23, 2026, 03:17 UTC.