# OraFabric Medical Ontology Knowledge Base (remote · orafabric.com)

Expert-structured medical ontologies, relationships, and evidence for AI research and reasoning.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `orafabric.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp.md), [page](https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp)

## Channel facts

- Endpoint: `https://orafabric.com/api/dev/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.2`

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

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1124 tokens (~187/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### How do I install the OraFabric Medical Ontology Knowledge Base MCP server?

OraFabric Medical Ontology Knowledge Base is a hosted endpoint at https://orafabric.com/api/dev/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 com-orafabric-medical-ontology 'https://orafabric.com/api/dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-orafabric-medical-ontology": {
      "url": "https://orafabric.com/api/dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-orafabric-medical-ontology": {
      "type": "http",
      "url": "https://orafabric.com/api/dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-orafabric-medical-ontology]
url = "https://orafabric.com/api/dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-orafabric-medical-ontology": {
      "type": "remote",
      "url": "https://orafabric.com/api/dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-orafabric-medical-ontology --url 'https://orafabric.com/api/dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-orafabric-medical-ontology:
    url: "https://orafabric.com/api/dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-orafabric-medical-ontology": {
      "Transport": "http",
      "Url": "https://orafabric.com/api/dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-orafabric-medical-ontology -t streamable-http -u 'https://orafabric.com/api/dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-orafabric-medical-ontology": {
      "type": "http",
      "url": "https://orafabric.com/api/dev/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-21 (score 79, +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.

### 2026-11-19 (score 78, +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.

### 2026-11-17 (score 77, +1)

- [security regression] Authorization: unverified → fail
- [security improvement] Injection markers: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.30

### 2026-11-16 (score 76, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.23 → unverified
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-11-15 (score 76, +1)

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

### 2026-11-13 (score 75, +1)

- [security] Tool “check_relation” rewrote its description, which is the text the model reads

### 2026-11-10 (score 74, +1)

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

### 2026-11-09 (score 73, +3)

- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 35% → 100%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: fair → excellent
- [cosmetic] “check_relation” reworded the description of “both_directions”
- [cosmetic] “check_relation” reworded the description of “filters”
- [cosmetic] “check_relation” reworded the description of “limit”
- [cosmetic] “check_relation” reworded the description of “relation”
- [cosmetic] “explore_concept” reworded the description of “concept”
- [cosmetic] “explore_concept” reworded the description of “direction”
- [cosmetic] “explore_concept” reworded the description of “filters”
- [cosmetic] “explore_concept” reworded the description of “limit”
- [cosmetic] “explore_concept” reworded the description of “relations”
- [cosmetic] “get_paper” reworded the description of “include_findings”
- [cosmetic] “resolve_concept” reworded the description of “limit”
- [cosmetic] “resolve_concept” reworded the description of “name”
- [cosmetic] “resolve_concept” reworded the description of “type”
- [cosmetic] “retrieve_evidence” reworded the description of “filters”
- [cosmetic] “retrieve_evidence” reworded the description of “include_hypotheses”
- [cosmetic] “retrieve_evidence” reworded the description of “max_evidence”

## MCP tools (6)

### `retrieve_evidence` (~197 tokens)

Retrieve evidence

Search the whole knowledge base for a research question. Returns an evidence pack: findings, a subgraph and the papers. $0.03. The model writes the answer.

Input parameters:

- `filters` (object): Narrow the evidence before it is returned. Filtering here is better than filtering the result afterwards, because the retrieval budget is then spent on evidence that qualifies.
- `include_hypotheses` (boolean): Include author interpretations and hypotheses alongside observed findings, returned in a separate bucket. Keep it on when the question is about mechanism; turn it off when you need only what was meas…
- `max_evidence` (integer): How many findings to retrieve. Lower it to around 20 for a narrow factual question; raise it towards 100 when the question spans several mechanisms or you are looking for contradictions, which only a…
- `query` (string, required): The research question, up to 1,000 characters.

### `check_relation` (~245 tokens)

Check relation

Evidence for, against and null on one relationship between two named things. $0.03. A finding is returned only when one end matches the subject and the other matches the object. If a name matches several concepts, results include all of them and notices lists their ids.

Input parameters:

- `both_directions` (boolean): Also return evidence for the reverse relationship, object acting on subject. Set it when the direction of causation is itself the question, because the literature often reports both.
- `filters` (object): Narrow the evidence before it is returned. Filtering here is better than filtering the result afterwards, because the retrieval budget is then spent on evidence that qualifies.
- `limit` (integer): How many findings to return per bucket. Raise it for a well-studied pair where 20 may only surface the most recent work.
- `object` (string, required): The thing acted on.
- `relation` (string): The specific claim to test. Use 'any' unless the question names a direction of effect. 'any' returns supporting, contradicting and null evidence across all relation types, which is usually more infor…
- `subject` (string, required): The acting thing.

### `explore_concept` (~291 tokens)

Explore concept

What is known around one gene, drug or disease: upstream, downstream and associations. $0.03.

Input parameters:

- `concept` (string, required): One gene, drug or disease to walk outward from. A single entity, not a question. Use retrieve_evidence for a question. If the name may be ambiguous, resolve it first with the free resolve_concept.
- `direction` (string): Which way to walk. 'downstream' returns what this concept acts on: what it causes, inhibits or treats. 'upstream' returns what acts on it: what regulates, inhibits or induces it. 'both' returns each…
- `filters` (object): Narrow the evidence before it is returned. Filtering here is better than filtering the result afterwards, because the retrieval budget is then spent on evidence that qualifies.
- `limit` (integer): How many relationships to return per direction. Raise it for a hub concept such as TP53 or EGFR, where 20 will only show the most common edges.
- `relations` (array): Restrict the walk to these relation types. Use it when the question is about one kind of link, ['inhibits','activates'] for regulation, ['treats','prevents'] for therapeutic claims. Leaving it unset…

### `get_paper` (~92 tokens)

Get paper

One paper and the findings extracted from it. Does not return the article text. $0.03.

Input parameters:

- `id` (string, required): A paper_id from an earlier result, a PMID or a DOI.
- `include_findings` (boolean): Return the findings extracted from this paper, not only its metadata. Turn it off when you only need the title, journal and year, for example when rendering a citation.

### `resolve_concept` (~163 tokens)

Resolve concept

Match a name, abbreviation or synonym to standard concepts. Free.

Input parameters:

- `limit` (integer): How many candidate concepts to return. Raise it when the name is a common abbreviation likely to collide; 5 is enough for a specific name.
- `name` (string, required): The name, abbreviation or synonym to resolve, as it appeared in the question. Do not normalise it first. 'HER2', 'ERBB2' and 'Her-2/neu' are all valid input.
- `type` (string): Restrict to concepts of this kind. Set it when the name is ambiguous across kinds. 'CD20' is both a gene and a drug target, 'ALK' is a gene and a disease qualifier. Leave unset to see every kind.

### `get_coverage` (~27 tokens)

Get coverage

What the knowledge base currently covers: datasets, concepts and relationships. Free. No arguments.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 76
- 2026-11-15: 76
- 2026-11-14: 75
- 2026-11-13: 75
- 2026-11-12: 74
- 2026-11-11: 74
- 2026-11-10: 74
- 2026-11-09: 73
- 2026-11-08: 70
- 2026-11-07: 36
- 2026-11-06: 36

## Common questions

### What is the OraFabric Medical Ontology Knowledge Base MCP server?

OraFabric Medical Ontology Knowledge Base is an MCP server listed in the public MCP registry as com.orafabric/medical-ontology. Expert-structured medical ontologies, relationships, and evidence for AI research and reasoning. This page covers its hosted endpoint (https://orafabric.com/api/dev/mcp).

### Is the OraFabric Medical Ontology Knowledge Base MCP server safe to use?

OraFabric Medical Ontology Knowledge Base scores 79 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 OraFabric Medical Ontology Knowledge Base MCP server expose?

OraFabric Medical Ontology Knowledge Base exposes 6 tools: retrieve_evidence, check_relation, explore_concept, get_paper, resolve_concept, get_coverage. Their descriptions and schemas cost roughly 1,015 tokens of context every time the server is loaded.

### Does the OraFabric Medical Ontology Knowledge Base MCP server require authentication?

Yes. OraFabric Medical Ontology Knowledge Base asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the OraFabric Medical Ontology Knowledge Base MCP server still maintained?

OraFabric Medical Ontology Knowledge Base 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 OraFabric Medical Ontology Knowledge Base MCP server?

VerifyMCP ran 13 checks on OraFabric Medical Ontology Knowledge Base, 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://orafabric.com/api/dev/mcp
- Authorisation metadata: https://orafabric.com/.well-known/oauth-protected-resource/api/dev/mcp
- Repository: https://github.com/OraFabric/medical-ontology-mcp-examples
- Website: https://orafabric.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-orafabric-medical-ontology/api-dev-mcp
