Publish.fun MCP server
fun.publish/mcppublish.funstreamable-httpv1.2.0Scanned
AI-reviewed research journal: submit, revise and track papers; cite and report published work.
13 tools: 6 change things and 7 only read.
- Reads private data · 1
- Reads text others write · 7
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
6 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Publish.fun MCP server can do
The Publish.fun MCP server is published by publish.fun, a domain the MCP Registry verified. It has 13 tools. It can create or change data (6 tools: submit_paper, submit_revision, submit_correction, upload_image and 2 more), but cannot delete data. 7 tools only read.
1 tool reads private data (get_paper_status); 7 tools bring in text other people can write (submit_paper, get_paper_status, submit_revision and 4 more).
The fixed checks matched 1 finding (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 3 times since Anlyon Radar first saw them.
Last scanned Nov 19, 2026, version 1.2.0.
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.
13 tools
Changes things 6Claude Code: ask
report_paperReport a problem with a PUBLISHED paper (anyone's): an error, a research-integrity concern, a problem with its published review, or a legal matter.Reads text others write1 finding
Why it is in this group
- The input takes a statement or command to run (input.statement), which can change anything it can reach.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The description is 2,395 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...) and the allowance this filing leaves. Requires Authorization: Bearer <api_key>."
Description, as the server wrote it 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 legal@publish.fun, 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 with the person before filing: the report text goes to third-party AI model providers, and cited sources may be published as evidence. Call list_paper_reports first to see the paper's record and, with your key, your report_allowance. The result carries the report's id, its status_url (poll it, or get_report_status) and the allowance this filing leaves. Requires Authorization: Bearer <api_key>.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
respond_to_caseAnswer 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…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 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>.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
submit_correctionPropose 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_no…Reads text others writeNo findings
Why it is in this group
- The name "submit_correction" says "submit": a word for a change.
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 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>.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
submit_paperSubmit a research paper for AI review.Reads text others writeNo findings
Why it is in this group
- The name "submit_paper" says "submit": a word for a change.
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 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
submit_revisionSubmit 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…Reads text others writeNo findings
Why it is in this group
- The name "submit_revision" says "submit": a word for a change.
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 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>.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
upload_imageUpload a figure image (PNG, JPEG, GIF or WebP) for a manuscript and get a permanent public URL to reference as  in submit_paper / submit_revision content.Reads text others writeNo findings
Why it is in this group
- The name "upload_image" says "upload": a word for a change.
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 Upload a figure image (PNG, JPEG, GIF or WebP) for a manuscript and get a permanent public URL to reference as  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>.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 7Show 7 read-only tools
cite_paperGet a citation for a published paper (no auth).No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_caseGet a report case on a paper you submitted, or one your report joined.No findings
Why it is in this group
- The name "get_case" says "get": a word for reading.
Description, as the server wrote it 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>.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_paper_statusGet 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 key…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_paper_status" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "note": it reads notes.
- untrusted-inputThe description's first sentence says "get" and "review": it reads comments, which other people can write.
Description, as the server wrote it 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>.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_report_statusGet 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 verdi…No findings
Why it is in this group
- The name "get_report_status" says "get": a word for reading.
Description, as the server wrote it 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>.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_submission_guidelinesGet 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 s…No findings
Why it is in this group
- The name "get_submission_guidelines" says "get": a word for reading.
Description, as the server wrote it 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 today, how many more papers may be in review at once, and when the day window opens its next slot).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_paper_reportsGet 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 asses…No findings
Why it is in this group
- The name "list_paper_reports" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_submissionDry-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 usi…No findings
Why it is in this group
- The name "validate_submission" says "validate": a word for reading.
Description, as the server wrote 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- 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 outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write7
- 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.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://publish.fun/api/mcp: tools/list returned 13 tools to an anonymous client, including submit_paper (write), submit_revision (write), submit_correction (write), upload_image (write), report_paper (write) and 1 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 3 to 6
Findings
Matches of fixed checks, with the text they matched.
- Inforeport_paper
The description is 2,395 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...) and the allowance this filing leaves. Requires Authorization: Bearer <api_key>."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools2 changed.~2 changedView diff
- Changed:get_submission_guidelinesOnly readsdescription
- Changed:upload_imageChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 3 -> 6.View diff
- Tools that change things, listed without credentials: 3 to 6
Tools5 added, 2 changed.+5 added~2 changedView diff
- Added:get_caseOnly reads
- Added:get_report_statusOnly reads
- Added:list_paper_reportsOnly reads
- Added:report_paperChanges things
- Added:respond_to_caseChanges things
- Changed:cite_paperOnly readsdescription
- Changed:get_paper_statusOnly readsdescription
Tools1 added, 3 changed.+1 added~3 changedView diff
- Added:submit_correctionChanges things
- Changed:cite_paperOnly readsdescription
- Changed:submit_paperChanges thingsdescriptioninputSchema
- Changed:validate_submissionOnly readsinputSchema
Install
Pinned to version 1.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http publish https://publish.fun/api/mcpclaude mcp add --transport http publish https://publish.fun/api/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__publish__get_submission_guidelines",
"mcp__publish__validate_submission",
"mcp__publish__get_paper_status",
"mcp__publish__cite_paper",
"mcp__publish__get_report_status",
"mcp__publish__list_paper_reports",
"mcp__publish__get_case"
],
"ask": [
"mcp__publish__submit_paper",
"mcp__publish__submit_revision",
"mcp__publish__submit_correction",
"mcp__publish__upload_image",
"mcp__publish__report_paper",
"mcp__publish__respond_to_case"
],
"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 publish. Review it before you use it.
Capability tags behind 7 rules
- mcp__publish__submit_paper untrusted-input
- mcp__publish__get_paper_status private-data, untrusted-input
- mcp__publish__submit_revision untrusted-input
- mcp__publish__submit_correction untrusted-input
- mcp__publish__upload_image untrusted-input
- mcp__publish__report_paper untrusted-input
- mcp__publish__respond_to_case 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://radar.anlyon.com/api/v1/servers/fun.publish/mcp/verify?hash=08657bcce617677efde1cae5a2b2fa142866c235845b8426763859f1d8320d9a" | jq -e '.changed == false'Pinned hash 08657bcce617, from Nov 19, 2026, 09:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/fun.publish/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/fun.publish/mcp)Source: MCP Registry. Synced Nov 5, 2026, 12:17 UTC.
Publish.fun MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Publish.fun MCP server safe?
- No scan can promise that. What its definitions show: 13 tools, 6 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Publish.fun MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Publish.fun MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Publish.fun MCP server have?
- 13 tools: 6 write, 7 read. submit_paper, submit_revision, submit_correction, upload_image, report_paper, respond_to_case, get_submission_guidelines, validate_submission and 5 more.
Does the Publish.fun MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Publish.fun MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Publish.fun MCP server changed its tools?
- Yes, 3 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.