Seiva Ai MCP Server

@seiva-ai/mcp-server npm v0.3.0 Source verified

Published by joaopedromano-source — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 9

high Shell/command execution in server code (checkout_tools.js)MTC-SRC-002

In the server's implementation (`checkout_tools.js:18`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: rt { spawn } from "node:child_process"; import { existsSync } from "node:fs"; import { createRequire } from "node:module

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server checkout_tools.js

medium Tool "seiva_write_file" can modify the filesystemMTC-CAP-002

Tool "seiva_write_file" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool seiva_write_file

medium Tool "seiva_edit_file_diff" can modify the filesystemMTC-CAP-002

Tool "seiva_edit_file_diff" can write, overwrite or delete files (keyword "edit_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool seiva_edit_file_diff

medium Tool "seiva_write_files" can modify the filesystemMTC-CAP-002

Tool "seiva_write_files" can write, overwrite or delete files (keyword "write_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool seiva_write_files

medium Tool "seiva_delete_file" can modify the filesystemMTC-CAP-002

Tool "seiva_delete_file" can write, overwrite or delete files (keyword "delete_file" in tool name). Verify it is scoped to a safe directory.

Fix: Constrain file operations to an explicit, non-sensitive root; reject path traversal.

Location: tool seiva_delete_file

low Mutating tool "seiva_write_file" declares no destructiveHintMTC-CAP-005

Tool "seiva_write_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool seiva_write_file

low Mutating tool "seiva_edit_file_diff" declares no destructiveHintMTC-CAP-005

Tool "seiva_edit_file_diff" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool seiva_edit_file_diff

low Mutating tool "seiva_write_files" declares no destructiveHintMTC-CAP-005

Tool "seiva_write_files" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool seiva_write_files

low Mutating tool "seiva_delete_file" declares no destructiveHintMTC-CAP-005

Tool "seiva_delete_file" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool seiva_delete_file

Tools 97

Each tool and what it can reach — statically extracted from the published source.

  • seiva_delete_filewrites files
  • seiva_edit_file_diffwrites files
  • seiva_get_logsreads sensitive data
  • seiva_list_builtin_toolsingests untrusted input
  • seiva_list_filesreads sensitive data
  • seiva_read_filereads sensitive data
  • seiva_write_filewrites files
  • seiva_write_fileswrites files
  • seiva_acquire_app_lockno sensitive capability
  • seiva_analyze_external_projectno sensitive capability
Show 87 more tools ↓
  • seiva_app_build_localno sensitive capability
  • seiva_app_checkout_statusno sensitive capability
  • seiva_app_pullno sensitive capability
  • seiva_app_pushno sensitive capability
  • seiva_archive_agentno sensitive capability
  • seiva_archive_skillno sensitive capability
  • seiva_archive_toolno sensitive capability
  • seiva_build_appno sensitive capability
  • seiva_count_recordsno sensitive capability
  • seiva_create_agentno sensitive capability
  • seiva_create_appno sensitive capability
  • seiva_create_credentialno sensitive capability
  • seiva_create_recordno sensitive capability
  • seiva_create_scheduleno sensitive capability
  • seiva_create_skillno sensitive capability
  • seiva_create_toolno sensitive capability
  • seiva_create_workspaceno sensitive capability
  • seiva_delete_agentno sensitive capability
  • seiva_delete_recordno sensitive capability
  • seiva_delete_scheduleno sensitive capability
  • seiva_delete_skillno sensitive capability
  • seiva_delete_toolno sensitive capability
  • seiva_describe_datapack_tableno sensitive capability
  • seiva_enable_builtin_toolno sensitive capability
  • seiva_execute_toolno sensitive capability
  • seiva_fire_scheduleno sensitive capability
  • seiva_generate_migration_planno sensitive capability
  • seiva_get_agentno sensitive capability
  • seiva_get_appno sensitive capability
  • seiva_get_app_lockno sensitive capability
  • seiva_get_app_runtime_errorsno sensitive capability
  • seiva_get_app_usageno sensitive capability
  • seiva_get_build_logsno sensitive capability
  • seiva_get_contextno sensitive capability
  • seiva_get_instructionsno sensitive capability
  • seiva_get_project_contextno sensitive capability
  • seiva_get_recordno sensitive capability
  • seiva_get_scheduleno sensitive capability
  • seiva_get_session_logsno sensitive capability
  • seiva_get_skillno sensitive capability
  • seiva_get_toolno sensitive capability
  • seiva_grant_app_datano sensitive capability
  • seiva_import_env_varsno sensitive capability
  • seiva_import_project_filesno sensitive capability
  • seiva_list_agentsno sensitive capability
  • seiva_list_app_agentsno sensitive capability
  • seiva_list_app_data_grantsno sensitive capability
  • seiva_list_appsno sensitive capability
  • seiva_list_available_datapacksno sensitive capability
  • seiva_list_credentialsno sensitive capability
  • seiva_list_instructionsno sensitive capability
  • seiva_list_membersno sensitive capability
  • seiva_list_partnership_agentsno sensitive capability
  • seiva_list_partnership_skillsno sensitive capability
  • seiva_list_partnership_toolsno sensitive capability
  • seiva_list_pending_approvalsno sensitive capability
  • seiva_list_recordsno sensitive capability
  • seiva_list_schedulesno sensitive capability
  • seiva_list_skillsno sensitive capability
  • seiva_list_toolsno sensitive capability
  • seiva_list_versionsno sensitive capability
  • seiva_list_workspacesno sensitive capability
  • seiva_pause_scheduleno sensitive capability
  • seiva_publish_agentno sensitive capability
  • seiva_publish_appno sensitive capability
  • seiva_publish_skillno sensitive capability
  • seiva_publish_toolno sensitive capability
  • seiva_release_app_lockno sensitive capability
  • seiva_renew_app_lockno sensitive capability
  • seiva_request_datapack_grantno sensitive capability
  • seiva_request_external_dependencyno sensitive capability
  • seiva_resume_scheduleno sensitive capability
  • seiva_revoke_app_datano sensitive capability
  • seiva_schedule_statsno sensitive capability
  • seiva_select_workspaceno sensitive capability
  • seiva_set_app_permissionsno sensitive capability
  • seiva_set_member_roleno sensitive capability
  • seiva_tool_checkout_statusno sensitive capability
  • seiva_tool_pullno sensitive capability
  • seiva_tool_pushno sensitive capability
  • seiva_update_agentno sensitive capability
  • seiva_update_appno sensitive capability
  • seiva_update_recordno sensitive capability
  • seiva_update_scheduleno sensitive capability
  • seiva_update_skillno sensitive capability
  • seiva_update_toolno sensitive capability
  • seiva_upload_app_assetno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.3.0 latest A 94/100 9 1.9.0 2026-07-24

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/seiva-ai-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/seiva-ai-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/seiva-ai-mcp-server"><img src="https://mcptrustchecker.com/registry/seiva-ai-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/seiva-ai-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @seiva-ai/mcp-server --online

Use the free API → How scoring works

More in Developer Tools