Publish.fun

fun.publish由 publish.fun 发布官方发布者v1.2.0更新于 Nov 5, 2026

AI-reviewed research journal: submit, revise and track papers; cite and report published work.

已验证Streamable HTTP可网页运行效率与工作流知识与记忆

概览

AI 生成的概览

Publish.fun 让助手提交研究论文接受 AI 评审、跟踪与修订稿件、上传图片、引用已发表论文,并提交或回应问题报告。

可以做什么
  • 查询投稿要求,并在正式提交前试运行校验稿件
  • 提交论文接受 AI 评审,并跟踪评审状态、轮次与各版本
  • 为需修订的论文提交修订稿,为已发表论文提交更正
  • 上传插图并获得可嵌入稿件的公开链接
  • 获取已发表论文的 BibTeX、RIS、CSL 或纯文本引用
  • 举报已发表论文的问题、查询举报状态、查看论文公开举报记录,并回应针对自己论文的案件
适用场景
适合作者希望由助手准备、校验并向该 AI 评审期刊投稿,跟进评审轮次,或处理修订、更正与学术诚信举报,而不必使用网页界面时。
运行要求
远程 streamable HTTP 端点 publish.fun,无需本地安装。多数只读工具无需凭据,但提交、修订、更正、上传图片、举报和回应案件都需要在 Authorization 请求头中提供 bearer API 密钥。已录用论文要正式发表,账户须绑定 ORCID iD。
安装前请注意
Authorization 请求头中的 API 密钥可用于投稿和账户操作。提交、修订、更正、举报和回应都会对期刊记录产生真实且不可撤销的影响。上传的插图一经上传即公开可访问,早于任何评审。案件结案后,举报与回应会进入公开记录。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Publish.fun,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/fun.publish%2Fmcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "publish-fun": {
      "type": "http",
      "url": "https://publish.fun/api/mcp"
    }
  }
}

工具

13

get_submission_guidelines

Get submission guidelines

Get the requirements and JSON schema for submitting a paper to Publish.fun, how to obtain an API key, and what the account's ORCID iD gates (publication of an accepted paper, not submission). With Authorization: Bearer <api_key> on the request it also returns the account's current submission_allowance (how many submissions are left this hour and today, and when the next slot opens).

无需输入参数。

validate_submission

Check a paper before submitting it

Dry-run a submission: the same checks submit_paper makes (fields, lengths, co-author consent, figure references) plus warnings for common mistakes, without creating anything or using a submission slot. Works without a key; with Authorization: Bearer <api_key> it also reports the account's readiness (submissions left, whether an accepted paper would publish at once or wait for the account's ORCID iD).

输入参数title必填authors必填content必填licenseabstract必填keywordsauthorshipaiGenerationresponsiblePersoncoauthorsConfirmed

submit_paper

Submit a paper for review

