Scimar

Scimar (Scimar Ltd., formerly styled SciMar) is a privately held Canadian life-sciences company founded in 2009 with its head office in Dauphin, Manitoba and research laboratories in Winnipeg. It commercializes the work of co-founder and Chief Scientific Officer Dr. W. Wayne Lautt, who in 1996 identified hepatalin — known in the literature as hepatic insulin-sensitizing substance, or HISS — a liver hormone Scimar describes as the missing link in nutrient partitioning, prediabetes and type 2 diabetes. Its pipeline pairs diagnostics with therapeutics: SciMar NuPa Test, a diagnostic test meal that measures hepatalin production and is in Phase 2 clinical trials in Canada; SciMar NuPa Renew, a pre-meal pharmaceutical preparing for Phase 2B; SciMar NuPa Daily, an antioxidant supplement intended to protect hepatalin production; and Hepatalin-S, a synthetic hepatalin for advanced-stage disease. Alongside the science the company runs the Wellness Transformation Network, a community outreach program with nonprofits, Indigenous communities and Manitoba businesses, and produces the Webby-nominated science podcast Inside the Breakthrough hosted by Dan Riskin. Scimar publishes no product or developer API and operates no developer program. The machine-readable surface on scimar.ca is CMS-provided: a served llms.txt generated by All in One SEO, the anonymously readable WordPress REST API (wp/v2) that returns news stories, pages, team profiles, media and site search as JSON, and a WordPress MCP Adapter that advertises two Model Context Protocol endpoints plus RFC 8414 and RFC 9728 OAuth discovery documents — all of which are authentication-gated.

Scimar publishes 9 APIs on the APIs.io network, including Comments API, Discovery API, Media API, and 6 more. Tagged areas include Company, Biotechnology, Life Sciences, Pharmaceuticals, and Diabetes.

Scimar’s developer surface includes engineering blog, product news, support, authentication, and 28 more developer resources.

25.4/100 emerging ▬ flat Agent 37/100 agent ready saas Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2
10 APIs 1 MCP Servers
CompanyBiotechnologyLife SciencesPharmaceuticalsDiabetesDiagnosticsClinical TrialsHealthNutritionResearchCanadaContent

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2
Composite quality — 25.4/100 · emerging
Contract Quality 2.8 / 21
Developer Ergonomics 3.5 / 17
Access Clarity 3.6 / 17
Operational Transparency 0.0 / 11
Contract Governance 0.5 / 10
Discoverability 6.9 / 9
Regulatory Posture 7.9 / 15
Agent readiness — 37/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 6 / 6
Protected Resource Metadata 5 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/scimar: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

Scimar MCP Server (WordPress MCP Adapter)

Two Model Context Protocol endpoints advertised in the scimar.ca WordPress REST route index under the "mcp" namespace — /wp-json/mcp/mcp-oauth-server and /wp-json/mcp/mcp-adapte...

Scimar Comments API

The Comments API from Scimar — 2 operation(s) for comments.

Scimar Discovery API

The Discovery API from Scimar — 4 operation(s) for discovery.

Scimar Media API

The Media API from Scimar — 4 operation(s) for media.

Scimar Pages API

The Pages API from Scimar — 6 operation(s) for pages.

Scimar Posts API

The Posts API from Scimar — 6 operation(s) for posts.

Scimar Search API

The Search API from Scimar — 1 operation(s) for search.

Scimar Settings API

The Settings API from Scimar — 1 operation(s) for settings.

Scimar Taxonomy API

The Taxonomy API from Scimar — 6 operation(s) for taxonomy.

Scimar Users API

The Users API from Scimar — 6 operation(s) for users.

Scroll for all 10

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Scimar MCP Server

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Scimar Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Scimar Rate Limits

0 limits

RATE LIMITS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Scimar Authentication

http · 1 scheme

SECURITY

Scimar Domain Security

TLSv1.3 · HSTS

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Scimar Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 3

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 8

The organization behind the API

Scroll for all 8

