OraFabric Medical Ontology Knowledge Base
com.orafabricPublished by orafabric.comOfficial publisherv1.0.1Updated Nov 6, 2026
Expert-structured medical ontologies, relationships, and evidence for AI research and reasoning.
Overview
Remote MCP endpoint giving assistants expert-structured medical ontologies, relationships and evidence for research and reasoning.
- What you can do
- No tool list is published, so capabilities are inferred from the description.
- Provides access to expert-structured medical ontologies and the relationships between their concepts.
- Supplies supporting evidence intended for AI research and reasoning tasks.
- Connects over a hosted streamable HTTP endpoint rather than a local package.
- When to use it
- Consider it when an assistant needs structured medical terminology, concept relationships or supporting evidence for research, literature work or clinical-domain reasoning, and you are willing to use a hosted third-party service.
- Requirements
- A remote streamable HTTP endpoint at the provider's domain; no local runtime or package is needed. Authentication is OAuth and required: an Authorization header carrying a bearer API key from the provider's developer console.
Installation
In SourceWeft
- Open OraFabric Medical Ontology Knowledge Base in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.orafabric%2Fmedical-ontology/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"orafabric-medical-ontology-knowledge-bas": {
"type": "http",
"url": "https://orafabric.com/api/dev/mcp"
}
}
}Tools
0Version history
1- v1.0.1LatestNov 6, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.
