Moyne Ross MCP

Moyne Ross research on commercial property and capital, served over the Model Context Protocol. A connected assistant can search and cite Capital Made Physical (49 papers on what commercial property is becoming) and the Technical Library (103 pages, one for each building element and functional space a Capital Strategy assesses: how it fails, what to look for, how serious a finding is, what fixes it), explain the Capital Register and the MR Index, read a sample Capital Strategy, and, for one actual building, hand the person to the Moyne Ross Start your strategy form already filled in.

Public, read-only, and separate from every client system. The server bundles a snapshot of public files from moyneross.com; it has no route to the Moyne Ross portal, client strategies, payments or any database.

Version: 1.1.0 · Protocol: MCP 2026-07-28, with stateless 2025-era compatibility · Endpoint: https://mcp.moyneross.com/mcp · Registry: io.github.Steven3265/moyneross · For assistants: moyneross.com/assistants

Connect

Related MCP server: INDUSS Research Intelligence MCP Server

Tools

Every tool is read-only, with all four annotations set explicitly, input and output schemas, and icons. Prompts: answer_from_research, compare_papers (with paper autocompletion), brief_on_topic and read_a_building_element (with library autocompletion). Resources: moyneross://catalogue, the templates moyneross://papers/{slug} and moyneross://technical/{slug} (with autocompletion), moyneross://methods/{capital-register|mr-index} and moyneross://sample. Results link to them with resource_link blocks.

Built for every assistant's limits

Default answers stay under 20,000 characters (GitHub Copilot keeps them inline), every answer's text under 40,000 (Gemini CLI's truncation point), and the tools that can return a full paper declare anthropic/maxResultSizeChars so Claude Code keeps them inline too. Summaries come first; sections, full text and the register's lines are one argument away.

Citations that survive

The papers have 400 anchored sections between them and the library 1,133, matching the anchors on moyneross.com, so a claim can be cited to the exact section. Citations carry the corpus version (for example 2026-11-08.70433cca: date and content fingerprint), so the cited text can always be identified.

Other interfaces

• REST: GET /v1/search, /v1/papers, /v1/paper, /v1/technical, /v1/method, /v1/sample, /v1/cite, /v1/engage (OpenAPI 3.1). Answers carry the clean canonical URL to cite and a separate attributed referralUrl.

• Server card: /mcp/server-card · Service metadata: /server-card.json · Health and content fingerprint: /health

• Packaging: Claude plugin (.claude-plugin/, .mcp.json), GitHub Copilot (.github/plugin/), agent-plugins (plugin.json, mcp.json), Gemini (gemini-extension.json), the OpenAI submission package (distribution/openai/) and the GitHub Agent Finder pack (distribution/github-agentfinder/).

• Skills: skills/commercial-capital-research and skills/capital-strategy-handover, also served at https://mcp.moyneross.com/skills/{name}/SKILL.md (npm run sync:skills keeps the copies identical).

• Docs: tool contract · protocol support · security · benchmark · architecture · deployment · content terms · security contact at /.well-known/security.txt

How it stays right

• One corpus, three readers. The snapshot is built from files the website's own publishing scripts produce (/insights/export.json, /insights/search-index.json, /technical/export.json, /llms.txt, the methodology and sample pages). The ranking of the papers, methodology and sample is a faithful port of the website's public retrieval benchmark, on the website's own statistics, so the benchmark, the site search and this server rank them alike; library pages are scored beside them (see docs/BENCHMARK.md).

• Deterministic snapshot. data/corpus.json is dated from the content (the latest sitemap date), never the clock. A daily workflow rebuilds it and opens a pull request only when moyneross.com has actually changed.

• Checked on every change (npm run check): release metadata (including the Agent Skills and Agent Plugins rules); skill copies; snapshot validation (structure, no secrets, none of the sample's real identifiers); 27 core tests; three retrieval benchmarks (the website's 56 allocator questions: all in the top three and strong; 24 questions in practitioners' shorthand: 23 in the top three, 22 strong; 26 building-element questions: all in the top three with scope: technical, 24 unscoped); the protocol suite (2026-07-28 cache fields, ordering, result metadata and error codes; annotations, icons and size ceilings on every tool; prompts and completion; neutral answers on every surface; research only on the OpenAI surface); the REST suite; and per-client answer-size budgets, hostile input and speed. The official MCP conformance suite runs in its own workflow (25 live checks). Each release is a GitHub Release with a CycloneDX SBOM.

Boundaries and privacy

The research and the Technical Library are general; the library describes how elements behave and carries no prices. A Capital Strategy is desk-based and reviewed by Moyne Ross before release; it is not an inspection, a valuation or a guarantee of cost. The server cannot assess a building, order anything, access client data or modify any system.

Telemetry is operational only: protocol method, tool name, query length, scope, counts, match strength, a coarse client family, outcome and duration. Questions, addresses, names, emails and IP addresses are not logged by the application. Privacy: moyneross.com/privacy#connector.

Develop

npm ci
npm run snapshot        # rebuild data/corpus.json from moyneross.com
# or, from a local build of the website (canonical URLs stay on moyneross.com):
# MOYNEROSS_FETCH_FROM=http://127.0.0.1:8765 npm run snapshot
npm run check           # everything
npm run start:stdio     # run over stdio

Licence: MIT for the server code. The content is not MIT licensed; see data/TERMS.md.