Avallon Labs MCP Server

@avallon-labs/mcp npm v43.3.0

Published by @avallon-labs — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Avallon API MCP server - generated from OpenAPI

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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 = 92/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 − 8 = 92. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([listSecrets, getSecret]) and tools that can send data out ([sendEmail, createWorkerWebhook, createAgentWebhook, createInboxWebhook, createExtractorWebhook, deleteWebhook, getWebhook, listWebhookDeliveries, testWebhook]) are exposed together. An agent can move private data to the sink.

Evidence: sources [listSecrets, getSecret] → sinks [sendEmail, createWorkerWebhook, createAgentWebhook, createInboxWebhook, createExtractorWebhook, deleteWebhook, getWebh

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow listSecrets → sendEmail

Tools 152

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

  • createAgentWebhooknetwork egress
  • createExtractorWebhooknetwork egress
  • createInboxWebhooknetwork egress
  • createWorkerWebhooknetwork egress
  • deleteWebhooknetwork egress
  • getSecretreads sensitive data
  • getWebhooknetwork egress
  • listSecretsreads sensitive data
  • listWebhookDeliveriesnetwork egress
  • sendEmailnetwork egress
Show 142 more tools ↓
  • testWebhooknetwork egress
  • addCaseLinksno sensitive capability
  • addToolsToVoiceAgentno sensitive capability
  • cancelJobno sensitive capability
  • cancelWorkerRunno sensitive capability
  • checkInboxAvailabilityno sensitive capability
  • createApiKeyno sensitive capability
  • createArtifactno sensitive capability
  • createCallFeedbackno sensitive capability
  • createCaseno sensitive capability
  • createChatno sensitive capability
  • createChatAgentno sensitive capability
  • createExtractorno sensitive capability
  • createExtractorJobno sensitive capability
  • createInboxno sensitive capability
  • createScheduleno sensitive capability
  • createSecretno sensitive capability
  • createToolno sensitive capability
  • createVoiceAgentno sensitive capability
  • createWorkerno sensitive capability
  • createWorkerRunno sensitive capability
  • deleteArtifactno sensitive capability
  • deleteCallFeedbackno sensitive capability
  • deleteChatAgentno sensitive capability
  • deleteEmailno sensitive capability
  • deleteExtractorno sensitive capability
  • deleteInboxno sensitive capability
  • deleteScheduleno sensitive capability
  • deleteSecretno sensitive capability
  • deleteToolno sensitive capability
  • deleteToolsFromVoiceAgentno sensitive capability
  • deleteVoiceAgentno sensitive capability
  • deleteWorkerno sensitive capability
  • executeCodeno sensitive capability
  • getAnalyticsTimeSeriesno sensitive capability
  • getArtifactno sensitive capability
  • getArtifactMetadataKeysno sensitive capability
  • getArtifactStatusSummaryno sensitive capability
  • getArtifactUploadUrlno sensitive capability
  • getCallno sensitive capability
  • getCallAnalyticsno sensitive capability
  • getCallEvaluationno sensitive capability
  • getCaseno sensitive capability
  • getChatno sensitive capability
  • getChatAgentno sensitive capability
  • getChatAgentPromptno sensitive capability
  • getEmailno sensitive capability
  • getExtractno sensitive capability
  • getExtractCitationsno sensitive capability
  • getExtractorno sensitive capability
  • getExtractorJobno sensitive capability
  • getOAuthUrlno sensitive capability
  • getPartnerJwksno sensitive capability
  • getProfileno sensitive capability
  • getPublicChatAgentno sensitive capability
  • getScheduleno sensitive capability
  • getSessionTokenno sensitive capability
  • getToolno sensitive capability
  • getVoiceAgentno sensitive capability
  • getVoiceAgentPlaceholdersno sensitive capability
  • getVoiceAgentPromptno sensitive capability
  • getVoiceAgentVersionno sensitive capability
  • getVoiceAgentVersionChangeSummaryno sensitive capability
  • getWorkerno sensitive capability
  • getWorkerPromptno sensitive capability
  • getWorkerRunno sensitive capability
  • getWorkerVersionno sensitive capability
  • getWorkerVersionChangeSummaryno sensitive capability
  • inviteTeamMemberno sensitive capability
  • listAgentWebhooksno sensitive capability
  • listApiKeysno sensitive capability
  • listArtifactsno sensitive capability
  • listCallFeedbackno sensitive capability
  • listCallsno sensitive capability
  • listCaseLinksno sensitive capability
  • listCasesno sensitive capability
  • listChatAgentsno sensitive capability
  • listChatMessagesno sensitive capability
  • listChatsno sensitive capability
  • listDispatchesno sensitive capability
  • listEmailsno sensitive capability
  • listEmailThreadsno sensitive capability
  • listExtractorJobsno sensitive capability
  • listExtractorsno sensitive capability
  • listExtractsno sensitive capability
  • listInboxesno sensitive capability
  • listInboxWebhooksno sensitive capability
  • listJobsno sensitive capability
  • listNotificationsno sensitive capability
  • listSchedulesno sensitive capability
  • listTeamInvitationsno sensitive capability
  • listTeamMembersno sensitive capability
  • listToolsno sensitive capability
  • listVoiceAgentsno sensitive capability
  • listVoiceAgentVersionsno sensitive capability
  • listWebhooksno sensitive capability
  • listWorkerModelsno sensitive capability
  • listWorkerRunMessagesno sensitive capability
  • listWorkerRunsno sensitive capability
  • listWorkersno sensitive capability
  • listWorkerVersionsno sensitive capability
  • listWorkerWebhooksno sensitive capability
  • notifyAdminno sensitive capability
  • partnerLaunchno sensitive capability
  • postChatMessageno sensitive capability
  • promoteVoiceAgentVersionno sensitive capability
  • promoteWorkerVersionno sensitive capability
  • refreshTokenno sensitive capability
  • removeCaseLinkno sensitive capability
  • removeMemberno sensitive capability
  • replyToEmailno sensitive capability
  • requestPasswordResetno sensitive capability
  • resendTeamInvitationno sensitive capability
  • resetPasswordno sensitive capability
  • revokeApiKeyno sensitive capability
  • revokeTeamInvitationno sensitive capability
  • scheduleJobno sensitive capability
  • searchCasesno sensitive capability
  • signInno sensitive capability
  • signUpno sensitive capability
  • updateApiKeyno sensitive capability
  • updateArtifactMetadatano sensitive capability
  • updateCallControlsno sensitive capability
  • updateChatAgentno sensitive capability
  • updateChatAgentPromptno sensitive capability
  • updateExtractorno sensitive capability
  • updateInboxno sensitive capability
  • updateMemberRoleno sensitive capability
  • updateScheduleno sensitive capability
  • updateSecretno sensitive capability
  • updateToolno sensitive capability
  • updateVoiceAgentno sensitive capability
  • updateVoiceAgentModelsno sensitive capability
  • updateVoiceAgentPromptno sensitive capability
  • updateWorkerno sensitive capability
  • updateWorkerMcpsno sensitive capability
  • updateWorkerPromptno sensitive capability
  • updateWorkerRunScopeno sensitive capability
  • uploadFileno sensitive capability
  • workerExecuteToolno sensitive capability
  • workerGetToolno sensitive capability
  • workerListToolsno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 10

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
v43.3.0 latest A 92/100 1 1.13.0 2026-09-07
v43.1.0 A 92/100 1 1.13.0 2026-09-04
v42.1.0 A 92/100 1 1.13.0 2026-09-01
v41.0.0 A 92/100 1 1.13.0 2026-08-27
v39.6.0 A 92/100 1 1.13.0 2026-08-25
Show 5 more versions ↓
v39.3.0 A 92/100 1 1.12.1 2026-08-24
v39.2.0 A 92/100 1 1.12.1 2026-08-20
v39.0.0 A 92/100 1 1.12.1 2026-08-19
v38.1.0 A 92/100 1 1.12.1 2026-08-18
v38.0.0 A 92/100 1 1.12.1 2026-08-17

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 · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/avallon-labs-mcp/badge.svg)](https://mcptrustchecker.com/registry/avallon-labs-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/avallon-labs-mcp"><img src="https://mcptrustchecker.com/registry/avallon-labs-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/avallon-labs-mcp/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 @avallon-labs/mcp --online

Use the free API → How scoring works

More in API Development