Virtual Incision

Virtual Incision Corporation is a Lincoln, Nebraska surgical robotics company, spun out of the University of Nebraska in 2006, that builds MIRA — the Miniaturized In vivo Robotic Assistant — and defined the miniaturized robotic-assisted surgery (miniRAS) category. MIRA is a roughly two-pound, tray-to-table robot inserted through a single umbilical incision, designed to make any operating room robot-ready in minutes. It won FDA De Novo authorization for colectomy in 2024 and 510(k) clearance for benign hysterectomy in 2026. Virtual Incision publishes no product or developer API: MIRA is regulated capital equipment, not a platform. The machine-readable surface on virtualincision.com is the anonymously readable WordPress REST API (newsroom, MIRA pages, events, jobs, media) plus a live but OAuth-gated WordPress MCP Adapter endpoint advertised by RFC 8414 and RFC 9728 discovery documents. The company publishes a coordinated vulnerability disclosure policy under FDA Section 524B.

Virtual Incision is listed with 2 APIs on the APIs.io network. Tagged areas include Company, Medical Devices, Surgical Robotics, Robotics, and Healthcare.

Virtual Incision’s developer surface includes engineering blog, support, authentication, code examples, and 26 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

25.3/100 emerging ▬ flat Agent 22/100 agent aware Front door AI 1/6 silent Heartbeat 94/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs 1 MCP Servers 3 Agent Skills

Company Medical Devices Surgical Robotics Robotics Healthcare Health Life Sciences Medical Technology News Careers Event MCP

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 25.3/100 · emerging

Contract Quality 1.4 / 21

Developer Ergonomics 4.4 / 17

Access Clarity 3.6 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 5.7 / 9

Regulatory Posture 5.6 / 15

Agent readiness — 22/100 · agent aware

Machine-Readable Contract 0 / 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 7 / 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 Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/virtual-incision/"><img src="https://apis.io/badge/virtual-incision/card.svg" alt="Virtual Incision on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks

5 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 6.5 — up to +23.4 composite points
Access Clarity scores 21.1 — up to +15.8 composite points
Developer Ergonomics scores 25.6 — up to +14.9 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/virtual-incision/apis.yml: open an issue on github.com/api-evangelist/virtual-incision to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
IVD, Diagnostics and Surgical Devices (FDA / EU regulated device makers)	regulated	20.6 (thin)	-	-
Canada Medical Device Licensing (Health Canada MDALL licence holders, incl. SaMD)	regulated	20.6 (thin)	-	-
FDA Device Establishments (radiology, nuclear medicine, cardiovascular, robotic surgery)	regulated	20.6 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

APIs 2

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

Virtual Incision Website (WordPress REST)

The public WordPress REST API (wp-json) of the Virtual Incision website at virtualincision.com: the route index of the site's content management system, catalogued as one site s...

Virtual Incision MCP Server (WordPress MCP Adapter)