Other 6

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: scimar
name: Scimar
description: 'Scimar (Scimar Ltd., formerly styled SciMar) is a privately held Canadian life-sciences company founded in 2009
  with its head office in Dauphin, Manitoba and research laboratories in Winnipeg. It commercializes the work of co-founder
  and Chief Scientific Officer Dr. W. Wayne Lautt, who in 1996 identified hepatalin — known in the literature as hepatic insulin-sensitizing
  substance, or HISS — a liver hormone Scimar describes as the missing link in nutrient partitioning, prediabetes and type
  2 diabetes. Its pipeline pairs diagnostics with therapeutics: SciMar NuPa Test, a diagnostic test meal that measures hepatalin
  production and is in Phase 2 clinical trials in Canada; SciMar NuPa Renew, a pre-meal pharmaceutical preparing for Phase
  2B; SciMar NuPa Daily, an antioxidant supplement intended to protect hepatalin production; and Hepatalin-S, a synthetic
  hepatalin for advanced-stage disease. Alongside the science the company runs the Wellness Transformation Network, a community
  outreach program with nonprofits, Indigenous communities and Manitoba businesses, and produces the Webby-nominated science
  podcast Inside the Breakthrough hosted by Dan Riskin. Scimar publishes no product or developer API and operates no developer
  program. The machine-readable surface on scimar.ca is CMS-provided: a served llms.txt generated by All in One SEO, the anonymously
  readable WordPress REST API (wp/v2) that returns news stories, pages, team profiles, media and site search as JSON, and
  a WordPress MCP Adapter that advertises two Model Context Protocol endpoints plus RFC 8414 and RFC 9728 OAuth discovery
  documents — all of which are authentication-gated.'
url: https://raw.githubusercontent.com/api-evangelist/scimar/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
image: https://scimar.ca/wp-content/uploads/2022/11/scimar-logo.svg
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
tags:
- Company
- Biotechnology
- Life Sciences
- Pharmaceuticals
- Diabetes
- Diagnostics
- Clinical Trials
- Health
- Nutrition
- Research
- Canada
- Content
tags_raw:
- Company
- Biotechnology
- Life Sciences
- Pharmaceuticals
- Diabetes
- Diagnostics
- Clinical Trials
- Health
- Nutrition
- Research
- Canada
- Content
apis:
- aid: scimar:mcp
  name: Scimar MCP Server (WordPress MCP Adapter)
  description: 'Two Model Context Protocol endpoints advertised in the scimar.ca WordPress REST route index under the "mcp"
    namespace — /wp-json/mcp/mcp-oauth-server and /wp-json/mcp/mcp-adapter-default-server. Both are live and authentication-gated:
    an anonymous JSON-RPC tools/list returns HTTP 401, so the published tool set could not be enumerated. Unusually for this
    class of surface, the OAuth server endpoint answers with a WWW-Authenticate Bearer challenge naming an RFC 9728 protected-resource
    metadata document, and scimar.ca serves both /.well-known/oauth-authorization-server (RFC 8414) and /.well-known/oauth-protected-resource
    anonymously with HTTP 200.'
  humanURL: https://scimar.ca/wp-json/mcp
  baseURL: https://scimar.ca/wp-json/mcp/mcp-oauth-server
  tags:
  - MCP
  - Agents
  properties:
  - type: MCPServer
    url: mcp/scimar-mcp.yml
  - type: ToolCrosswalk
    url: mcp/scimar-tool-crosswalk.yml
  - type: OAuthScopes
    url: scopes/scimar-scopes.yml
  - type: WellKnown
    url: well-known/scimar-well-known.yml
