Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agent Interop Runtime

NPM · AGENT-INTEROP-RUNTIME

Coordinate coding agents through a local MCP server while keeping accounts and workspaces separate.

−12 this week 76 Trust /100

Last scanned (4 hours ago)

Scores higher than 53% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 1 of 10 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Praket7/agent-interop-runtime). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 436 tokens (~48/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability check failed: the tool surface changed between 0.3.2 and 1.1.0: 51 tool removals, 0 breaking changes, 8 additions. See how to fix → Fail
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +15
    • Stability: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Dependency health: 0.86 → 0.97 ▲ functional
    • First check of Tool coverage: 100 functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
    • Package version: 1.0.2 → 1.1.0 functional
  • 3 Nov 26 −27
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → fail ▼ security
    • Schema quality: 43 → 53 ▼ functional
    • Package version: 0.3.2 → 1.0.2 functional
  • 2 Nov 26 0
    • Package version: 0.2.4 → 0.3.2 functional
  • 30 Oct 26 0
    • Stability: 0.97 → pass security
  • 29 Oct 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 0
    • Stability: 0.97 → pass security
  • 21 Oct 26 +1
    • Package version: 0.2.4 → 0.3.2 functional
  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/agent-interop-runtime@1.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Praket7/agent-interop-runtime
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Praket7/agent-interop-runtime/.github/workflows/publish-mcp.yml@refs/tags/v1.1.0
Rekor log index 3691429241
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:3752b70a0af8186011ff2230049f510300f8ac19006f99d0282883a5df6156999872cce20022f51e52492ed31972098fb4d72a702e36adf14447cb554

Background: How many MCP packages publish verified provenance →

Dependencies 10 packages
Packages resolved 10
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~436 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_session ~31

Cancel work in a provider native session.

NameTypeReqDescription
nativeIdstringyes–
providerstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

create_session ~37

Create a native provider session when supported.

NameTypeReqDescription
cwdstring––
providerstringyes–
titlestring––
NameTypeReqDescription
result–yes–

No examples provided.

get_runtime_status ~36

Report installed provider capabilities and the active tool profile. Use list_providers for per-provider capabilities and list_agent_sessions to inspect available sessions.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yes–

No examples provided.

get_session_diff ~51

Read file change evidence for one exact native provider session. Use read_session_events for its progress history; this tool returns file changes only.

NameTypeReqDescription
nativeIdstringyes–
providerstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

list_agent_sessions ~48

Find actual native sessions from installed providers, optionally filtered by provider. Provider errors are returned separately from an empty result. Use list_providers to inspect adapter capabilities.

NameTypeReqDescription
providerstring––
NameTypeReqDescription
result–yes–

No examples provided.

list_providers ~37

List configured provider adapters and their supported actions. Use list_agent_sessions to find actual native sessions; discovery does not confirm sign in or readiness.

Input schema present but exposes no named parameters.

NameTypeReqDescription
result–yes–

No examples provided.

read_session_events ~69

Read a bounded page of native provider events with a resumable cursor, stream epoch, and retention-gap metadata.

NameTypeReqDescription
afterSequenceinteger––
limitinteger––
nativeIdstringyes–
providerstringyes–
timeoutMsinteger––
NameTypeReqDescription
result–yes–

No examples provided.

resume_session ~33

Resume or reattach to an exact native session.

NameTypeReqDescription
nativeIdstringyes–
providerstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

send_session_message ~94

Send one prompt to an exact native provider session. Model, agent, and reasoning are separate controls. For OpenCode, accepted means queued by transport and does not mean completed.

NameTypeReqDescription
agentstring––
modestring––
modelobject––
nativeIdstringyes–
providerstringyes–
reasoningstring––
textstringyes–
NameTypeReqDescription
result–yes–

No examples provided.

Install

How do I install the Agent Interop Runtime MCP server?

Agent Interop Runtime runs locally as an npm package, launched with npx -y agent-interop-runtime. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · agent-interop-runtime

# add to Claude Code
claude mcp add praket7-agent-interop-runtime -- npx -y agent-interop-runtime
Common questions

What is the Agent Interop Runtime MCP server?

Agent Interop Runtime is an MCP server listed in the public MCP registry as io.github.Praket7/agent-interop-runtime. Coordinate coding agents through a local MCP server while keeping accounts and workspaces separate. This page covers its npm package (agent-interop-runtime).

Is the Agent Interop Runtime MCP server safe to use?

Agent Interop Runtime scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Agent Interop Runtime MCP server expose?

Agent Interop Runtime exposes 9 tools: get_runtime_status, list_providers, list_agent_sessions, get_session_diff, read_session_events, and 4 more. Their descriptions and schemas cost roughly 436 tokens of context every time the server is loaded.

Is the Agent Interop Runtime MCP server still maintained?

Agent Interop Runtime is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Agent Interop Runtime MCP server under?

Agent Interop Runtime declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.