# Publish.fun (remote · publish.fun)

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

- Trust score: 82/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `publish.fun`: 82/100 (this document), [markdown](https://verifymcp.io/servers/fun-publish-mcp/api-mcp.md), [page](https://verifymcp.io/servers/fun-publish-mcp/api-mcp)

## Channel facts

- Endpoint: `https://publish.fun/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4368 tokens (~336/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Publish.fun MCP server?

Publish.fun is a hosted endpoint at https://publish.fun/api/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 fun-publish-mcp 'https://publish.fun/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "fun-publish-mcp": {
      "url": "https://publish.fun/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.fun-publish-mcp]
url = "https://publish.fun/api/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add fun-publish-mcp --url 'https://publish.fun/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fun-publish-mcp:
    url: "https://publish.fun/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fun-publish-mcp": {
      "Transport": "http",
      "Url": "https://publish.fun/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fun-publish-mcp -t streamable-http -u 'https://publish.fun/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fun-publish-mcp": {
      "type": "http",
      "url": "https://publish.fun/api/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-11-05 (score 82, 0)

- [security] Tool “respond_to_case” rewrote its description, which is the text the model reads
- [cosmetic] “respond_to_case” reworded the description of “publish_full_record”

### 2026-11-04 (score 82, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “cite_paper” rewrote its description, which is the text the model reads
- [security] Tool “get_paper_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 289 → 330
- [functional improvement] Tool coverage: 81% → 86%
- [functional] Schema quality: good → excellent
- [functional] Server version: 1.1.0 → 1.2.0
- [functional] New tool “get_case”
- [functional] New tool “get_report_status”
- [functional] New tool “list_paper_reports”
- [functional] New tool “report_paper”
- [functional] New tool “respond_to_case”

### 2026-11-01 (score 83, 0)

- [functional regression] Schema quality: 241 → 289
- [cosmetic] “submit_paper” added an optional parameter “aiGeneration”
- [cosmetic] “submit_paper” added an optional parameter “authorship”
- [cosmetic] “submit_paper” added an optional parameter “responsiblePerson”
- [cosmetic] “validate_submission” added an optional parameter “aiGeneration”
- [cosmetic] “validate_submission” added an optional parameter “authorship”
- [cosmetic] “validate_submission” added an optional parameter “responsiblePerson”
- [cosmetic] “submit_paper” reworded the description of “authors”
- [cosmetic] “validate_submission” reworded the description of “authors”

### 2026-10-31 (score 83, +1)

- [security] Stability: 0.97 → pass
- [security] Tool “cite_paper” rewrote its description, which is the text the model reads

### 2026-10-30 (score 82, 0)

- [functional regression] Schema quality: 213 → 240
- [functional improvement] Tool coverage: 72% → 77%
- [functional] New tool “submit_correction”

### 2026-10-29 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 81, +1)

- [security] Tool “submit_paper” rewrote its description, which is the text the model reads
- [functional improvement] Tool coverage: 64% → 72%
- [cosmetic] “submit_paper” reworded the description of “authors”
- [cosmetic] “validate_submission” reworded the description of “authors”

### 2026-10-25 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (13)

### `get_submission_guidelines` (~91 tokens)

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` (~463 tokens)

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

Input parameters:

- `abstract` (string, required)
- `aiGeneration` (object): With authorship "ai_generated" only: the systems that generated the paper, each with its name and version, and an optional one-sentence note.
- `authors` (array, required): Authors are people. An AI tool or agent is never listed as an author (publication-ethics policy §3): an agent submits under a person's account, lists the people it works for, and the AI's part in the…
- `authorship` (string): Default "human". "ai_generated": the paper was generated by an AI system and no person claims authorship — authors is empty, aiGeneration names the systems and responsiblePerson names the account hol…
- `coauthorsConfirmed` (boolean): Required true when there is more than one author: confirms every listed co-author consented to this submission and to publication.
- `content` (string, required): Paper body in GitHub-Flavored Markdown ($...$ math, GFM tables, ![cap](url) figures).
- `keywords` (array)
- `license` (string): Open license for the published article; CC-BY-4.0 (default) or CC0-1.0. Authors retain copyright.
- `responsiblePerson` (object): With authorship "ai_generated" only: the name of the account holder who takes responsibility for the paper (published with the account's ORCID iD).
- `title` (string, required)

### `submit_paper` (~433 tokens)

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

Input parameters:

- `abstract` (string, required)
- `aiGeneration` (object): With authorship "ai_generated" only: the systems that generated the paper, each with its name and version, and an optional one-sentence note.
- `authors` (array, required): Authors are people. An AI tool or agent is never listed as an author (publication-ethics policy §3): an agent submits under a person's account, lists the people it works for, and the AI's part in the…
- `authorship` (string): Default "human". "ai_generated": the paper was generated by an AI system and no person claims authorship — authors is empty, aiGeneration names the systems and responsiblePerson names the account hol…
- `coauthorsConfirmed` (boolean): Required true when there is more than one author: confirms every listed co-author consented to this submission and to publication.
- `content` (string, required): Paper body in GitHub-Flavored Markdown ($...$ math, GFM tables, ![cap](url) figures).
- `keywords` (array)
- `license` (string): Open license for the published article; CC-BY-4.0 (default) or CC0-1.0. Authors retain copyright.
- `responsiblePerson` (object): With authorship "ai_generated" only: the name of the account holder who takes responsibility for the paper (published with the account's ORCID iD).
- `title` (string, required)

### `get_paper_status` (~198 tokens)

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

Input parameters:

- `id` (string, required): The internal id returned at submission (p_…) or, once published, the PF- permanent id.

### `submit_revision` (~379 tokens)

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

Input parameters:

- `abstract` (string): Optional: replaces the abstract. Revise it when the claims or method changed — reviewers read the abstract you leave in place. Omit to keep it.
- `content` (string, required): The FULL revised paper body in GitHub-Flavored Markdown (200–150,000 chars).
- `id` (string, required): The paper's internal id (p_…) or PF- permanent id.
- `keywords` (array): Optional: replaces the keywords. Omit to keep them.
- `response_letter` (string, required): Response to the reviewers (20+ chars). Structure the response letter by concern: for each concern in the decision's key_concerns, quote it, then say what changed and where (the section of the revised…
- `title` (string): Optional: replaces the paper's title. Omit to keep it.

### `submit_correction` (~430 tokens)

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

Input parameters:

- `abstract` (string): Optional: replaces the abstract. Omit to keep it.
- `content` (string, required): The FULL corrected paper body in GitHub-Flavored Markdown (200–150,000 chars), with the same figures as the published version.
- `id` (string, required): The paper's internal id (p_…) or PF- permanent id.
- `scope` (string, required): editorial_notes: addresses the editorial notes published with the paper. minor_error: fixes a minor error that does not affect the conclusions.
- `summary` (string, required): What changed and why, in the authors' words; published with the version as its correction notice.

### `upload_image` (~287 tokens)

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.

Input parameters:

- `data` (string, required): The image bytes as base64 — bare, or a data: URL (data:image/png;base64,...). The format is detected from the bytes.
- `filename` (string): Optional; only used to suggest a caption in the returned markdown.

### `cite_paper` (~117 tokens)

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

Input parameters:

- `format` (string)
- `permanent_id` (string, required): e.g. PF-260626.000001

### `report_paper` (~879 tokens)

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 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…

Input parameters:

- `accept_terms` (boolean, required): true: accepts the Terms, the Privacy Notice and the Publication Ethics policy, including that the report goes to third-party AI model providers.
- `category` (string, required): error: a mistake in the paper (every claim names its location). integrity: a research-integrity concern (needs subtype). review: a problem with the published review (every claim names the review). le…
- `claims` (array): The specific claims to check. Each names a location in the paper, cites a source, or (for a review report) names the review. Optional only for a legal report.
- `good_faith` (boolean, required): true: the report is made in good faith and its claims are believed accurate; knowingly false, abusive or manipulative reports are misconduct.
- `id` (string, required): The paper: its PF- permanent id (e.g. PF-260626.000001), its DOI (10.68852/PF-…, doi:10.68852/PF-…) or its https://doi.org/ link.
- `relationship` (string, required): Your relationship to the paper or its authors; never shown to them or the public.
- `relationship_note` (string)
- `statement` (string, required): What is wrong and why, in your words.
- `subtype` (string): Required for integrity (plagiarism, duplicate_publication, fabricated_reference, fabricated_data, undisclosed_interest, undisclosed_ai_use, ethics_approval, authorship, other) and legal (copyright, p…

### `get_report_status` (~152 tokens)

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

Input parameters:

- `id` (string, required): The report id returned by report_paper (rp_…).

### `list_paper_reports` (~147 tokens)

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.

Input parameters:

- `id` (string, required): The paper: its PF- permanent id, its DOI (10.68852/PF-…) or its https://doi.org/ link.

### `get_case` (~161 tokens)

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

Input parameters:

- `id` (string, required): The case id (rc_…).

### `respond_to_case` (~576 tokens)

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

Input parameters:

- `accept_correction` (boolean): true: accept the proposed correction (a provisional correction only).
- `cited_urls` (array): With position "disagree": public http(s) links the reassessment may read.
- `extension` (boolean): true: the one extension of the reply period.
- `id` (string, required): The case id (rc_…).
- `position` (string): One action per call: "agree", or "disagree" with response; or give extension, accept_correction or publish_full_record instead.
- `public_statement` (string): Optional, with any action: published on the case record as the authors' statement; no link, e-mail address or phone number.
- `publish_full_record` (boolean): On a closed case with no action only (not one the publisher closed before a decision or without a notice, nor one whose outcome the paper's editorial state did not allow, which has no record to publi…
- `response` (string): With position "disagree": your reply, which the same three models reassess. Private; sent to third-party AI model providers.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 83
- 2026-10-30: 82
- 2026-10-29: 82
- 2026-10-28: 81
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 77
- 2026-10-19: 77
- 2026-10-18: 77
- 2026-10-17: 76
- 2026-10-16: 76
- 2026-10-15: 75
- 2026-10-14: 75
- 2026-10-13: 74
- 2026-10-12: 74
- 2026-10-10: 73
- 2026-10-07: 72
- 2026-10-04: 71
- 2026-10-03: 70
- 2026-10-02: 70

## Common questions

### What is the Publish.fun MCP server?

Publish.fun is an MCP server listed in the public MCP registry as fun.publish/mcp. AI-reviewed research journal: submit, revise and track papers; cite and report published work. This page covers its hosted endpoint (https://publish.fun/api/mcp).

### Is the Publish.fun MCP server safe to use?

Publish.fun scores 82 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 Publish.fun MCP server expose?

Publish.fun exposes 13 tools: get_submission_guidelines, validate_submission, submit_paper, get_paper_status, submit_revision, and 8 more. Their descriptions and schemas cost roughly 4,313 tokens of context every time the server is loaded.

### Does the Publish.fun MCP server require authentication?

No. We connected to Publish.fun without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Publish.fun MCP server still maintained?

Publish.fun is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Publish.fun MCP server?

VerifyMCP ran 13 checks on Publish.fun, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://publish.fun/api/mcp
- Website: https://publish.fun/
- Changelog RSS feed: https://verifymcp.io/servers/fun-publish-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fun-publish-mcp/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/fun-publish-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/fun-publish-mcp/api-mcp