- aid: scimar:scimar-comments-api
  name: Scimar Comments API
  description: The Comments API from Scimar — 2 operation(s) for comments.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Comments
  properties:
  - type: OpenAPI
    url: openapi/scimar-comments-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-discovery-api
  name: Scimar Discovery API
  description: The Discovery API from Scimar — 4 operation(s) for discovery.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/scimar-discovery-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-media-api
  name: Scimar Media API
  description: The Media API from Scimar — 4 operation(s) for media.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Media
  properties:
  - type: OpenAPI
    url: openapi/scimar-media-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-pages-api
  name: Scimar Pages API
  description: The Pages API from Scimar — 6 operation(s) for pages.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Pages
  properties:
  - type: OpenAPI
    url: openapi/scimar-pages-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-posts-api
  name: Scimar Posts API
  description: The Posts API from Scimar — 6 operation(s) for posts.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Posts
  properties:
  - type: OpenAPI
    url: openapi/scimar-posts-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-search-api
  name: Scimar Search API
  description: The Search API from Scimar — 1 operation(s) for search.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Search
  properties:
  - type: OpenAPI
    url: openapi/scimar-search-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-settings-api
  name: Scimar Settings API
  description: The Settings API from Scimar — 1 operation(s) for settings.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Settings
  properties:
  - type: OpenAPI
    url: openapi/scimar-settings-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-taxonomy-api
  name: Scimar Taxonomy API
  description: The Taxonomy API from Scimar — 6 operation(s) for taxonomy.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - Taxonomy
  properties:
  - type: OpenAPI
    url: openapi/scimar-taxonomy-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
- aid: scimar:scimar-users-api
  name: Scimar Users API
  description: The Users API from Scimar — 6 operation(s) for users.
  humanURL: https://scimar.ca/news/
  baseURL: https://scimar.ca/wp-json
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/scimar-users-api-openapi.yml
  - type: DataModel
    url: data-model/scimar-data-model.yml
  - type: ErrorCatalog
    url: errors/scimar-problem-types.yml
  - type: Conventions
    url: conventions/scimar-conventions.yml
x-enrichment:
  date: '2026-08-26'
  status: enriched
  artifacts_added: 23
  pass: local-v1
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://scimar.ca/
- type: About
  url: https://scimar.ca/about/
- type: Blog
  url: https://scimar.ca/news/
- type: BlogRSS
  url: https://scimar.ca/feed/
- type: News
  url: https://scimar.ca/news/
- type: Press
  url: https://scimar.ca/about/media/
- type: Support
  url: https://scimar.ca/about/contact/
- type: Team
  url: https://scimar.ca/team/
- type: Technology
  url: https://scimar.ca/science-products/the-science/
- type: Pipeline
  url: https://scimar.ca/science-products/product-pipeline/
- type: Community
  url: https://scimar.ca/community/
- type: Videos
  url: https://scimar.ca/videos/
- type: TermsOfService
  url: https://scimar.ca/about/legal/
- type: PrivacyPolicy
  url: https://scimar.ca/about/privacy/
- type: Accessibility
  url: https://scimar.ca/about/accessibility/
- type: LinkedIn
  url: https://www.linkedin.com/company/698875/
- type: Twitter
  url: https://twitter.com/SciMarL
- type: SecondaryMarket
  url: https://www.hiive.com/securities/scimar-stock
- type: LLMsTxt
  url: llms/scimar-llms.txt
- type: WellKnown
  url: well-known/scimar-well-known.yml
- type: Packages
  url: packages/scimar-packages.yml
- type: Authentication
  url: authentication/scimar-authentication.yml
- type: Conventions
  url: conventions/scimar-conventions.yml
- type: Conformance
  url: conformance/scimar-conformance.yml
- type: ErrorCatalog
  url: errors/scimar-problem-types.yml
- type: DataModel
  url: data-model/scimar-data-model.yml
- type: Lifecycle
  url: lifecycle/scimar-lifecycle.yml
- type: DomainSecurity
  url: security/scimar-domain-security.yml
- type: Plans
  url: plans/scimar-plans-pricing.yml
- type: RateLimits
  url: rate-limits/scimar-rate-limits.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Overlay
  url: overlays/scimar-content-overlay.yaml

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/scimar"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/scimar/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/scimar/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

A second provider on the same verified email joins the account you already have.