Is paid-micro-apis safe to use?

paid-micro-apis scores 88/100 (grade B) on the Canopii Trust Index — good, minor gaps. It passes 14 of the 25 security controls that apply to it, with no confirmed security failures.

How reliable is the security score for paid-micro-apis?

We could evaluate 88% of the controls that apply to paid-micro-apis. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.

How was paid-micro-apis scored?

Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.

paid-micro-apis MCP Server Security Report

eu.skavio/paid-micro-apis

x402 USDC-paid MCP tools: 7-chain transaction checks, PDF evidence and DNS/TLS audits.

88B

Security Trust Score

Grade B · Moderate posture

Tier 1 · Public sourceHigh confidence · 88%latest v1.0.0 Repository

Declared MCP capabilities

ResourcesPrompts

Run it securely

Host eu.skavio/paid-micro-apis in a governed environment — SSO in front, every tool call attributed and audited.

Are you the maintainer?

Verify with GitHub to get alerted whenever skavio-eu/skavio-agent-tools changes score — and claim the badge for your README.

Claim this server

The short answer

Is paid-micro-apis safe to use?: paid-micro-apis scores 88/100 (grade B) on the Canopii Trust Index — good, minor gaps. It passes 14 of the 25 security controls that apply to it, with no confirmed security failures.
How reliable is the security score for paid-micro-apis?: We could evaluate 88% of the controls that apply to paid-micro-apis. Scores are deterministic — the same source always produces the same score — and a partially-scannable server cannot present a high one, because confidence caps the result. The scanner is open source, so this score can be reproduced independently.
How was paid-micro-apis scored?: Its published source was scanned against a fixed catalog of weighted security controls covering code safety, committed secrets, dependency vulnerabilities, tool-description integrity, authentication and transport, and maintenance. A confirmed flaw caps the score outright regardless of what else passes. The full rubric is published.

Reputation0stars0forks1open issuestodaylast commit<1yage

Security controlslatest scored version v1.0.0

Each control is evaluated deterministically with evidence. The score is earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

Warn
Strict JSON Schema Enforcementschemas not strict
Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.
Fix: Set additionalProperties:false and require explicit parameters on every tool.
Pass
Indirect Prompt Injection (IPI) Defensesguardno injection markers
Tool/prompt/resource text is free of hidden instructions that could hijack the agent.
Pass
In-Session Definition Integrityguardno call-gated or call-time tool definition changes
Tool and prompt definitions stay fixed during a session — they don't change after a few calls, which is how runtime-gated rug-pulls slip past one-time review.
Pass
User-in-the-Loop / Approval Scopeguardno destructive tool scope
No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.
N/A
Tool Definition Integrityguardno prior version to diff
Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

Application Security Checks

Warn
Credentials sourced from environmentno env-based config detected
Reading secrets from env/secret stores avoids hardcoding them.
Fix: Read credentials from environment variables or a secret manager.
Warn
Dependencies pinned (lockfile)no lockfile found
A lockfile makes installs reproducible and resistant to silent dependency swaps.
Fix: Commit a lockfile (package-lock.json / pnpm-lock.yaml / poetry.lock).
Warn
Declares a licenseno recognized license
A clear license is required for legal enterprise use.
Fix: Add a recognized SPDX license (MIT, Apache-2.0, …).
Warn
Has a security policyno security policy
A SECURITY.md gives a private path to report vulnerabilities.
Fix: Add SECURITY.md with a disclosure contact and process.
Warn
Adoption & popularitylimited adoption
A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.
Fix: Adoption grows naturally with real-world use; this never gates the score.
Pass
No command-injection sinksguardno sinks found
Untrusted tool input reaching a shell yields remote code execution.
Pass
No dynamic code executionguardno sinks found
eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.
Pass
No path traversalguardno sinks found
Naive path checks let tools read/write outside intended directories (EscapeRoute-class).
Pass
No SSRF sinksguardno sinks found
Fetching tool-supplied URLs can pivot into internal networks and metadata services.
Pass
No unsafe deserializationguardno sinks found
pickle/yaml.load/etc. on untrusted data can execute code.
Pass
No committed secretsguardno secrets found
Hardcoded keys/tokens in published source are live credentials an attacker can use.
Pass
Actively maintainedrecent commits
Unmaintained servers don't receive security fixes.
Pass
Repository not archivedguardactive
Archived repositories will never be patched.
Not checked
No known-vulnerable dependenciesno lockfile found
Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.
Not checked
Signed releasesnot evaluated
Signed releases let consumers verify artifacts weren't tampered with.
N/A
No install/post-install scriptsguardno published package
install hooks run arbitrary code on every consumer at install time.
N/A
Package name not typosquattingguardno published package
Names mimicking popular packages are a common malware delivery vector.
N/A
Published with provenanceno published package
Build provenance attests the artifact was built from the claimed source by CI.
N/A
Established maintainerno published package
Brand-new / single anonymous maintainers raise takeover and malware risk.

Transport & Trust Model

Warn
IAM / Authentication Scopingno authentication handling detected
OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.
Fix: Implement OAuth 2.1 with a .well-known/oauth-protected-resource document.
Warn
Execution Sandboxingruns natively (no container image)
A container/sandbox image limits blast radius; a server that runs natively has full host access.
Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.
Pass
Transport Encryption (TLS)guardall remotes use HTTPS
Plaintext HTTP exposes traffic and bearer tokens to interception.
Pass
No Token Passthroughguardno inbound token forwarded downstream
The client's token is never forwarded to downstream APIs — the server obtains its own, correctly-scoped credential instead.
Pass
Network Exposureno bind-all detected
Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.
Not checked
DNS-Rebinding ProtectionHTTP transport not found in source
HTTP endpoints reject requests carrying an unlisted Origin, so a malicious web page can't drive the server through the user's browser.
N/A
Live Endpoint Reachablenot dynamically scanned
A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.
N/A
Authentication Enforced (live)not dynamically scanned
If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Embed this score

Add the live badge to your README — it updates automatically on every rescan.

markdown

[![Canopii Trust Score](https://index.canopii.dev/api/badge/eu.skavio/paid-micro-apis)](https://index.canopii.dev/server/eu.skavio/paid-micro-apis)

html

<a href="https://index.canopii.dev/server/eu.skavio/paid-micro-apis"><img src="https://index.canopii.dev/api/badge/eu.skavio/paid-micro-apis" alt="Canopii Trust Score" /></a>

Versions

Version	Score	Status	Published
v1.0.0latest	88B	scored	10/12/2026

Wondering how this compares? The MCP Security Index tracks grade distribution, committed secrets, and missing authentication across the whole ecosystem, refreshed monthly.