Gateway MCP Server

https://app.duvera.ai/mcp Remote v1.0

Published by app.duvera.ai — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Governed AI actions with signed, verifiable receipts: free keyless reads, human-approved writes.

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
Live
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 2

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: bluesky__trending_get ⇒ datadog__logs_view → venmo__payment_request. Untrusted input is ingested, private data is read, and it can be sent to an external sink — and at least one leg is a direct schema wire (⇒), where a producer's output drops straight into a free-text parameter of the next tool, so the chain needs little agent cooperation. Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow bluesky__trending_get → datadog__logs_view → venmo__payment_request

low Unconstrained path parameter "path" on "duvera__github_read_file"MTC-CAP-008

Tool "duvera__github_read_file" takes a path parameter "path" with no constraint. Without a canonicalize-and-contain check (not visible statically), this permits ../ traversal outside the intended root.

Fix: Resolve and verify the path stays within an allowed root; reject traversal sequences.

Location: tool duvera__github_read_file · inputSchema.properties.path

Tools 52

Each tool and what it can reach — enumerated from the running server.

  • bluesky__trending_getingests untrusted input
  • datadog__logs_viewreads sensitive data
  • duvera__github_read_filereads sensitive data
  • hackernews__stories_topingests untrusted input
  • postgres__sql_readreads sensitive data
  • venmo__payment_requestnetwork egress
  • amazon__package_trackno sensitive capability
  • applehealth__heart_rate_readno sensitive capability
  • applehealth__sleep_readno sensitive capability
  • applehealth__steps_readno sensitive capability
Show 42 more tools ↓
  • chase__balance_checkno sensitive capability
  • delta__boardingpass_showno sensitive capability
  • duvera__dev_npm_packageno sensitive capability
  • duvera__dev_pypi_packageno sensitive capability
  • duvera__dev_stackoverflow_searchno sensitive capability
  • duvera__finance_crypto_priceno sensitive capability
  • duvera__finance_exchange_ratesno sensitive capability
  • duvera__food_recipe_searchno sensitive capability
  • duvera__food_restaurant_searchno sensitive capability
  • duvera__geo_geocodeno sensitive capability
  • duvera__github_latest_releaseno sensitive capability
  • duvera__github_search_reposno sensitive capability
  • duvera__news_searchno sensitive capability
  • duvera__news_top_storiesno sensitive capability
  • duvera__reference_dictionaryno sensitive capability
  • duvera__reference_public_holidaysno sensitive capability
  • duvera__time_nowno sensitive capability
  • duvera__travel_flight_searchno sensitive capability
  • duvera__weather_air_qualityno sensitive capability
  • duvera__weather_currentno sensitive capability
  • duvera__wiki_searchno sensitive capability
  • duvera__wiki_summaryno sensitive capability
  • gmail__mail_readno sensitive capability
  • google_workspace__mail_searchno sensitive capability
  • googlecalendar__availability_findno sensitive capability
  • grubhub__order_trackno sensitive capability
  • instacart__menu_searchno sensitive capability
  • maps__eta_shareno sensitive capability
  • microsoft365__calendar_listno sensitive capability
  • microsoft365__mail_searchno sensitive capability
  • notion__notes_searchno sensitive capability
  • obsidian__notes_searchno sensitive capability
  • open_meteo__weather_forecastno sensitive capability
  • opensky__flights_liveno sensitive capability
  • shazam__audio_identifyno sensitive capability
  • slack__message_searchno sensitive capability
  • southwest__flight_statusno sensitive capability
  • telegram__message_readno sensitive capability
  • twitter__tweets_searchno sensitive capability
  • uber__fare_estimateno sensitive capability
  • united__flight_statusno sensitive capability
  • wallet__boardingpass_showno sensitive capability

Toxic flows 1

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

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
v1.0 latest A 94/100 2 1.13.0 2026-09-06

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/app-duvera-ai/badge.svg)](https://mcptrustchecker.com/registry/app-duvera-ai)
HTML
<a href="https://mcptrustchecker.com/registry/app-duvera-ai"><img src="https://mcptrustchecker.com/registry/app-duvera-ai/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/app-duvera-ai/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 https://app.duvera.ai/mcp --online

Use the free API → How scoring works

More in Other