Manusights
REMOTE · MANUSIGHTS.COM
Check if references exist or were retracted, look up journal AI policies, and preview manuscripts.
Available components
Last scanned (2 hours ago)
Scores higher than 73% of remote servers
Reachable. Last reached 25 Oct 2026.
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1572 tokens (~174/item across 9 items; 6 tools + 3 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Oct 26 76
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Probed https://manusights.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=manusights.com | CN=YR1,O=Let's Encrypt,C=US | 3 Oct 2026 | 1 Jan 2027 | RSA 2048 | SHA256-RSA | 69057e836e245aef4c508d2a7752cbe033f |
| SANs: manusights.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of manusights.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| manusights.com. | present | 2371 | 13 | Verified |
| manusights.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
| content-security-policy | base-uri 'self'; frame-ancestors 'none'; object-src 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://manusights.com/mcp | Verified | 200 | |
| http (plaintext) | http://manusights.com/mcp | HTTPS enforced | 308 | https://manusights.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_references Check references ~576
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_reference_count | integer | – | 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 coun… |
| reference_list | string | – | 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. |
| references | array | – | The references to check, one item each. Leave out when sending reference_list. |
| start_at | integer | – | For reference_list only: the list position to continue from, as the previous result's progress.next_start_at says. |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | – |
| counts | object | yes | – |
| how_to_report | string | – | – |
| licensed_by | – | yes | – |
| progress | object | – | – |
| retraction_data_as_of | – | yes | – |
| retraction_data_complete | boolean | yes | – |
| rows | array | yes | – |
No examples provided.
get_journal_ai_policy Get a journal's AI policy ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| journal | string | yes | The journal's exact name or ISSN, e.g. "Nature Communications" or "2041-1723". |
| Name | Type | Req | Description |
|---|---|---|---|
| acceptance_time | – | yes | – |
| ai_policy | – | yes | – |
| journal | – | yes | – |
| name_suggestions | array | – | Closest recorded names for an unmatched query; suggestions are not confirmed matches. Ask which name the user means before another lookup. |
| query | string | yes | – |
No examples provided.
get_manuscript_review Read a manuscript review ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| review_id | string | yes | The review_id of one of the user's reviews. |
| Name | Type | Req | Description |
|---|---|---|---|
| check_again_after_seconds | – | yes | – |
| created_at | – | yes | – |
| filename | – | yes | – |
| full_review | object | yes | – |
| next_step | string | yes | – |
| preview | object | yes | – |
| review_id | string | yes | – |
| target_journal | – | yes | – |
No examples provided.
list_manuscript_reviews List manuscript reviews ~34
Use this when the user asks about their earlier Manusights reviews. Returns the 20 most recent, newest first.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| reviews | array | yes | – |
No examples provided.
review_manuscript Start a manuscript preview ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manuscript | object | yes | The manuscript file the user attached. |
| target_journal | string | – | The journal the author plans to submit to, only if the user named one. |
| Name | Type | Req | Description |
|---|---|---|---|
| check_again_after_seconds | – | yes | – |
| created_at | – | yes | – |
| filename | – | yes | – |
| full_review | object | yes | – |
| next_step | string | yes | – |
| preview | object | yes | – |
| review_id | string | yes | – |
| target_journal | – | yes | – |
No examples provided.
review_manuscript_text Start a manuscript preview from its text ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manuscript_text | string | yes | The full manuscript text, as written. |
| target_journal | string | – | The journal the author plans to submit to, only if the user named one. |
| Name | Type | Req | Description |
|---|---|---|---|
| check_again_after_seconds | – | yes | – |
| created_at | – | yes | – |
| filename | – | yes | – |
| full_review | object | yes | – |
| next_step | string | yes | – |
| preview | object | yes | – |
| review_id | string | yes | – |
| target_journal | – | yes | – |
No examples provided.
How do I install the Manusights MCP server?
Manusights is a hosted endpoint at https://manusights.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · manusights.com
claude mcp add --transport http com-manusights-manusights 'https://manusights.com/mcp'
What is the Manusights MCP server?
Manusights is an MCP server listed in the public MCP registry as com.manusights/manusights. Check if references exist or were retracted, look up journal AI policies, and preview manuscripts. This page covers its hosted endpoint (https://manusights.com/mcp).
Is the Manusights MCP server safe to use?
Manusights scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Manusights MCP server expose?
Manusights exposes 6 tools: check_references, get_journal_ai_policy, review_manuscript, review_manuscript_text, get_manuscript_review, list_manuscript_reviews. Their descriptions and schemas cost roughly 1,389 tokens of context every time the server is loaded.
Does the Manusights MCP server require authentication?
No. We connected to Manusights without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Manusights MCP server still maintained?
Manusights is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.