A Model Context Protocol endpoint registered under the "mcp" namespace of the virtualincision.com WordPress REST route index and served at /wp-json/mcp/mcp-oauth-server (with a ...

MCP Servers 1

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

Virtual Incision MCP Server

Remote MCP server at virtualincision.com over HTTP requiring OAuth.

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

virtual-incision-careers-watch

AGENT SKILL

virtual-incision-media-assets

AGENT SKILL

virtual-incision-newsroom-monitor

AGENT SKILL

Virtual Incision API pricing

Pricing Plans 1

Published pricing tiers and plan structures.

Virtual Incision Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Virtual Incision Rate Limits

0 limits

RATE LIMITS

Security Posture 3

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

Virtual Incision Authentication

apiKey/http/oauth2 · 3 schemes

SECURITY

Virtual Incision Domain Security

TLSv1.3 · DMARC

SECURITY

Virtual Incision Vulnerability Disclosure

no policy recorded

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Virtual Incision Scopes

1 scope · authorization_code

1 scopes

SCOPES

Resources

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

LLMsTxt

AgentSkill

MCPServer

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

Conformance

Lifecycle

ErrorCatalog

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

Packages

Examples

ToolCrosswalk

Access & Security 5

Authentication, authorization, and security posture

Security

Authentication

OAuthScopes

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Operate 2

Status, limits, changes, and where to get help

Support

Support

RateLimits

RateLimits

Commercial 3

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Plans

Plans

Company 5

The organization behind the API

Website

Blog

BlogRSS

Careers

LinkedIn

Other 2

Properties that don't map to a standard resource type

Technology

Technology

SecondaryMarket

SecondaryMarket

Source (apis.yml)

aid: virtual-incision
name: Virtual Incision
description: 'Virtual Incision Corporation is a Lincoln, Nebraska surgical robotics company, spun out of the University of
  Nebraska in 2006, that builds MIRA — the Miniaturized In vivo Robotic Assistant — and defined the miniaturized robotic-assisted
  surgery (miniRAS) category. MIRA is a roughly two-pound, tray-to-table robot inserted through a single umbilical incision,
  designed to make any operating room robot-ready in minutes. It won FDA De Novo authorization for colectomy in 2024 and 510(k)
  clearance for benign hysterectomy in 2026. Virtual Incision publishes no product or developer API: MIRA is regulated capital
  equipment, not a platform. The machine-readable surface on virtualincision.com is the anonymously readable WordPress REST
  API (newsroom, MIRA pages, events, jobs, media) plus a live but OAuth-gated WordPress MCP Adapter endpoint advertised by
  RFC 8414 and RFC 9728 discovery documents. The company publishes a coordinated vulnerability disclosure policy under FDA
  Section 524B.'
url: https://raw.githubusercontent.com/api-evangelist/virtual-incision/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: enrichment-pipeline
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://virtualincision.com/wp-content/uploads/2022/07/VIC-logo-icon-400.png
specificationVersion: '0.20'
created: '2026-09-04'
modified: '2026-09-04'
tags:
- Company
- Medical Devices
- Surgical Robotics
- Robotics
- Healthcare
- Health
- Life Sciences
- Medical Technology
- News
- Careers
- Event
- MCP
tags_raw:
- Company
- Medical Devices
- Surgical Robotics
- Robotics
- Healthcare
- Health
- Life Sciences
- Medical Technology
- News
- Careers
- Events
- Model Context Protocol
position: Producing
apis:
- aid: virtual-incision:virtualincision-com-website-wordpress-rest
  name: Virtual Incision Website (WordPress REST)
  description: 'The public WordPress REST API (wp-json) of the Virtual Incision website at virtualincision.com: the route
    index of the site''s content management system, catalogued as one site surface rather than as separate APIs.'
  baseURL: https://virtualincision.com/wp-json
  tags:
  - WordPress
  x-surface: platform-generated
  properties:
  - type: Documentation
    url: https://virtualincision.com/wp-json
  x-platform: wordpress
  x-platform-surface: rest
- aid: virtual-incision:mcp
  name: Virtual Incision MCP Server (WordPress MCP Adapter)
  description: 'A Model Context Protocol endpoint registered under the "mcp" namespace of the virtualincision.com WordPress
    REST route index and served at /wp-json/mcp/mcp-oauth-server (with a second endpoint at /wp-json/mcp/mcp-adapter-default-server).
    The server is live but OAuth-gated: an anonymous JSON-RPC tools/list returns HTTP 401 mcp_unauthorized with a WWW-Authenticate
    Bearer challenge pointing at https://virtualincision.com/.well-known/oauth-protected-resource, so the published tool set
    could not be enumerated. This is the site CMS''s MCP endpoint, not a MIRA product MCP server.'
  humanURL: https://virtualincision.com/wp-json/mcp
  baseURL: https://virtualincision.com/wp-json/mcp/mcp-oauth-server
  tags:
  - MCP
  - Agents
  tags_raw:
  - MCP
  - Agents
  - Model Context Protocol
  properties:
  - type: MCPServer
    url: mcp/virtual-incision-mcp.yml
  - type: ToolCrosswalk
    url: mcp/virtual-incision-tool-crosswalk.yml
  - type: OAuthScopes
    url: scopes/virtual-incision-scopes.yml
  - type: Authentication
    url: authentication/virtual-incision-authentication.yml
  image: https://virtualincision.com/wp-content/uploads/2022/07/VIC-logo-icon-400.png
  x-surface: platform-generated
  x-platform: wordpress
  x-platform-surface: mcp-plugin
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://virtualincision.com/
- type: Blog
  url: https://virtualincision.com/news/
- type: BlogRSS
  url: https://virtualincision.com/feed/
- type: Support
  url: https://virtualincision.com/customer-support/
- type: Careers
  url: https://virtualincision.com/careers/
- type: Technology
  url: https://virtualincision.com/mira/
- type: TermsOfService
  url: https://virtualincision.com/terms-of-use/
- type: PrivacyPolicy
  url: https://virtualincision.com/privacy-policy/
- type: Security
  url: https://virtualincision.com/coordinated-disclosure/
- type: GitHubOrganization
  url: https://github.com/virtualincision
- type: LinkedIn
  url: https://www.linkedin.com/company/virtual-incision-corporation/
- type: SecondaryMarket
  url: https://forgeglobal.com/virtual-incision_stock/
- type: WellKnown
  url: well-known/virtual-incision-well-known.yml
- type: LLMsTxt
  url: llms/virtual-incision-llms.txt
- type: Packages
  url: packages/virtual-incision-packages.yml
- type: Authentication
  url: authentication/virtual-incision-authentication.yml
- type: OAuthScopes
  url: scopes/virtual-incision-scopes.yml
- type: Conventions
  url: conventions/virtual-incision-conventions.yml
- type: Conformance
  url: conformance/virtual-incision-conformance.yml
- type: Lifecycle
  url: lifecycle/virtual-incision-lifecycle.yml
- type: DomainSecurity
  url: security/virtual-incision-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/virtual-incision-vulnerability-disclosure.yml
- type: ErrorCatalog
  url: errors/virtual-incision-problem-types.yml
- type: DataModel
  url: data-model/virtual-incision-data-model.yml
- type: Examples
  url: examples/virtual-incision-examples.yml
- type: RateLimits
  url: rate-limits/virtual-incision-rate-limits.yml
- type: Plans
  url: plans/virtual-incision-plans-pricing.yml
- type: AgentSkill
  url: skills/_index.yml
- type: MCPServer
  url: mcp/virtual-incision-mcp.yml
- type: ToolCrosswalk
  url: mcp/virtual-incision-tool-crosswalk.yml
x-enrichment:
  date: '2026-09-04'
  status: enriched
  artifacts_added: 58
  pass: local-v3
x-tags-removed:
- Content

Virtual Incision API — frequently asked questions

Does Virtual Incision have an API?

Yes. APIs.io lists 2 APIs from Virtual Incision, including Virtual Incision Website (WordPress REST) and Virtual Incision MCP Server (WordPress MCP Adapter).

How do I authenticate with the Virtual Incision API?

Virtual Incision documents its authentication (apiKey/http/oauth2 · 3 schemes). The details are profiled on APIs.io as Virtual Incision Authentication.

Does Virtual Incision have an MCP server?

Yes. APIs.io lists 1 MCP server for Virtual Incision: Remote MCP server at virtualincision.com over HTTP requiring OAuth.

Is the Virtual Incision API ready for AI agents?

Virtual Incision has a Kin Score of 25.3 out of 100 (emerging) and an Agent Readiness score of 21.9 (agent-aware), scored by API Evangelist on 2026-11-06.

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/virtual-incision"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/virtual-incision/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/virtual-incision/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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