# Manusights (remote · manusights.com)

Check if references exist or were retracted, look up journal AI policies, and preview manuscripts.

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

## Components

- remote · `manusights.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-manusights-manusights/manusights.md), [page](https://verifymcp.io/servers/com-manusights-manusights/manusights)

## Channel facts

- Endpoint: `https://manusights.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-manusights-manusights 'https://manusights.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-manusights-manusights": {
      "url": "https://manusights.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-manusights-manusights": {
      "type": "http",
      "url": "https://manusights.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-manusights-manusights]
url = "https://manusights.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-manusights-manusights": {
      "type": "remote",
      "url": "https://manusights.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-manusights-manusights --url 'https://manusights.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-manusights-manusights:
    url: "https://manusights.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-manusights-manusights": {
      "Transport": "http",
      "Url": "https://manusights.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-manusights-manusights -t streamable-http -u 'https://manusights.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-manusights-manusights": {
      "type": "http",
      "url": "https://manusights.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-25 (score 77, +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.

### 2026-10-24 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-23 (score 76)

First indexed and scored.

## MCP tools (6)

### `check_references` (~576 tokens)

Check references

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.

Input parameters:

- `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.

Output parameters:

- `checked_at` (string)
- `counts` (object)
- `how_to_report` (string)
- `licensed_by`
- `progress` (object)
- `retraction_data_as_of`
- `retraction_data_complete` (boolean)
- `rows` (array)

### `get_journal_ai_policy` (~191 tokens)

Get a journal's AI policy

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.

Input parameters:

- `journal` (string, required): The journal's exact name or ISSN, e.g. "Nature Communications" or "2041-1723".

Output parameters:

- `acceptance_time`
- `ai_policy`
- `journal`
- `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)

### `review_manuscript` (~216 tokens)

Start a manuscript preview

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.

Input parameters:

- `manuscript` (object, required): The manuscript file the user attached.
- `target_journal` (string): The journal the author plans to submit to, only if the user named one.

Output parameters:

- `check_again_after_seconds`
- `created_at`
- `filename`
- `full_review` (object)
- `next_step` (string)
- `preview` (object)
- `review_id` (string)
- `target_journal`

### `review_manuscript_text` (~254 tokens)

Start a manuscript preview from its text

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.

Input parameters:

- `manuscript_text` (string, required): The full manuscript text, as written.
- `target_journal` (string): The journal the author plans to submit to, only if the user named one.

Output parameters:

- `check_again_after_seconds`
- `created_at`
- `filename`
- `full_review` (object)
- `next_step` (string)
- `preview` (object)
- `review_id` (string)
- `target_journal`

### `get_manuscript_review` (~118 tokens)

Read a manuscript review

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.

Input parameters:

- `review_id` (string, required): The review_id of one of the user's reviews.

Output parameters:

- `check_again_after_seconds`
- `created_at`
- `filename`
- `full_review` (object)
- `next_step` (string)
- `preview` (object)
- `review_id` (string)
- `target_journal`

### `list_manuscript_reviews` (~34 tokens)

List manuscript reviews

Use this when the user asks about their earlier Manusights reviews. Returns the 20 most recent, newest first.

Output parameters:

- `reviews` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-manusights-manusights/manusights#diagnostics

## Score history

- 2026-10-25: 77
- 2026-10-24: 76
- 2026-10-23: 76

## Common questions

### 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.

## Links

- Remote endpoint: https://manusights.com/mcp
- Repository: https://github.com/Manusights/manusights-mcp
- Website: https://manusights.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-manusights-manusights/manusights.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-manusights-manusights/manusights.json
- HTML version of this page: https://verifymcp.io/servers/com-manusights-manusights/manusights