Skip to content
Agentmart
Submit a tool

FORRT Research

Produce verifiable FORRT nanopublication chains: grounded quote checks and Science Live projections.

Connector by sciencelive4all.org · Domain verified by the MCP Registry

IndexedMITLocal (stdio)
Write a review

Install

Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.

npx agentmarket install connector/sciencelive4all-org-forrt-research-mcp

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Produce verifiable FORRT nanopublication chains: grounded quote checks and Science Live projections.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools
7 read · 1 write · 0 delete · 5 not yet classified
Secrets
1 (API keys, tokens or passwords)
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 13

Read from the source code; the running server may list different tools.

Read 7 · Look things up without changing anything.

  • list_schemas
  • validate_chain_draft
  • validate_draft
  • validate_drafts
  • verify_chain
  • verify_quote
  • wikidata_lookup

Write 1 · Create, change, send or run things.

  • resolve_doi

Not yet classified 5 · We could not tell from the name and description.

  • constellation
  • constellation_raw
  • prior_work
  • template_fields
  • vocabulary

Secrets and settings it asks for

Secrets: values you paste in that let it act as you.

  • SCIENCELIVE_API_KEY

Other settings (environment variables or headers).

  • SCIENCELIVE_API_BASE

Files it touches

  • Any path the agent passes to its tools

