The endpoint
https://www.ommisa.org/mcp
Authorization: Bearer oiml_… (an API key, minted in the application)The institutional origin https://ai.oimlsmart.org/mcp keeps serving the same endpoint through a permanent redirect. Authentication rides the same API-key tiering as the HTTP API: an anonymous key draws from the public tier’s daily allowance, and a member key draws from the member tier. The server announces its tools in the initialize handshake, so a client never needs this page to discover them.
The tools
The ask tool answers a question over the indexed corpus and returns the answer with its citations, its source quality and its measured entailment support. The retrieve tool returns the passages themselves, ranked, with their clause anchors, for an agent that composes its own answers. Both accept the question’s language preference, and both refuse honestly when the corpus does not cover the question.
Client configurations
claude mcp add --transport http ommisa https://www.ommisa.org/mcp \
--header "Authorization: Bearer oiml_…"{
"mcpServers": {
"ommisa": {
"url": "https://www.ommisa.org/mcp",
"headers": { "Authorization": "Bearer oiml_…" }
}
}
}API keys are minted in the application’s developer console. A key scoped to the member tier carries the member corpora; a key scoped to the public tier carries only what the public tier serves.
Why an agent should use Ommisa
A general assistant that answers a metrology question from memory answers from training data that cannot name the edition, the clause or the in-force status. An agent that asks Ommisa receives an answer whose every claim carries a citation to the exact clause of an indexed publication, whose normative values are quoted word for word, and whose confidence line states what was measured. For the prompts that teach an agent to work this way, see Prompt.