Skip to main content

Manusights Connector API

Manusights reviews research manuscripts before journal submission. This API lets an AI agent, acting for a researcher who has signed in to Manusights, upload a manuscript for a free preview, read the results, and open checkout for the $39 Full Review. The review is produced by our AI engine, trained with active peer reviewers at top journals. Do not tell users that a person reviewed their manuscript.

MCP setup for Claude

Connect Claude or another remote MCP client to https://manusights.com/mcp. Reference checks and journal AI-policy lookups work without a Manusights account. Starting a manuscript preview or reading saved reviews requires a Manusights account and your approval on its consent screen. Researchers can follow the step-by-step guide at Manusights in Claude.

Connect in Claude

  1. Open Customize, then Connectors, and choose Add custom connector.
  2. Enter Manusights as the name and https://manusights.com/mcp as the server URL.
  3. Choose Sign in when needed under Authentication and Register automatically under OAuth client. Leave fixed request headers empty.
  4. Enable Manusights for your conversation. An account tool will ask you to sign in and approve access when needed. Google, an emailed link, and password sign-in are supported.

Team and Enterprise workspaces may need an owner to add the connector first. See Claude's custom connector guide for the current client controls.

Connect in Claude Code, Codex, Cursor or VS Code

  • Claude Code: run claude mcp add --transport http manusights https://manusights.com/mcp. For account tools, run /mcp in Claude Code, choose manusights and authenticate.
  • Codex: run codex mcp add manusights --url https://manusights.com/mcp. For account tools, run codex mcp login manusights and approve access.
  • Cursor: add {"mcpServers": {"manusights": {"url": "https://manusights.com/mcp"}}} to .cursor/mcp.json in a project or ~/.cursor/mcp.json for every project.
  • VS Code: add {"servers": {"manusights": {"type": "http", "url": "https://manusights.com/mcp"}}} to .vscode/mcp.json.
  • Reference checks and journal AI-policy lookups work in each without signing in. An account tool opens the Manusights sign-in the first time you use it. Ask for Manusights by name.

Available tools

  • check_references: check up to 100 references per call against Crossref, the DOI registry, and Retraction Watch. References without a DOI are also searched in Semantic Scholar, PubMed, arXiv, Open Library (books), and CRAN (R packages). DOI and title are compared; matching a record does not establish that it supports a claim. Account optional.
  • get_journal_ai_policy: look up a journal's recorded AI rules, qualifications, source link, and check date. Unknown, overdue, or unreadable records are identified. Account optional.
  • review_manuscript: start a preview when your client can supply the attached file and its actual download URL. A Manusights account is required. Not offered in Claude, which cannot pass files to a connector.
  • review_manuscript_text: start a preview from the complete manuscript text when your client cannot pass the file. Include the title, abstract, all sections, figure legends, and references. Figures and images are not reviewed in this mode. A Manusights account is required.
  • get_manuscript_review: retrieve an existing preview or review on your account using its review_id.
  • list_manuscript_reviews: list your account's 20 most recent reviews, newest first.

Manusights checks and critiques manuscripts; it does not write or rewrite them. Reference checks send the requested references to Manusights. A manuscript preview sends the manuscript file or complete text for processing and storage under our privacy policy.

Retrieve a manuscript preview

In Claude, use the text tool when an attachment has no downloadable file URL. Send the complete text, not a summary or excerpt; it must contain between 1,500 and 600,000 characters. Ask for a preview and retain the returned review_id.

While preview.status is processing, wait check_again_after_seconds and call get_manuscript_review with that same ID. If the conversation stops waiting, ask Manusights to check the review results. Do not start another preview to check progress. Report status while processing and only the returned findings when ready. A failed or expired result names the next step.

MCP troubleshooting

  • If a tool is not called, enable Manusights for the current conversation and ask to use it by name.
  • If an account tool asks you to connect, complete the Manusights sign-in and consent flow, then retry that tool. An invalid or expired OAuth token returns 401; reconnect if refresh fails.
  • OAuth clients discover the authorization server from the WWW-Authenticate challenge and the MCP resource metadata: https://manusights.com/.well-known/oauth-protected-resource/mcp. Use this MCP metadata URL rather than the REST resource metadata below.
  • If a file cannot be passed, use the complete-text tool. Do not invent a download URL or send a local sandbox path.
  • If a result says it could not be checked, preserve that uncertainty and follow the returned retry guidance. It does not mean a reference is wrong.