Tools (13)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • constellation

    The FORRT chain(s) reachable from a published nanopub URI, as a compact projection you can actually read. Call this to see an existing chain — before starting a replication (what has already been done?), when extending someone else's chain, or to inspect your own after publishing. The raw Science Live constellation is ~330 KB for one chain, of which ~95 % is a depth-5 neighbourhood of UNRELATED chains reachable through shared links (on the marine-heatwave chain, 64 of 98 nodes are other studies' AIDA statements). This returns the chains, the apex CiTO, any Research Synthesis, and the Quote/Q…

  • constellation_raw

    The unprojected `/np/constellation` response, including every node and edge. For debugging the graph itself or investigating an upstream data problem. Prefer `constellation` for normal use: this is very large (~330 KB for a single chain) and most of it belongs to other studies. Lower `depth` to shrink the walk.

  • list_schemas

    Which chain steps and vocabularies this server can look up. Cheap, offline, and no network. Call it first if you are unsure what to pass to `template_fields` or `vocabulary`.

  • prior_work

    What has already been claimed about a paper — the starting point for new work, whether that work is a replication or a fresh study. Given any published nanopub URI in a constellation, returns one entry per completed chain: the claim type, what was tested (`scope`), how (`method`), what was done differently (`deviations`), the verdict and confidence, and — the field to read most carefully — `limitations`, where the previous authors stated in their own signed words what their study did NOT cover. Use it to avoid duplicating an existing replication, to choose a CiTO relation relative to prior w…

  • resolve_doi

    Does this DOI resolve, and to what? Call it on every DOI destined for a nanopub field, `CITATION.cff`, or a CiTO citation. `resolves: false` means the DOI is not registered — do not publish it, however well-formed it looks. A well-formed DOI is not a real one, and a fabricated one is indistinguishable from a genuine one until something asks the registry. On success it returns the registered title, authors, year, container and type, so you can confirm it is the paper you mean rather than merely a paper that exists. Accepts bare (`10.…`), URL, or `doi:`-prefixed forms.

  • template_fields

    The exact form fields of one FORRT chain step, from the live template. Call this BEFORE drafting any nanopub field. A nanopub template *is* the schema for its step, so this is what makes "never invent a field name" a lookup rather than a rule you have to remember: it returns the real field ids, prompts, whether each is required or repeatable, the length/format constraints (`regex`, `prefix`, `datatype` — where the Quote template's character cap actually lives), and, for choice fields, the allowed values. `step` accepts `05_outcome`, `05`, or `outcome`. Known steps: 01_quote, 01_pico, 01_pcc,…

  • validate_chain_draft

    Check `nanopubs/chain-draft.json` before handing it to the chain wizard. Run this at the end of Phase 5b, after `pixi run build-chain-draft` and BEFORE pushing the file and opening the wizard URL. `readyForWizard` is true only when nothing came back as an error. This file — not the markdown drafts — is what the wizard pre-fills each step from, and therefore what a human reviews and signs. `validate_draft` checks the authoring input; this checks the artifact. What it catches that reading the file cannot: - a **superseded `template_uri`**, which is invisible in the JSON but makes the wi…

  • validate_draft

    Check one drafted nanopub against its template and the real world. Run this on every draft before publishing. It is the pre-flight checklist in `docs/forrt-form-fields.md`, actually executed: field ids checked against the live template, choice values against the template's own enumeration, length caps against its regex, DOIs against the registry, Wikidata QIDs against Wikidata. `publishable` is true only when there are no errors. Severities: error would publish something false, or be rejected by the form warning a human should look, but it may be intentional info checked and f…

  • validate_drafts

    Check every draft in a `nanopubs/drafts/` directory at once. The whole-chain pre-flight: run it before starting Phase 5b, and again before announcing. Returns per-draft results plus totals, with `publishable` true only when no draft has an error. Note what it cannot see: values a draft puts in prose or a markdown table rather than behind a `<!-- field: … -->` marker are reported as `coverage` warnings, not as missing. The CiTO step's citation list is the known case.

  • verify_chain

    Verify a published FORRT chain. Run this before announcing it anywhere. Point it at a `nanopubs/PUBLISHED.md` ledger (or the directory holding one). Read-only: it never edits, retracts or supersedes — a failing row is for a human to act on. `green` is true only when nothing failed. What it checks: - every required step (01-06) has a URI in the ledger; - every URI is really published — present in the constellation, or, for the upstream anchors the walk does not reach, served as RDF by the `w3id.org/np/` resolver; - the Outcome's repository resolves (a Zenodo **version** DOI is t…

  • verify_quote

    Prove that a candidate quotation is really in a source PDF, before it is published as verbatim. Call this on EVERY quotation destined for a Quote-with-comment nanopub. You choose which sentence carries the paper's claim — that is judgement. This decides whether the sentence is admissible, and that is not: it is a string search, and anyone can re-run it and get the same answer. Returns a graded verdict with the page, character offsets and the file's SHA-256 as evidence: exact byte-identical to the extracted page text normalized matched after whitespace / ligature…

  • vocabulary

    The allowed values of a FORRT controlled vocabulary, from its template. Use it whenever a draft needs a claim type, a study type, a validation status, a confidence level, or a CiTO relation. Every term comes from the real restricted-choice field on the real template (or the value-list nanopub it points at), so a value returned here is one the form will actually accept — and nothing else is. Names: claim_type, study_type, validation_status, confidence_level, cito_relation, pico_question_type. Three worth reading before you draft: - `study_type` carries the Reproduction vs Replication disti…

  • wikidata_lookup

    Find real Wikidata items for a term, and type-check them. Call it for every Wikidata topic or keyword destined for a nanopub field. It returns candidates with their descriptions and real P31/P279 types; it deliberately does NOT choose one, because picking the right sense of an ambiguous label is a judgement. What it guarantees is that the QID you publish exists and is what you say it is. Pass `expected_type` as a QID (e.g. `Q16521` taxon, `Q11862829` academic discipline) and each candidate is marked `typeMatches` from its actual statements. Candidates are annotated, never filtered — a near m…

Signals

Stars
0
Forks
0
Open issues
2
Weekly downloads
39
Last commit
Sep 21, 2026 (1 month ago)
Last release
Oct 25, 2026 (4 days ago)
Last package publish
Sep 21, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
org.sciencelive4all/forrt-research-mcp
Version
0.2.0
Auth
API key
Packages
pypi forrt-research-mcp
License
MIT
First seen
Oct 24, 2026
Last checked
Oct 26, 2026

More from sciencelive4all.org

Cite this page

FORRT Research MCP server. Agent Mart. https://agentmart.dev/connectors/sciencelive4all-org-forrt-research-mcp (last updated 2026-10-26)