Skip to content
IsoKron

Disputes

Right of reply and disputes

How a named vendor replies to a published result, and how anyone disputes a published fact, finding or rating. Free, and no customer relationship is needed.

Right of reply

  • We publish results on named servers without a pre-publication review. The right of reply applies from the moment a page is live.
  • The vendor or maintainers may send a statement of up to 300 words at any time. Once received, it is shown on the page beside the result, signed, dated and unedited.
  • Errors of fact, findings and ratings are disputed through the process below. A confirmed error is corrected on the page and listed in the corrections log, and a dispute with material evidence marks the result “Disputed” until it is decided.
  • Security-class findings are not published with the results. They go to the project’s private reporting channel under our disclosure policy, with a 90-day default embargo.
  • Correctness findings filed as public issues on the project’s own tracker are already public, and the page links to them.

Statements:

  • We publish a statement as written or decline it; we never edit it.
  • We decline a statement that is unlawful, contains personal data about someone else, discloses security details still under embargo, or is not about the result. We tell the author why, and they may send a new one.
  • Before publishing, we confirm who wrote it: the statement must come from an email address at the vendor’s domain or listed by the project, or be posted by a maintainer account on the project’s own repository. It is published with the author’s name and role.

Who can dispute

Anyone: the vendor, the maintainers, a user of the server or a researcher. Disputes from people and companies that have never bought from IsoKron are handled exactly like those from clients. Opening a dispute is free.

A dispute about a private audit report goes through the engagement: show us an error of fact with evidence and we correct the report free of charge, list the change with its date and fingerprint the corrected version beside the original.

What you can dispute

  • A fact. The server version, the date, the tool list, the configuration or anything a transcript shows.
  • A finding. The records do not show what the page says they show, or the behavior does not reproduce with the published command.
  • Applicability. A requirement was applied to a tool that a written applicability rule excludes, or the reverse.
  • The rating. The published method was applied to the records incorrectly.
  • A tester fault. The harness, not the server, caused the recorded behavior.
  • Attribution. The behavior belongs to the backend or platform, not to the MCP server, or the reverse.
  • Gaming. A result was produced by special-casing the tester. Such an allegation is published only once evidence substantiates it.

The method itself is not decided case by case. Comments on the MWS specification go through its public comment process on the specification page; rating-method changes are versioned and announced in advance, as the ethics policy sets out. A fix released in a newer version does not change the result for the version tested: ask for a run of the new release instead, and both results stay listed with their dates.

How to open a dispute

Email hello@isokron.ai with the subject “Dispute: [server] [version]” and these fields. The button above opens an email with the template filled in.

  1. Your name and role (maintainer, vendor, user, researcher, other)
  2. Organization (optional)
  3. Page (the URL of the result, rating or finding)
  4. Result or finding ID (for example GH-01)
  5. Server and version (the version or commit the result covers)
  6. What is wrong (one or two sentences)
  7. Evidence (commands and output, raw records, logs, code links, documentation)
  8. Outcome you ask for (correction, withdrawal, or a statement beside the result)
  9. Statement to publish (optional, up to 300 words)
  10. May we name you in the dispute log? (yes or no)
Dispute template
Your name and role (maintainer, vendor, user, researcher, other):

Organization (optional):

Page (the URL of the result, rating or finding):

Result or finding ID (for example GH-01):

Server and version (the version or commit the result covers):

What is wrong (one or two sentences):

Evidence (commands and output, raw records, logs, code links, documentation):

Outcome you ask for (correction, withdrawal, or a statement beside the result):

Statement to publish (optional, up to 300 words):

May we name you in the dispute log? (yes or no):

Never send tokens, passwords or keys. A security problem in IsoKron’s own site or tools goes to the security page instead.

Evidence that helps

Reproducible evidence settles a dispute fastest. For example:

  • A run of the published command on the same version with the public tester, which maintainers can run themselves, with its records, that does not reproduce the result.
  • A field in the raw records that shows the tester recorded something other than what happened.
  • Code in the server, at the version tested, that shows a different behavior.
  • Platform documentation or a control run against the platform’s own API, for attribution.

Every result published under our ethics policy carries its command and raw records, so a dispute can start from the same run we made.

Maintainers can run the public MWS tester themselves and send its records. IsoKron decides whether to re-run the test itself.

Timeline

Acknowledgment
We reply within two business days.
Review
A person at IsoKron reviews the evidence, including any records the maintainer ran with the public tester, and decides whether to re-run the disputed test.
Decision
Within 30 days of receiving the evidence. If a re-run needs longer, we say why and give a new date.
Reasons
Every decision states its reasons, and the dispute log records it.
New evidence
A decided dispute can be reopened once with evidence that was not available before.

Outcomes

Corrected
The fact, finding or rating changes. The page carries a dated correction note saying what changed and why, the change is added to the corrections log, and a corrected private report gets a new fingerprint beside the original.
Upheld
The result stands. The page shows the decision and its reasons, and the vendor’s or maintainer’s statement of up to 300 words if they want one, signed, dated and unedited.
Withdrawn
The finding or rating is withdrawn. The page keeps a dated note of what was withdrawn and why; it is never deleted silently.

How a disputed result is shown

  • Only disputes that carry material evidence about a result are logged and shown on the page.
  • Once we confirm that a dispute carries material evidence about a result, the result is marked “Disputed”, with the date the dispute was opened and a link to its entry in the dispute log.
  • The letter, the coverage and the records stay visible while the dispute is open.
  • When the dispute closes, the marker is replaced by its outcome and date: corrected, upheld or withdrawn.
  • A dispute without material evidence is answered privately. It is not logged and does not mark the result.
  • Log entries and markers summarize what is disputed in neutral terms. An unsubstantiated allegation, of gaming or anything else, is never republished.

Example

Disputedopened [date] · link to the dispute log entry

Dispute log

Every dispute that carries material evidence about a result is listed here with its dates, a neutral summary of what was disputed and its outcome. The person who opened it is named only with their consent.

No disputes recorded as of 18 November 2026.

Corrections that come out of disputes also appear in the corrections log.