InterAI Risk Oracle MCP server
online · 100% uptimeio.github.InterAILabs/ai-risk-oracle·v0.1.3-beta.1·1 starsPre-execution policy gate for consequential agent actions with durable trust receipts.
1 stars
Reviews
Write oneNobody has reviewed InterAI Risk Oracle yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
InterAI Risk Oracle tools (9)
write = sends, deletes, buys or postsoracle.agent_cardFreeRead-only A2A Agent Card with agent identity, security scheme, capabilities, and skills. Use it when selecting or integrating InterAI through A2A; use oracle.service_descriptor for general service metadata or oracle.discovery_bundle for complete bootstrap context.
oracle.discovery_bundleFreeRead-only bootstrap or handoff bundle with service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. Use it for complete integration context; use oracle.service_descriptor for focused service metadata, oracle.agent_card for A2A capabilities, or oracle.get_pricing for costs.
oracle.get_pricingFreeRead-only public metadata for costs, trial availability, idempotency, and top-up or payment paths. Use it before budgeting or onboarding; it does not evaluate risk or create a trust receipt.
oracle.get_trust_receiptFreeRead-only lookup of the canonical public representation and signature metadata for a trust receipt that already exists. Supply receipt_id. It does not create or re-run a decision; use oracle.verify_trust_receipt_signature when the goal is signature validation.
oracle.service_descriptorFreeRead-only general service descriptor with identity, endpoints, billing, trust, and supported agent protocols. Use it to inspect service-level integration metadata; use oracle.agent_card for A2A skills or oracle.discovery_bundle for the complete bootstrap package.
oracle.verify_autonomous_actionFreePrimary tool for one concrete proposed autonomous action before it executes. This authenticated prepaid verification may consume account balance and records a signed trust receipt; InterAI evaluates the proposal but does not execute or modify the proposed external action. Reuse idempotency_key only when retrying the same logical request to avoid duplicate billing. Returns allow, review_required, or block with policy signals. Use oracle.verify_batch for multiple independent items and oracle.verify_response only for legacy prompt/response compatibility.
oracle.verify_batchFreeUse for multiple independent legacy or autonomous verification items in one authenticated prepaid call (1 to 100). The batch may consume account balance and records one trust receipt per item; InterAI does not execute any proposed external action. Reuse idempotency_key only for the same logical batch retry. For one proposed action, use oracle.verify_autonomous_action instead.
oracle.verify_responseFreeLegacy compatibility entry point for existing clients. This authenticated prepaid verification may consume account balance and records a trust receipt, but it does not execute any proposed external action. Supply exactly one contract: prompt + response, or use_case + action; never mix them. Reuse idempotency_key only for the same logical retry. For new action preflight use oracle.verify_autonomous_action; use oracle.verify_batch for multiple items.
oracle.verify_trust_receipt_signatureFreeRead-only service-side validation of a trust receipt that already exists. Supply signature plus either receipt_id for the canonical server-stored receipt or a caller-supplied receipt object. Returns valid true or false when signing is enabled. Current signatures use HMAC-SHA256 and are service-verifiable by InterAI, not independent offline public-key proofs. It does not evaluate risk or create a receipt; use oracle.get_trust_receipt to retrieve receipt metadata.
Public scan report
scanner v0.1.10 · 2026-10-03 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 1623ms20/20
- Tool poisoning9 tool descriptions checked15/15
- Auth qualityopen endpoint, read-only tools10/15
- Maintenancelast push 4 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How InterAI Risk Oracle compares
Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 80% of 4,460 AI and agents servers
- Tools
- 9
- the typical AI and agents server has 6
- Tools that change things
- 0%
- typical: 0%. Fewer write tools means less an agent can break
- Uptime
- 100%
- of our recent checks; the typical remote AI and agents server answers 100%
- Response time
- 538 ms
- faster than 25% of 2,331 AI and agents servers
- GitHub stars
- 1
- more than 50% of 2,711 AI and agents servers
What its tools let an agent do: 9 read
Install InterAI Risk Oracle in Claude Code, Cursor or VS Code
claude mcp add --transport http ai-risk-oracle https://api.interailabs.dev/mcp
What the publisher says
From the InterAI Risk Oracle repository's README, as published. We do not edit it. Read it on GitHub
InterAI Risk Oracle
Independent pre-execution decision layer for consequential agent actions.
Before an agent executes, InterAI verifies.
I’m Alejandro Bolognese, building InterAI through InterAI Labs as ongoing work on agent infrastructure, execution control, trust boundaries, and production systems.
Live proof: Action Boundary Lab · Controlled safe demo · Architecture & authority boundary · OpenAPI
InterAI sits between an autonomous agent and a consequential action. The agent proposes what it wants to do; InterAI evaluates the action in context, applies authoritative host/account constraints plus any request-scoped caller constraints, and returns a machine-readable authority decision:
proposed action
|
v
InterAI
|
+--> ALLOW
+--> REVIEW_REQUIRED
+--> BLOCK
|
v
signed trust receiptThe important boundary is not merely can this principal technically perform the action? It is:
Should this specific action execute now, in this context, under this policy?
That makes InterAI complementary to authentication, permissions, spend limits, workflow rules, and domain-specific controls rather than a replacement for them.
Where InterAI Fits
Identity / authentication
"Who is this?"
|
Permissions / deterministic limits
"Can this principal do this class of operation?"
|
InterAI
"Should this exact proposed action execute in this context?"
|
Execution / escalation / abortUse InterAI when an agent is about to do something with real consequences: execute a tool, move funds, update production state, approve a workflow, sign a wallet action, send an external message, or trigger another irreversible or costly operation.
Decision Contract
For autonomous execution requests, the primary InterAI authority contract is:
- recommendedaction: allow, reviewrequired, or block
- policy_result: the authority result under the effective policy
- policy_violations: explicit policy findings when applicable
- trustreceiptid: durable decision evidence
- executionintentdigest: deterministic identifier for the exact intent evaluated
- effective host/account/caller policy provenance in authenticated decision receipts
review_required means the current agent should not execute autonomously under the current policy. Review can be handled by a supervisor agent, policy system, governance queue, wallet rule, or human operator.
Exact-action binding
For executable pilot authorization, the host constructs the trusted action envelope interai-canonical-action/v1 and the host-attested execution context interai-host-execution-context/v1. InterAI returns a CanonicalExecutionIntent (interai-canonical-execution-intent/v2), executionintentdigest, and—only for an authenticated allow—an ExecutionAuthorization (interai-execution-authorization/v1). The host must verify the receipt, rebuild the final invocation immediately before the side effect, recompute the canonical digest, validate the authorization, and fail closed on any mismatch. A change to tool, arguments, authoritative actor, run, workspace, environment, resource/destination, or relevant policy invalidates the earlier allow and requires a new decision. review_required and block are non-authorizing.
Execution authorization is single-use and short lived: 1–300 seconds, 60 seconds by default. InterAI does not provide universal distributed replay prevention across external runtimes; the host must atomically and durably consume the authorization when that guarantee is required.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
InterAI Risk Oracle: common questions
- Is InterAI Risk Oracle MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the InterAI Risk Oracle safety report
- How do I install InterAI Risk Oracle?
- It runs remotely at api.interailabs.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does InterAI Risk Oracle need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is InterAI Risk Oracle maintained?
- The last commit was 36 days ago (2026-09-29). The latest release is v0.1.3-beta.1.
- Is InterAI Risk Oracle up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- What can I use instead of InterAI Risk Oracle?
- Servers from other publishers that do the same job: Decionis MCP server, Emilia Protocol MCP server and Agent-Native Chat MCP server.
- How does InterAI Risk Oracle compare with other AI and agents MCP servers?
- safety score 88/100 (higher than 80% of 4,460 AI and agents servers); tools 9 (the typical AI and agents server has 6); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to InterAI Risk Oracle
Same job from other publishers: the closest match first, then the best rated.
- not reviewedEstablishedA
- Emilia ProtocolExact-action approval for consequential agent actions: request, track, and verify signed receipts.not reviewedEstablishedB
- Agent-Native ChatMinimal chat-first app with durable threads, actions, and the app-agent loopnot reviewedEstablishedA
Agoragentic Agent OS MCPTriptych OS (Agent OS) MCP for governed routing, receipts, and USDC settlement on Base.not reviewedEstablishedB- three.ws ProvenanceAppend-only, signed, on-chain-verifiable agent action log — record and audit what agents did.not reviewedEstablishedB