For help, email team@manusights.com with the client, tool name, and error message. Keep access tokens and private manuscript content out of the message.

Base URL and specification

Authentication

OAuth 2.1 authorization code flow with PKCE. The user signs in to Manusights with Google or an emailed sign-in link, then approves the connector. Send the access token as Authorization: Bearer <token>. Access tokens are short-lived; use the refresh token to renew them. An unauthenticated call returns 401 with a WWW-Authenticate header pointing at the resource metadata below, so a client can discover the authorization server without configuration.

  • Authorization endpoint: https://mdpguwfazfatqedzbrtq.supabase.co/auth/v1/oauth/authorize
  • Token endpoint: https://mdpguwfazfatqedzbrtq.supabase.co/auth/v1/oauth/token
  • Resource metadata (RFC 9728): https://manusights.com/.well-known/oauth-protected-resource/api/connector/v1
  • Authorization server metadata (RFC 8414): https://mdpguwfazfatqedzbrtq.supabase.co/.well-known/oauth-authorization-server/auth/v1
  • OpenID discovery: https://mdpguwfazfatqedzbrtq.supabase.co/auth/v1/.well-known/openid-configuration
  • Scopes: openid email profile. Reviews are delivered to the account email.
  • Client credentials are issued by Manusights. Email team@manusights.com with your redirect URIs.

Endpoints

  • POST/uploads

    For files over 4 MB: send filename and size_bytes, get a signed upload_url and an upload_id.

  • POST/reviews

    Start the free preview: JSON with upload_id (after /uploads), or multipart field "file" for files up to 4 MB. Optional target_journal.

  • GET/reviews

    List the account's 20 most recent reviews.

  • GET/reviews/{review_id}

    Preview results (readiness score, verdict, strengths, top risks, citation check) and Full Review status.

  • POST/reviews/{review_id}/checkout

    Get a Stripe Checkout link for the $39 Full Review. Requires a finished preview.

Typical flow

  1. Upload the manuscript. Call POST /uploads with the filename and size, send the raw bytes with PUT to upload_url using the returned headers, then call POST /reviews with the upload_id. Files up to 4 MB can instead go straight to POST /reviews as multipart. Accepted: PDF, Word (.docx, .doc), OpenDocument, RTF and plain text, up to 50 MB. Pass target_journal when the user has one in mind.
  2. Poll GET /reviews/{review_id} every poll_after_seconds until preview.status is ready. Previews usually take a few minutes.
  3. Show the readiness score and top risks. The preview is free and the user is also emailed a link to it.
  4. If the user wants the Full Review, call POST /reviews/{review_id}/checkout and open checkout_url. The user pays $39 on Stripe Checkout (cards, Apple Pay, Google Pay, Link). Never complete payment without the user's confirmation.
  5. Poll the review until full_review.status is ready, then share download_url (a .docx). The report is also emailed to the account address.

Limits

  • 3 free previews per account per 24 hours through the connector.
  • 120 requests per minute per account. Every 429 carries Retry-After.
  • Retries: POST /reviews with the same upload_id returns the first review instead of starting a second preview, and a repeated checkout call returns the same Stripe session. A retried multipart upload has no such key, so prefer POST /uploads for anything you may retry.
  • The Full Review costs $39 (USD) per manuscript and comes with a 60-day money-back guarantee.

Errors

Errors return { "error": { "code", "message" }, "request_id" }. The message is written to be shown to the user.

  • 401unauthorized

    Missing, invalid or expired access token. Refresh the token and retry.

  • 404not_found

    No review with that id exists for this account.

  • 400unsupported_file / file_too_large

    Show the message to the user; it names the accepted formats and limit.

  • 429daily_limit_reached

    The account used its free connector previews for the last 24 hours.

  • 409preview_not_ready

    Poll the review until preview.status is "ready", then retry checkout.

  • 409already_purchased

    Poll the review for the Full Review status instead.

  • 422manuscript_too_large

    The manuscript is too long for the automated Full Review. Point the user to team@manusights.com.

  • 503service_unavailable

    Temporary. Retry with backoff.

Privacy and support

Manuscripts are handled under our privacy policy and terms. Users can disconnect any app themselves under connected apps in their Manusights account, which revokes its tokens immediately. Questions and client registration: team@manusights.com.