Swagger Petstore MCP Server

@open-mcp/swagger-petstore npm v0.0.9

Published by @open-mcp — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
98/100
Last scanned
Trust
A · 98/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
Minimal
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.
A Why this grade 100 − 2.1 = 98/100

Every server starts at 100. These are the exact deductions the deterministic engine applied — each one reproducible, none of it an opinion or an LLM's guess:

PointsWhat was foundCategory
−2.1 Package has no source repository MTC-SUP-011 supply-chain

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 the deduction.

Findings 2

medium Dynamic module load from a non-literal (dist/server.js)MTC-SRC-005

In the server's implementation (`dist/server.js:13`): Loading a module chosen at runtime (from a variable) can pull in and run attacker-influenced code paths. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: import(file)

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 dist/server.js

low Package has no source repositoryMTC-SUP-011

"@open-mcp/swagger-petstore" declares no repository URL, so its published artifact cannot be compared against reviewable source.

Fix: Prefer packages that link to public, reviewable source.

Location: package @open-mcp/swagger-petstore

What this scan could not see

Versions

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.0.9 latest A 98/100 2 1.5.0 2026-07-22

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

Use the free API → How scoring works

More in API Development