Submit a research paper for AI review. Requires Authorization: Bearer <api_key> on the request. No ORCID iD is needed to submit; an accepted paper is published once the account has linked one (the result's identity field says whether it has).

输入参数title必填authors必填content必填licenseabstract必填keywordsauthorshipaiGenerationresponsiblePersoncoauthorsConfirmed

get_paper_status

Get a paper's review status

Get the review status of a paper you submitted (decisions with their editorial_notes, reviews, current round, and versions: each round's manuscript with the title, abstract and keywords in force for it), plus your account's submission_allowance and a progress block: the step running now with its elapsed time, the steps still to come, and each round's steps with their times. Once published it also carries the paper's editorial_notices (corrections, expressions of concern, a retraction or withdrawal, each with its notice page and DOI once registered), its integrity block (state, an active expression of concern, a retraction under the publisher's review, the counts of report cases) and open_cases, the reports on it you may answer. Requires Authorization: Bearer <api_key>.

输入参数id必填

submit_revision

Submit a revised manuscript

Submit a revised manuscript for a paper whose status is revision_requested — address the decision's summary_to_authors and key_concerns from get_paper_status, concern by concern in response_letter (see its description). The paper re-enters review as the next round: after a major-revision request the same panel checks each listed concern against the revised manuscript, reusing its earlier web evidence unless it cites a DOI or arXiv id that version did not, or more than 30% of its paragraphs are new or changed since the version that evidence was gathered on, and the editor accepts once every concern is addressed unless a new correctness, validity, novelty or reproducibility issue is documented with evidence; a round after a minor-revision request is checked by the editor alone (see get_submission_guidelines for the revision policy). Requires Authorization: Bearer <api_key>.

输入参数id必填titlecontent必填abstractkeywordsresponse_letter必填

submit_correction

Propose a corrected version of a published paper

Propose a corrected version of a PUBLISHED paper you authored: the full corrected body, a summary of what changed (published as the correction notice) and the scope — "editorial_notes" when the change addresses the editorial notes published with the paper, "minor_error" when it fixes a minor error that does not affect the conclusions. The editor model rules on the change against the correction policy; within scope, the text becomes the next version of record with a correction notice on the article and the previous version kept on the History tab; otherwise the request is refused with the editor's rationale. get_paper_status shows the ruling (correction_request) and the author is e-mailed either way. A corrected version may only address the editorial notes published with the paper or fix minor errors that do not affect the paper's conclusions or reliability (a typo, a mislabeled figure, an incomplete statement, a broken reference, a small factual slip). It must not change the paper's claims, results, methods, data, figures or references in substance, and must not add new findings; such changes call for a new paper or, where the published results cannot be relied upon, a retraction. The title cannot change. Every version stays on the record: the previous text remains readable from the paper's History tab. The figures must be the published version's; one request at a time per paper. Requires Authorization: Bearer <api_key>.

输入参数id必填scope必填content必填summary必填abstract

upload_image

Upload a figure image

Upload a figure image (PNG, JPEG, GIF or WebP) for a manuscript and get a permanent public URL to reference as ![caption](url) in submit_paper / submit_revision content. An uploaded image is public as soon as it is uploaded: anyone with the link can open it, before any review and whether or not the paper is ever accepted, so upload only images that may be made public. Copies of images referenced at other hosts or embedded inline are public in the same way once the paper enters review. The image is re-encoded (metadata stripped; GIF/WebP stored as PNG; at most 10 MB and 25 megapixels; 60 uploads/hour). NOTE: this JSON-RPC endpoint accepts bodies up to 4 MB, so base64 images are capped at roughly 3 MB here — for larger files POST multipart/form-data to /api/uploads/images (GET it for the schema). Images become permanent once a submitted manuscript references them; unreferenced uploads are removed after 7 days. Requires Authorization: Bearer <api_key> and a verified ORCID iD.

输入参数data必填filename

cite_paper

Cite a published paper

Get a citation for a published paper (no auth). Returns BibTeX/RIS/CSL/text, with the paper's Crossref DOI once it is registered. A retracted or withdrawn paper is cited as such: each format's title starts "Retracted: " or "Withdrawn: " and its note names the notice's DOI once registered (format all also gives editorial_state and notice_doi).

输入参数formatpermanent_id必填

report_paper

Report a problem with a published paper

Report a problem with a PUBLISHED paper (anyone's): an error, a research-integrity concern, a problem with its published review, or a legal matter. Any signed-in account may report a problem with a published paper: an error, a research-integrity concern, a problem with the published review, or a legal matter. Use POST /api/papers/{id}/reports, the MCP tool report_paper, or the Report page of the paper. Limits: 3 reports an hour and 5 a day, one open report per paper, and an account's first report is screened before it can file another. A report needs a category, a statement of 50–5000 characters, and (except for a legal matter) at least one claim that names a location in the paper (section, figure, table, equation, reference or a quoted passage) or cites a source (DOI, arXiv id or http(s) URL); quotes must be copied exactly. Code checks quotes and references, a model screens the report, and three AI models, from labs that did not review the paper wherever enough are available, assess what passes. Every outcome adverse to the authors needs all three, an expression of concern or a retraction also needs checked evidence from a source the reporter did not supply (a registry's answer that a cited work exists does not count), and, unless the report came from the authors themselves, the authors have 14 days (one 14-day extension) to reply before anything is published. A recommended retraction publishes an expression of concern at once and becomes a retraction after the publisher's review window of at least 7 days from the delivery of its notification unless the publisher declines it. Legal reports go to [email protected], and no model reads them. Your identity is never shown to the authors or the public; your report text is sent to third-party AI model providers, and sources you cite may be published as evidence, at most by the name of a public site that holds them (never their address). Knowingly false, abusive or manipulative reports are misconduct (Terms §10). Confirm w

输入参数id必填claimssubtypecategory必填statement必填good_faith必填accept_terms必填relationship必填relationship_note

get_report_status

Get a report's status

Get the status of a report you filed: its one-line reason if it was refused or dismissed, and, once its case is public (closed, or a retraction recommended), the outcome, the verdicts on your own claims and the public record's link; until then the case reads only "in_progress". Also returns your report_allowance. Report responses carry RateLimit-Limit/Remaining/Reset/Policy for the binding window (3/h, 5/day) and report_allowance in the body; a 429 carries Retry-After when a clock binds. Requires Authorization: Bearer <api_key>.

输入参数id必填

list_paper_reports

List a paper's public report record

Get a published paper's public record of reports: each case the journal decided (with its outcome, the upheld claims, the votes and the evidence), the number of other reports assessed with no action, and how to report a problem (the body, the categories this paper accepts, the limits and the policy). No key needed; with Authorization: Bearer <api_key> it also returns the account's report_allowance (what it may file now, and when the next slot opens), before you file.

输入参数id必填

get_case

Get a report case

Get a report case on a paper you submitted, or one your report joined. As the paper's submitting account you get the finding you may answer: the claims the assessing models upheld (restated neutrally) with the verified evidence, each model's verdict, the proposed notice and correction, reply_due_at and allowed_actions (answer with respond_to_case). As a reporter you get only "in_progress" until the case is public (closed, or a retraction recommended), then its outcome and public record. The case ids of your papers are in get_paper_status (open_cases) and GET /api/me (cases_on_my_papers). Requires Authorization: Bearer <api_key>.

输入参数id必填

respond_to_case

Answer a report case on your paper

Answer a report case on a paper you submitted (the paper's submitting account only): agree with the provisional finding, disagree with a response, accept a proposed correction, ask once for more time, or publish the full record of a case that ended with no action. Call get_case first: its allowed_actions say what is possible now. The authors (the paper's submitting account; for an AI-generated paper, the responsible person) answer a provisional finding before its reply deadline, 14 days after it is sent: agree; disagree with a response of 20–10,000 characters and up to 5 public links, which the same three models reassess and may confirm or lower, never raise (one reply); accept a proposed correction; or ask once for 14 more days. One action per request. A public statement of up to 2,000 characters, with no link, e-mail address or phone number, may go with any of them and is published on the case record. The response itself is private, and it is sent to third-party AI model providers. After the deadline the provisional outcome stands. A closed case that ended with no action is public only as a count unless the authors publish its full record (publish_full_record); a case the publisher closed before its assessment reached a decision or without a notice, or whose outcome the paper's editorial state did not allow, is not counted and has no record to publish (Publication Ethics §10). Confirm with the person before answering: agreeing or accepting applies the outcome, and a public statement is published. Requires Authorization: Bearer <api_key>.

输入参数id必填positionresponseextensioncited_urlspublic_statementaccept_correctionpublish_full_record

版本历史

2
  1. v1.2.0最新Nov 5, 2026
  2. v1.0.0Oct 1, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。

其他 Publish 集成