ontoloom
Health Pass
- License — License: BSD-3-Clause
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Community trust — 15 GitHub stars
Code Pass
- Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Pass
- Permissions — No dangerous permissions requested
This tool is a Hybrid-Driven Reasoning Architecture (HyDRA) that acts as an MCP server for building and exploring OWL 2 ontologies. It uses an AI persona committee approach to help developers generate domain-specific ontologies and knowledge graphs.
Security Assessment
Overall Risk: Low. The automated code scan checked 12 files and found no dangerous patterns, hardcoded secrets, or requests for dangerous permissions. Because it relies on the SymbolicAI framework, users must provide their own API keys via a local configuration file, meaning no sensitive credentials are exposed in the codebase. As an AI-driven ontology generator, the tool inherently makes outbound network requests to LLM APIs to process data. It does not appear to execute hidden or unauthorized shell commands.
Quality Assessment
The project is actively maintained, with its most recent code push occurring just today. It uses the highly permissive and standard BSD-3-Clause license, making it safe for integration into commercial and personal projects. While the community trust footprint is currently small (15 GitHub stars), the repository is well-documented and offers clear setup instructions.
Verdict
Safe to use: a well-documented, permissively licensed AI tool with a clean code scan and no apparent security risks.
MCP server for building and exploring OWL 2 ontologies with AI agents.
ontoloom
MCP tools for building and exploring OWL 2 ontologies with AI agents.
ontoloom is an MCP server for working with OWL 2 EL ontologies. Each ontology is a single SQLite file. Axioms are typed and validated at the API boundary, and identity is a content hash so duplicates can't slip in.
Example
A coding agent sketching a tiny solar-system ontology:
create_ontology(path="solar.ontology.db")
Created ontology at `solar.ontology.db`.
set_prefix(path="solar.ontology.db", name="sol", iri="http://example.org/solar-system#")
Set prefix `sol:` -> `http://example.org/solar-system#`
add_axioms(path="solar.ontology.db", axioms=[...])
Added 6 axioms, skipped 0 axioms.
```diff
+ [bb5496d24bd1] SubClassOf(sol:Star, sol:CelestialBody)
+ [f3b454b634a3] SubClassOf(sol:Planet, sol:CelestialBody)
+ [e4e965a69712] SubClassOf(sol:Moon, sol:CelestialBody)
+ [3f335b35490c] SubClassOf(sol:TerrestrialPlanet, sol:Planet)
+ [7bc195f4d6a6] SubClassOf(sol:Planet, ObjectSomeValuesFrom(sol:orbits, sol:Star))
+ [f3de1afbfd6c] SubClassOf(sol:Moon, ObjectSomeValuesFrom(sol:orbits, sol:Planet))
```
Now the agent queries the structure. match_axioms does structural pattern matching with ?vars - same variable in two positions enforces equality, and every solution comes back as a saved selection:
match_axioms(path="solar.ontology.db",
pattern={"sub_class": "?body",
"super_class": {"property": "sol:orbits", "filler": "?center"}},
into="orbits")
Saved 2 axioms to "orbits".
[7bc195f4d6a6] SubClassOf(sol:Planet, ObjectSomeValuesFrom(sol:orbits, sol:Star))
[f3de1afbfd6c] SubClassOf(sol:Moon, ObjectSomeValuesFrom(sol:orbits, sol:Planet))
Selections persist across calls and compose. A second match picks up everything asserted about Planet on the LHS; create_selection then intersects the two to find the axiom that's both about Planet and describes an orbital relationship:
match_axioms(path="solar.ontology.db",
pattern={"sub_class": "sol:Planet", "super_class": "?super"},
into="planet_facts")
Saved 2 axioms to "planet_facts".
[7bc195f4d6a6] SubClassOf(sol:Planet, ObjectSomeValuesFrom(sol:orbits, sol:Star))
[f3b454b634a3] SubClassOf(sol:Planet, sol:CelestialBody)
create_selection(path="solar.ontology.db",
name="planet_orbit",
expr={"intersect": ["orbits", "planet_facts"]})
Saved 1 axiom to "planet_orbit".
[7bc195f4d6a6] SubClassOf(sol:Planet, ObjectSomeValuesFrom(sol:orbits, sol:Star))
What you can do with it
- Build an ontology from scratch by talking to an agent
- Poke around an existing one: search by text or structure, inspect entities
- Hand an agent an existing ontology and ask it to clean up or extend
- Dump everything to JSONL for sharing or archival
- Manage prefix mappings and axiom-level annotations
Tools
Setupcreate_ontology | set_prefix | remove_prefix
Build
add_axioms- add validated axioms; duplicates are skippedremove_axioms- remove by hash or by axiom selectionannotate_axiom- change axiom-level annotations without touching identityreplace_axiom- atomic delete + add for one axiomrename_iri- rewrite an IRI across all (or scoped) axioms
Query
describe_ontology- entity and axiom counts, top entities, prefix mappingsget_entity- roles, annotations, and asserted axiom counts for one entityfind_entities- text search, optionally filtered by role or namespacefind_axioms- text search on axiom-level annotationsfind_duplicate_entities- entities sharing the same value for an annotation propertymatch_axioms- structural pattern matching with?varsand*wildcards
Selections - named, persistent sets of axiom hashes or entity IRIs
create_selection- build from set algebra over existing selectionsread_selection- paginated view with present/missing visibilitylist_selections- show all named selectionsremove_selections- drop one or more selections
Exportexport_jsonl - dump all axioms to a sorted JSONL file
Getting started
Requires Python 3.12 and uv.
git clone [email protected]:ExtensityAI/ontoloom.git
cd ontoloom
Claude Code plugin (recommended)
/plugins add /path/to/ontoloom/plugins/claude-plugin
Manual MCP configuration
Drop this into your .mcp.json, adjusting the paths for your clone:
{
"mcpServers": {
"ontoloom": {
"type": "stdio",
"command": "uv",
"args": [
"run",
"--project",
"packages/mcp",
"python",
"-m",
"ontoloom_mcp.server"
]
}
}
}
Standalone
uv run --project packages/mcp python -m ontoloom_mcp.server
Sandboxing (optional)
Set ONTOLOOM_WORKSPACE_ROOT=/path/to/workspace to confine all Ontology(...), export_jsonl, and import paths to that directory tree. Useful when running an agent that may take instructions from untrusted documents - the agent can't open or write SQLite files outside the workspace. Unset (default) means unrestricted single-user behavior.
How it works
Each ontology lives in a single .db file that works the same whether it has a dozen axioms or millions. SQLite is the source of truth; the MCP layer is the only writer, so axioms are always validated before they reach disk.
Axioms are typed Pydantic models hashed by canonical logical content, ignoring annotations - you can edit a comment without changing the hash, and exact duplicates are caught automatically.
Reviews (0)
Sign in to leave a review.
Leave a reviewNo results found