Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Moyne Ross

REMOTE · MCP.MOYNEROSS.COM

Moyne Ross research on commercial property capital, and a technical library of building elements.

+3 this week 81 Trust /100

Last scanned (17 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 17385 tokens (~102/item across 170 items; 14 tools + 156 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

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

  • 19 Nov 26 +1

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

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: pass → fail ▼ functional
    • First check of Capabilities: pass functional
    • New tool “building_brief” functional
    • New tool “compare_technical_sections” functional
    • New tool “trace_connections” functional
    • New tool “translate_term” functional
  • 13 Nov 26 +1

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

  • 12 Nov 26 0
    • Tool “get_technical_page” rewrote its description, which is the text the model reads security
    • “get_technical_page” added an optional parameter “market” cosmetic
  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_technical_page” rewrote its description, which is the text the model reads security
    • “get_technical_page” added an optional parameter “cursor” cosmetic
    • “get_technical_page” reworded the description of “format” cosmetic
  • 10 Nov 26 +1
    • “get_technical_page” reworded the description of “section” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.moyneross.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.moyneross.com CN=YR2,O=Let's Encrypt,C=US 7 Nov 2026 5 Feb 2027 RSA 2048 SHA256-RSA 699002c2950eb09865fe29ca758c686b0e2
SANs: mcp.moyneross.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.moyneross.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
moyneross.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.moyneross.com/mcp Verified 200
http (plaintext) http://mcp.moyneross.com/mcp HTTPS enforced 308 https://mcp.moyneross.com/mcp
MCP tools · 14 exposed · ~2,761 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
building_brief ~343

For a kind of building (commercial, industrial, institutional or residential-multi), the Technical Library's map of what a capital strategy looks at: its functional spaces, and the building elements in play, a page at a time in framework order, each with a link to its service life (every page also grades findings at #severity), how many measured thresholds each market has on it, and the papers that reason from it. Narrow it to the elements serving named spaces (plant rooms, loading docks, wet areas), to one framework section, or count one market's thresholds. General: it describes what such a building turns on, never the condition, cost or needs of a particular building.

NameTypeReqDescription
cursorstring–nextCursor from a previous call, for the next page of elements.
framework_sectionstring–Only elements in one framework section, e.g. Roofs, Mechanical Services, Fire Services. Matches on part of the name.
limitinteger––
marketstring–AU, UK or US: count that market's measured thresholds on each element. Without it, every market is counted.
response_formatstring–concise (default): each element's name, links, threshold counts and grounding papers. detailed: adds its short answer.
spacesarray–Only the elements serving these functional spaces, by slug or name, e.g. plant-rooms, loading-docks, bathrooms-and-wet-areas. Leave out for the whole building.
use_classstringyesThe kind of building: commercial, industrial, institutional or residential-multi (apartments, strata, mixed-use residential).
NameTypeReqDescription
boundarystringyes–
corpusVersionstringyes–
countintegeryes–
elementsarrayyes–
frameworkSectionsarrayyes–
market–yes–
nextCursorstring|nullyes–
spacesarrayyes–
totalintegeryes–
unknownSpacesarrayyes–
useClassstringyes–

No examples provided.

cite_paper ~131

Return an exact citation for a Capital Made Physical paper or a Technical Library page, optionally to one section, in BibTeX, RIS, CSL-JSON, APA or Harvard. Use the formatted text as given rather than retyping it.

NameTypeReqDescription
paperstringyesA Capital Made Physical paper (slug, CMP number or URL) or a Technical Library page (slug, element name or URL).
sectionstring–A section heading or its anchor, e.g. "a second income line".
stylestring–bibtex, ris, csl-json, apa or harvard.
NameTypeReqDescription
citationobjectyes–
formattedstringyes–
stylestringyes–

No examples provided.

compare_technical_sections ~212

Set one section side by side across two to five Technical Library pages: service life, severity grading, what to ask for, common misreads, remedies, the shape of the cost and more, or thresholds for the measured values by market (one market with market, otherwise every market labelled, with the rule that a value applies only in its own market). Each section comes with its anchored URL; a long section is shortened and marked truncated. General guidance on how elements behave, never evidence about a particular building.

NameTypeReqDescription
marketstring–With section thresholds: that market's values only. Without it, every market's values, each labelled.
pagesarrayyesTwo to five Technical Library pages, by slug, element name or URL.
sectionstringyesThe section to set side by side: service-life, severity, what-to-ask-for, misreads, remedies, cost-shape, investigation, jurisdiction-notes and the rest, or thresholds for the measured values by mark…
NameTypeReqDescription
corpusVersionstringyes–
market–yes–
pagesarrayyes–
policystring––
sectionstringyes–
unknownarrayyes–

No examples provided.

explain_method ~128

Explain the Capital Register (the line-by-line capital document behind every Capital Strategy) or the MR Index (the MR 1 to MR 5 reading of how much attention a building needs, and how soon), from the public methodology pages. By default the definition and the list of sections; format full gives the whole page, section gives one part.

NameTypeReqDescription
formatstring–summary (default): the definition and section list. full: the whole page.
methodstringyescapital-register or mr-index.
sectionstring–One section of the method page, by heading.
NameTypeReqDescription
methodobjectyes–

No examples provided.

get_paper ~155

Retrieve one Capital Made Physical paper by slug, CMP number or canonical URL. By default a summary: the question it answers, its short answer, summary, limitations and its sections with anchored URLs. format full adds the complete text; section returns one section. Always includes a ready citation. Carry the limitations through when relying on it.

NameTypeReqDescription
formatstring–summary (default): question, answer, summary, limitations and section list. full: adds the complete text.
paperstringyesThe paper: its slug (after-rent), CMP number (CMP 024 or 24) or canonical URL.
sectionstring–A section heading or its anchor, e.g. "a second income line".
NameTypeReqDescription
citationobjectyes–
paperobjectyes–
section–yes–

No examples provided.

get_sample_strategy ~160

Read the sample Moyne Ross Capital Strategy, a real strategy for an industrial warehouse and office with identifying details changed, to see what such a strategy contains. part summary (default): the ten-year figures, MR Index, executive summary and where the capital sits. part register: an overview of the Capital Register by section, or, with section (e.g. roofs), that section's lines with condition, action, timing, cost and cost basis.

NameTypeReqDescription
partstring–summary (figures, executive summary, key considerations, where the capital sits, how sure) or register.
sectionstring–With part register: one register section, e.g. roofs, fire, mechanical. Without it, register returns an overview by section.
NameTypeReqDescription
sampleobjectyes–

No examples provided.

get_technical_page ~439

Retrieve one Technical Library page by slug, element name or canonical URL: general technical guidance on how a building element or functional space is built, its service life, how it fails, what to look for, how to tell causes apart, how serious a finding is (graded safety, failure, condition, lifecycle, deadline, check or nil), investigation, remedies, the shape of the cost (never a price), standards in Australia, the UK and the US, measured thresholds by market, and what to ask the owner or agent for. Each threshold applies only in its own market: pass market (AU, UK or US) for the building in question to get that market's values alone; section thresholds returns the values on their own. By default a summary with every section's anchored URL; section returns one section, format full the whole page (a part at a time on a long page, with nextCursor). Always includes a ready citation. It describes how elements behave in general, never the condition of a particular building; carry its limitations through.

NameTypeReqDescription
cursorstring–With format full on a long page: the nextCursor from the previous part.
formatstring–summary (default): the question, short answer, where it applies, limitations, sources and the anchored sections. full: adds the complete text, a part at a time on a long page.
marketstring–The market of the building the answer is for: AU (Australia), UK or US. Returns that market's measured thresholds only. Without it, thresholds come grouped by market, each labelled, with the rule for…
pagestringyesThe Technical Library page: its slug (masonry-brickwork), element name (Roof Coverings) or canonical URL.
sectionstring–One section, by the id or heading the page summary lists, e.g. severity (how serious), service-life, what-to-ask-for, jurisdiction-notes (standards by country). Earlier addresses such as diagnosis or…
NameTypeReqDescription
citationobjectyes–
pageobjectyes–
partobject––
section–yes–

No examples provided.

list_papers ~110

List the Capital Made Physical papers in reading order, a page at a time, optionally for one of the seven parts (I to VII). Returns each paper's number, title, part, question, short answer, dates and canonical URL, and nextCursor for the next page.

NameTypeReqDescription
cursorstring–nextCursor from a previous call, for the next page.
limitinteger––
partstring–Only papers in this part of Capital Made Physical, I to VII.
NameTypeReqDescription
corpusVersionstringyes–
countintegeryes–
nextCursorstring|nullyes–
papersarrayyes–
totalintegeryes–

No examples provided.

list_technical_pages ~188

List the Moyne Ross Technical Library: one page for each building element and functional space a Capital Strategy assesses, in the order of the Building Check Framework (Substructure to Environmental), a page at a time, optionally for one section or page type. Returns each page's title, section, short answer and canonical URL, the framework sections, the severity scale every page grades findings on, and nextCursor for the next page.

NameTypeReqDescription
cursorstring–nextCursor from a previous call, for the next page.
limitinteger––
page_typestring–element (a building element, judged on condition) or space (a functional space, judged on whether it does its job).
sectionstring–Only pages in one framework section, e.g. Façades, Roofs, Mechanical Services, Fire Services. Matches on part of the name.
NameTypeReqDescription
corpusVersionstringyes–
countintegeryes–
nextCursorstring|nullyes–
pagesarrayyes–
sectionsarrayyes–
severityScaleobjectyes–
totalintegeryes–

No examples provided.

search_research ~295

Search the public Moyne Ross corpus on commercial property and capital: 49 Capital Made Physical papers, the Technical Library (103 pages on building elements and functional spaces: how each fails, what to look for, how serious a finding is, remedies), the Capital Register and MR Index methodology, and a sample Capital Strategy. Use for capital planning, lifecycle and condition, obsolescence, refurbish or redevelop, energy and solar, leases and make good, due diligence, the Australian, British and US markets, and for how a building element or system fails and is judged. For a question about one element or system (a roof, a façade, a chiller, lifts, fire services), scope technical searches the library alone. Returns ranked results with canonical URLs and a match strength with the matched and missing words; when the match is weak, the results are background only. General research: it does not assess a particular building.

NameTypeReqDescription
limitinteger––
querystringyesThe question or topic, in plain words. Practitioner shorthand (capex, dilaps, MEES, TDD) is understood.
response_formatstring–concise (default): title, URL and short answer per result. detailed: adds the citation, part and dates.
scopestring–all, research (the papers), technical (the Technical Library: building elements and spaces), methodology, or sample.
NameTypeReqDescription
boundarystringyes–
corpusVersionstringyes–
countintegeryes–
matchobjectyes–
matchStrengthstringyes–
querystringyes–
resultsarrayyes–
scopestringyes–
suggestedQueriesarrayyes–

No examples provided.

start_strategy_link ~153

Returns a link to the Moyne Ross request form for one actual commercial or multi-unit building, with the details the person has given filled in. Use only when the person asks to request a Capital Strategy, and only with details they have provided. Nothing is sent: the person opens the link, checks the form and sends it themselves.

NameTypeReqDescription
buildingstringyesThe building: street address, suburb or city, and state.
emailstring––
namestring––
notestring–Anything the person would like Moyne Ross to know, briefly.
organisationstring––
rolestring––
typestring–The kind of building.
NameTypeReqDescription
linkstringyes–
nextstringyes–

No examples provided.

trace_connections ~142

Follow the links between the Capital Made Physical papers and the Technical Library. From a paper: the library pages it reasons from (each with the section and why), and the other papers that rest on the same ground, most shared first. From a library page: the papers grounded in it and why, its related pages, and the spaces an element serves or the elements a space holds. Exact links, not a search: use it to see what an argument rests on, or everything that turns on one element.

NameTypeReqDescription
refstringyesA paper (slug, CMP number or URL) or a Technical Library page (slug, element or space name, or URL).
NameTypeReqDescription
corpusVersionstringyes–
elementsarrayyes–
fromobjectyes–
groundedPapersarrayyes–
relatedarrayyes–
restsOnarrayyes–
sharesGroundWitharrayyes–
spacesarrayyes–

No examples provided.

translate_term ~228

What a building element, lease term, code or report is called in Australia, the United Kingdom and the United States, from the Moyne Ross glossary: lift and elevator, make good and dilapidations, downpipe and downspout, strata and condominium, NCC and IBC. Give the term in any market's wording. Returns each matching entry with all three markets' terms, a note where the markets use different instruments rather than different words, and the Technical Library pages that cover it. match says how close the entry is: exact, close, loose or none. Use it to put a question into the right market's words before searching, or to answer "what is X called in Y". These are everyday professional equivalents, not legal definitions.

NameTypeReqDescription
marketstring–The market the answer is for: AU, UK or US. Its term is listed first. All three are always returned.
termstringyesThe term to look up, in any market's wording: "elevator", "dilapidations", "sarking", "certificate of occupancy".
NameTypeReqDescription
boundarystringyes–
corpusVersionstringyes–
countintegeryes–
glossaryUrlstringyes–
market–yes–
matchstringyes–
matchesarrayyes–
termstringyes–

No examples provided.

working_with_moyne_ross ~77

Factual information on how Moyne Ross engagements work: who it works with and where (commercial and multi-unit property in Australia, the United Kingdom and the United States), the three stages, the published terms on which a Capital Strategy is released, and common questions. Use when the person asks about engaging Moyne Ross.

Input schema present but exposes no named parameters.

NameTypeReqDescription
textstringyes–
urlstringyes–

No examples provided.

Install

How do I install the Moyne Ross MCP server?

Moyne Ross is a hosted endpoint at https://mcp.moyneross.com/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.

remote · mcp.moyneross.com

# add to Claude Code
claude mcp add --transport http steven3265-moyneross 'https://mcp.moyneross.com/mcp'
Common questions

What is the Moyne Ross MCP server?

Moyne Ross is an MCP server listed in the public MCP registry as io.github.Steven3265/moyneross. Moyne Ross research on commercial property capital, and a technical library of building elements. This page covers its hosted endpoint (https://mcp.moyneross.com/mcp).

Is the Moyne Ross MCP server safe to use?

Moyne Ross scores 81 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 Moyne Ross MCP server expose?

Moyne Ross exposes 14 tools: search_research, list_papers, get_paper, explain_method, get_sample_strategy, and 9 more. Their descriptions and schemas cost roughly 2,761 tokens of context every time the server is loaded.

Does the Moyne Ross MCP server require authentication?

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

Is the Moyne Ross MCP server still maintained?

Moyne Ross is still listed as active in the MCP registry. We last reached this channel on 21 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 Moyne Ross MCP server?

VerifyMCP ran 14 checks on Moyne Ross, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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.